Source: https://community.frontity.org/t/my-personal-blog-site/1962/6
These are generic needs of an isomorphic app like the one you’re creating with Frontity, this is, an app that returns HTML from the server but then hydrates the React App so it can take control of the app from there (until a new page reload is done)
We haven’t worked all the uses cases but here you have some threads that may help you to understand better the possibilities with a Frontity project:
How to read Environment Variables 1
Deploy to Netlify
One key idea that I think we need to explain better in the docs (although is briefly explained here) is that npx frontity build produces basically:
server.js file
static folder w/ static assets
This server.js is the one launched with the command npx frontity serve
But this server.js is really a middleware that (in theory) could be connected to any Node Web Server, adding logic before the requests are responded with the HTML
This architecture will allow to “extend” the server part to add things such as authentication
This is another feature that is is not really related to a Frontity project but to a generic Isomorphic React App. There are several techniques you could use to achieve this:
Use of polyglot-react HOC → https://github.com/hoducha/polyglot-react
Use of Context API → https://itnext.io/using-reacts-context-api-to-provide-a-localization-toolbox-for-your-components-48915f04bb54
We’re a small team trying to push forward this Open Source project, so there are still a lot of things to be done in terms of documentation and demos.
But we’ll be happy to support any Frontity project through this Community Forum, so feel free to continue using it to share any doubts or feedback about Frontity
Hope this helps.
Source: https://community.frontity.org/t/my-personal-blog-site/1962/6