You've been handed a design and tasked with writing the code that will bring that design to life. Where do you start?
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.
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.
You could build a house one brick at a time. Every room could be unique. That would take a long time and it'd cost a lot of money, as houses usually do. But what if you could build a house room-by-room?