Announcing Frontity 1.0!

Reyes Martínez on June 20, 2019

Today, we’re incredibly excited to introduce Frontity 1.0 to the world! 🎉 This is an important milestone for us here at Frontity but also for all ... [Read Full]
markdown guide
 

Wow! I think I may try this out for my next project. Wordpress is very user friendly and familiar to many users--so coupling it with React for a fast modern front end is almost the best of both worlds.

 

Thanks Brian! That's right. We do actually think this is the future of WordPress.

We'd love to get your feedback if you have the chance to try Frontity out for your project. If there is anything at all we can help with, please let us know :)

 

Looks awesome. I’m going to try this in a bit, for sure. I’ve already implemented a fast navigation using Swup, but I’ve run into a bit of a snag that I think is inherent with this type of thing: Plugins.

Many WordPress plugins require execution of JS, or are otherwise dependent on having a page load in its entirety. Does Frontity do anything to deal with that?

 

Thanks! These are websites built entirely in React. You can get a similar result using transition libraries with React like react-spring.

However, if you use Frontity, as it uses the WordPress REST API to populate the site, you won’t get any JS code from your WP plugin unless that code is part of a post/page content.

Let me know if you still have any doubts :)

 

Thanks for the reply. Let’s say I want a contact form, or something more special (something like activity submissions), I’d have to put that code into Frontity (or the theme?) yeah? I suppose custom made Gutenberg blocks would fit this as well, since they’re rendered inside the post content.

Analytics, if one wants those, would also have to be adapted to be triggered per rest-request.

Yes, everything that is not exposed in the REST API and/or requires some kind of logic, will need to be replicated on our end with Frontity. In the case of analytics, we are planning on releasing a plugin as we had in our previous version of the framework.

Regarding Gutenberg blocks, right now, they are rendered in the content as simple HTML code, so what you can do is to use @frontity/html2react and create a processor that will identify that HTML belonging to the block and render on its place the React component of your choice.

We try to make Frontity completely extensible, so if somebody creates a solution for a Gutenberg block, or an analytics library, it can be reused by the community.

I hope this solves your doubts! 😄

 

Great job on the amazing work you guys have done. Is there any live app built with frontity?

 

Hello Mohammadjavad! Thanks for the cheers up :)

You can see a live demo of Frontity here mars.frontity.org

Now that the 1.0 is live, we will be working on more examples so people can get inspired :)

I can also tell you that we are working hand to hand with some agencies and big blogs helping them create their Frontity frontends, we will be showcasing them as well.

By the way, if you access our blog.frontity.org from a mobile device what you will see is a React site created with an older version of our framework, we will be upgrading it to Frontity 1.0 and sharing the code as well :)

 

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?

 

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!

 
code of conduct - report abuse