Welcome

Metaframeworks Weekly is your bite-sized dose of the most important news and updates in the world of metaframeworks. Hand-curated by Fyodor, this newsletter cuts through the noise to bring you only the essentials.

Every week, we dive into the latest from frameworks like Next.js, Nuxt, SvelteKit, Astro, and more. Expect concise, actionable insights, and a sprinkle of community highlights — all delivered straight to your inbox. We take a sober look at the metaframeworks movement and ecosystem, presenting both the positive and negative aspects without strong opinions or judgments.

Latest newsletter issues

Frequently Asked Questions

  • How do you curate the content?

    My content curation process involves monitoring official blogs, social media accounts (BlueSky mostly), GitHub repositories (changelogs and releases), and community discussions (Reddit, HackerNews, etc.) of all major metaframeworks and tools around them. Sometimes I also create my own content which relates to the metaframeworks ecosystem and refer to it in this case. The target topics mostly coincide with the chapters of the Encyclopedia of Metaframeworks. I prioritize official releases, significant updates, security advisories, and innovative community projects. The goal is to provide a balanced view of the ecosystem without bias toward any particular framework or tool, and even any rigid opinions on the metaframeworks approach in general, because the idea is consider it objectively with all the relevant cons and flaws included.

  • Why the issue titles sound so weird?

    I use song names as issue titles to add a touch of creativity and fun to the newsletter. It's my way of making each issue unique and memorable. Usually, the chosen song, its title and a tagline are 100% relevant to the encompassing topic of the issue.

  • Can I suggest topics for future issues?

    Absolutely! I welcome topic suggestions and any other ideas and thoughts from readers. Feel free to send them to fyodor@metaframe.works, my BlueSky, or reply directly to any newsletter issue, if you're subscribed. I genuinely value any input as it helps me cover the topics most relevant to the newsletter community.