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
However, the moar we add, the moar the JSON Resume will take. Seems some kind of optimization will be needed here.
Some ideas:
At build time, create JSON data for each section through scripts
SQLite HTTP VFS to save everything in a database. But when serving, use only the needed chunks via HTTP chunks. Seems complex & tricky though. As maybe GitLab Pages doesn't support those. Also will need indexes / views to avoid queries looking in more chunks than the actually needed. It scales well though. To later query that info efficiently.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This will be very useful for #561
However, the moar we add, the moar the JSON Resume will take. Seems some kind of optimization will be needed here.
Some ideas:
Beta Was this translation helpful? Give feedback.
All reactions