Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance and Caching - Hosting Situation #137

Open
bodobraegger opened this issue Sep 18, 2023 · 1 comment
Open

Performance and Caching - Hosting Situation #137

bodobraegger opened this issue Sep 18, 2023 · 1 comment
Assignees
Labels
code Issue related to coding changes upload

Comments

@bodobraegger
Copy link
Collaborator

Currently, we have a static front-end with a pull-only back-end architecture, data being pulled from Strapi.

It would be better if we can integrate Strapi onto a server from where we also host the front-end, to allow for actual browser based caching using Progressive Web Apps, by serving the .json content files from the same location.

Related to #134 and #133.

@aladwani aladwani added the code Issue related to coding changes label Sep 20, 2023
@bodobraegger
Copy link
Collaborator Author

When the content is finalized, we ship it together with the front-end and eliminate the need for a back-end.

This will make caching everything possible and speed up the loading times.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code Issue related to coding changes upload
Projects
None yet
Development

No branches or pull requests

3 participants