Accompanying blog post

[sisyphusSmiling]

Description

This example should serve as a basis for technical content in addition to developer education, so will need a technical deep dive blog post focussing on the what, why, and how in addition to potential broader, more meaningful implications of the same pattern beyond this toy example.

[sisyphusSmiling]

WIP in this notion page

[sisyphusSmiling]

WHAT is this content you created?

This piece covers how Flow’s EVM equivalence paired with Cadence transactions empowers developers to create seamless, user-friendly blockchain experiences all without sacrificing interoperability.

WHY did you create this? What goal is it trying to achieve?

As a part of the DevEx team's approach to publishing walkthroughs on Flow's differentiating features, this post is written at appeal to product and business-minded readers. The intended action is that the would identify the functionality as a competitive advantage for their projects and pass the piece along to their developer teams for validation. The call to action then is a developer-focussed wakthrough, guiding developers through how to use Cadence to batch EVM transactions using Cadence and experiencing firsthand the problem and solution as well as equipping with the skills required to replicate the pattern in their own transaction flows.

WHERE will this content be published? (blog, social, dev docs, etc.)

This post is written for publishing on the flow blog at flow.com/blog.

WHO will be publishing this content? (author byline; dev doc; Flow)

This was written by @sisyphusSmiling and can be published under either his byline or the Flow team, whichever is most consistent with blog publishing patterns.

[BryceBladon]

Thanks, @sisyphusSmiling!

Goals:

• Convince product/business decision-makers that Flow's EVM compatibility + Cadence offers a competitive advantage through superior UX
• Drive technical readers to developer documentation for implementation details

[BryceBladon]

@sisyphusSmiling Left feedback and suggested changes as comments. (Notion's tracked changes can cause quite a few UX headaches in my experience)

I also made some direct edits where hyphens needed to be turned into colons or em-dashes respectively.

Once we finalize these edits, we can put it on the content calendar for next week or early December.

[sisyphusSmiling]

Updated the doc with your suggestions/feedback, thanks @BryceBladon!