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

Move every HTML component to the public application #23

Open
daleal opened this issue Aug 6, 2021 · 0 comments
Open

Move every HTML component to the public application #23

daleal opened this issue Aug 6, 2021 · 0 comments
Assignees
Projects

Comments

@daleal
Copy link
Collaborator

daleal commented Aug 6, 2021

Right now, when requesting for /:username Num directs that request to a Function, that processes the username and returns HTML with the user data. What we should be doing instead is that we should receive every request for /:username on an HTML on the public application. This HTML should have a JavaScript file that makes a request to a Function, which should now return a JSON with the user data (instead of returning the HTML directly). Finally, the JavaScript file should use this information to change the content of the HTML being showed to the user with the data just retrieved.

Caveat: This change by itself would screw our og tags (the preview data), as any crawler would find itself with an empty HTML on its rusty little hands. We would probably need to migrate immediately to a more complete frontend framework that supports SSR.

@daleal daleal added this to To do in Roadmap via automation Aug 6, 2021
@daleal daleal self-assigned this Sep 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Roadmap
To do
Development

Successfully merging a pull request may close this issue.

1 participant