problem

Getting started with Yew projects often requires significant boilerplate and lacks the conventions and tooling that make modern frontend frameworks productive.

motivation

I wanted Rust frontend development to feel as approachable as Next.js. Yewi Kit began as a personal toolkit to streamline my own workflow before evolving into an open-source ecosystem for the community

solution

Built a complete toolkit combining reusable components, project scaffolding, theming, SCSS and Tailwind integration, allowing developers to own the generated code while following a consistent architecture.

decisions

• Adopted a copy-and-own component philosophy instead of locking users into a component library.
• Integrated SCSS and Tailwind to provide flexible styling without sacrificing project structure.
• Designed the project architecture to feel familiar to React and Next.js developers.

challenges

• Building an efficient styling pipeline around Trunk without unnecessary recompilation.
• Finding a balance between flexibility and convention for generated projects.
• Designing a versioning strategy that allows future architectural changes without breaking existing projects.
• Improving SEO limitations inherent to client-side WebAssembly applications.

lessons

• Developer Experience is as important as runtime performance.
• Good defaults reduce friction without reducing flexibility.
• Versioning developer tooling requires long-term thinking beyond features.