DEV Community

Discussion on: Announcing Frontity 1.0!

Collapse
alex_barashkov profile image
Alex Barashkov • Edited on

Thank you for that nice project! Could you tell me about why is it better or "when" is it better to use Frontity with WordPress and not Gatsby with WordPress?

Collapse
r_martinezduque profile image
Reyes Martínez Author

Hey Alex, did you have the chance to try Frontity? We are actively looking for feedback to improve the framework and would love to learn from your experience. Let me know if you want to chat. Thanks :)

Collapse
alijaffar profile image
Eli Von

Trying it right now and looking to create my first page with it! I Googled and landed here when checking if Frontity supports pages, and this release does. So far it's a good experience, just wish there was more details around the SEO bit (I know you are working to release @frontity/head-tags package), as well as docs for page template creation. Cheers!

Thread Thread
r_martinezduque profile image
Reyes Martínez Author • Edited on

Hi Ali! Many thanks for your feedback! You're totally right, we have to keep working on our docs to address more details about the SEO. Feel free to reach out in the meantime if you have any questions about it (Christian Oliveira, our technical SEO expert, will be happy to help).

P.S. In case it helps, we also wrote this post about SEO for headless WordPress a few months ago: blog.frontity.org/seo-for-headless....

Collapse
r_martinezduque profile image
Reyes Martínez Author • Edited on

Hi Alex! Thanks for your comment. That's a very good question :)

We think Gatsby is an amazing framework, we've learned a lot from it, and the things it does it does really really well. But Frontity has a different approach in certain aspects:

  1. It's 100% focused on WordPress. This means the number of concepts to learn are minimal, it doesn't need any complex configuration to get you started and the APIs that WordPress developers use to create themes are tailored for the things they usually need.

  2. It's rendered dynamically. This means people don't have to rebuild the HTML each time they modify or publish something. Our preferred approach is SPR (zeit.co/blog/serverless-pre-rendering) although there are many ways to configure it. It's as fast as a static site: mars.frontity.org/.

  3. It's opinionated. It has its own state manager and CSS solution. Thanks to that people don't need to learn things like Redux and at the same time it powers a very flexible extensibility pattern, more similar to the one of WordPress itself than to the rest of JS frameworks.

Hope it solves your doubt!