You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 14, 2020. It is now read-only.
I am not sure if this can be expressed as a JAMstack?
Couple of options:
Clean separation between backend API (say given a GH username, provide their data as JSON from cache or whtever) and web app frontend (given JSON data, show it in browser)?
When a user does a "sign up", compute their GH data and generate a static HTML representing their profile and park it at ghuser.io/username which can then be periodically updated (if we are okay with delay between data change and update of profile).
PS: hey @xiegeo ! noticed you on the contributors, haha small world!
The text was updated successfully, but these errors were encountered:
Thanks for the input! Not sure yet if we want this, but keeping this issue open to think about it. Definitely worth thinking about it while looking into #103 and #49
I am not sure if this can be expressed as a JAMstack?
Couple of options:
PS: hey @xiegeo ! noticed you on the contributors, haha small world!
The text was updated successfully, but these errors were encountered: