Launch HN: Webiny (YC W21) – Open-source serverless framework with a drop-in CMS

📰 Hacker News · SvenAl

Learn how to use Webiny, an open-source serverless framework with a drop-in CMS, to build custom serverless applications and websites efficiently

intermediate Published 11 Mar 2021
Action Steps
  1. Explore Webiny's documentation to learn about its features and capabilities
  2. Install and configure Webiny to start building serverless applications
  3. Use Webiny's drop-in CMS to manage content and integrate it with custom business logic
  4. Build and deploy a serverless application using Webiny's framework and CMS
  5. Compare Webiny with other serverless frameworks and CMS solutions to determine its suitability for your project
Who Needs to Know This

Developers and development teams can benefit from using Webiny to streamline their workflow and reduce project delivery time

Key Insight

💡 Webiny combines the benefits of a serverless framework with a drop-in CMS, allowing developers to build custom applications and websites efficiently

Share This
🚀 Launch HN: Webiny (YC W21) - Open-source serverless framework with a drop-in CMS! 📄

Key Takeaways

Learn how to use Webiny, an open-source serverless framework with a drop-in CMS, to build custom serverless applications and websites efficiently

Full Article

Hi, Sven and Pavel here - we're building a self-hosted, open-source framework for developers that want to create serverless applications and websites. After 10 years of running a web development agency and delivering over 100 projects, we tried many different approaches to building apps and websites. When we looked at the patterns for most of the projects we delivered, it was always a combination of custom business logic and a way to manage content, like pages, news articles, and similar. Looking at the options available on the market, we either had frameworks for building the custom logic or ready-made CMS solutions for managing the content. There was no combination for when we wanted to do both. And this is one of the biggest pains we had. We would either force custom logic inside a CMS and break things or make them hard to maintain, or use a framework and take much longer to deliver a project since we'd end up building a custom CMS and making the whole thing more expensive
Read full article → ← Back to Reads