Exploring a theoretical approach to enabling Notion to serve as a CMS for complex websites with interactive components.
You've been handed a design and tasked with writing the code that will bring that design to life. Where do you start?
It takes a lot to build a rock-solid, performant, beautiful, well-organized, component-driven site. But there's one thing that matters more than the rest.
Why would you build a website with components? Because it can be great! But you should know what you're getting yourself into first.
Help your content editors enjoy their CMS experience by designing a content schema that balances productivity and flexibility.
Components may reduce the total volume of code you have to write, but keeping them organized can be a nightmare. Here are three simple rules to keep you organized, consistent, and productive.
While Eleventy doesn't appear to be built for today's component-driven landscape, here are three approaches we can take to get closer.
Component adapters are a great way to separate logic from presentation in component-driven development projects. Here's how I've implemented the approach in Gatsby.
We've traditionally organized files by type. But that can make specific files difficult to track down, especially in an era dominated by component-driven development.
It's tough to know when it's the right time to break a component up into smaller components. Here's a way to approach that process that relies on more than what you see on the screen.