Open-source serverless enterprise CMS platform. Includes a headless CMS, page builder, form builder, and file manager. Easy to customize and expand. Deploys to AWS.
No features have been listed yet.
Based on our record, GitHub Pages seems to be a lot more popular than Webiny. While we know about 467 links to GitHub Pages, we've tracked only 4 mentions of Webiny. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Even Strapi needs to be hosted somewhere, and that usually involves a recurring fee. I've had great success over the past 2 years building blogs using http://webiny.com, and because they get low traffic, I've only ever had 1 bill from AWS that was around 80 cents US. Source: almost 2 years ago
Strapi is awesome, I've been a fan of the project since its early days. However, I've been closely watching Webiny too. It's easier to host because you don't have to worry about running Docker containers or installing MongoDB on your local machine. Instead you put it on your AWS account (can be done with a few clicks), define your content models once it's there and you then only pay for usage. http://webiny.com. Source: about 2 years ago
Yeah I hear you, SAAS CMS platforms can get prohibitively expensive really quickly after the initial free tier expires. I've found hosting Strapi (or similar) on Heroku has saved me the cost of keeping a server instance running, which usually would cost $5-10 per month. However, the most cost effective for me so far has been Webiny. It's serverless so you install it on AWS and typically don't pay as much (if... Source: about 2 years ago
Otherwise if you want a framework to build on, there's Redwood (which works particularly well on Netlify and Vercel) or Webiny (for AWS, Azure and others). - Source: dev.to / almost 3 years ago
You can deploy to Github Pages in under 2 minutes by following their documentation. - Source: dev.to / 11 days ago
For this application, Elm controlled the routing. So, I had to adapt the scripts to deploy to Netlify instead of GitHub Pages. Why? Because you need to be able to tell the web server to redirect all relevant requests to the application. GitHub Pages doesn't have support for it. - Source: dev.to / about 1 month ago
It's super easy to publish a static site like the resume with GitHub Pages. Just check out the docs. - Source: dev.to / about 2 months ago
GitHub Pages: Host your static websites directly from your GitHub repository. - Source: dev.to / 3 months ago
As per many other comments, it sounds like a static site generator like Hugo (https://gohugo.io/) or Jekyll (https://jekyllrb.com/), hosted on GitHub Pages (https://pages.github.com/) or GitLab Pages (https://about.gitlab.com/stages-devops-lifecycle/pages/), would be a good match. If you set up GitHub Actions or GitLab CI/CD to do the build and deploy (see e.g.... - Source: Hacker News / 4 months ago
Serverless - Toolkit for building serverless applications
Vercel - Vercel is the platform for frontend developers, providing the speed and reliability innovators need to create at the moment of inspiration.
Ionic Creator V2 - Build better mobile apps, faster
Jekyll - Jekyll is a simple, blog aware, static site generator.
Payload CMS - Headless CMS and Application Framework built with Node.js, React and MongoDB
Netlify - Build, deploy and host your static site or app with a drag and drop interface and automatic delpoys from GitHub or Bitbucket