Need advice about which tool to choose?Ask the StackShare community!
As a Frontend Developer I wanted something simple to generate static websites with technology I am familiar with. GatsbyJS was in the stack I am familiar with, does not need any other languages / package managers and allows quick content deployment in pure HTML
or Markdown
(what you prefer for a project). It also does not require you to understand a theming engine if you need a custom design.
So many choices for CMSs these days. So then what do you choose if speed, security and customization are key? Headless for one. Consuming your own APIs for content is absolute key. It makes designing pages in the front-end a breeze. Leaving Ghost and Cockpit. If I then looked at the footprint and impact on server load, Cockpit definitely wins that battle.
10 Years ago I have started to check more about the online sphere and I have decided to make a website. There were a few CMS available at that time like WordPress or Joomla that you can use to have your website. At that point, I have decided to use WordPress as it was the easiest and I am glad I have made a good decision. Now WordPress is the most used CMS. Later I have created also a site about WordPress: https://www.wpdoze.com
Pros of Gatsby
- Generated websites are super fast28
- Fast16
- GraphQL15
- Progressive Web Apps generation10
- Easy to connect with lots of CMS via official plugins9
- Reusable components (React)9
- Allows to use markdown files as articles7
- Static-sites5
- All the benefits of a static website + React+GraphQL5
- Images5
- List of starters as base for new project4
- Easy to connect with Drupal via official plugin3
- Open source3
- Gitlab pages integration1
- Incremental Build1
Pros of WordPress
- Customizable416
- Easy to manage367
- Plugins & themes354
- Non-tech colleagues can update website content259
- Really powerful247
- Rapid website development145
- Best documentation78
- Codex51
- Product feature set44
- Custom/internal social network35
- Open source18
- Great for all types of websites8
- Huge install and user base7
- I like it like I like a kick in the groin5
- It's simple and easy to use by any novice5
- Perfect example of user collaboration5
- Open Source Community5
- Most websites make use of it5
- Best5
- API-based CMS4
- Community4
- Easy To use3
- <a href="https://secure.wphackedhel">Easy Beginner</a>2
Sign up to add or upvote prosMake informed product decisions
Cons of Gatsby
- No ssr7
- Documentation isn't complete.4
- Very slow builds3
- Flash of unstyled content issues2
- For-profit2
- Slow builds2
- Plugin driven development1
- Difficult maintenance1
- Problematic between develop and build commands1
- Too many dependencies1
- Difficult debugging1
Cons of WordPress
- Hard to keep up-to-date if you customize things13
- Plugins are of mixed quality13
- Not best backend UI10
- Complex Organization2
- Do not cover all the basics in the core1
- Great Security1