solution for front-end #2

Closed
opened 2020-09-02 18:38:56 +00:00 by oat · 0 comments
Owner

there are currently 3 ways this site could serve the user properly formatted html:

  1. give out pages that then contact the server through an api using javascript, and use that info. id go against this mainly because i dont want javascript to be mandatory to use the site
  2. embed the data into the document which the document can then read from using javascript, same as 1 but a bit less tedious and less networky, you send it once and its done
  3. embed the data into the document manually with replacement. this is the hackiest one and id very much rather not do this one

all of these are equally cursed and id much rather want some sort of solution that isnt this janky and dumb

there are currently 3 ways this site could serve the user properly formatted html: 1. give out pages that then contact the server through an api using javascript, and use that info. id go against this mainly because i dont want javascript to be mandatory to use the site 2. embed the data into the document which the document can then read from using javascript, same as 1 but a bit less tedious and less networky, you send it once and its done 3. embed the data into the document manually with replacement. this is the hackiest one and id very much rather not do this one all of these are equally cursed and id much rather want some sort of solution that *isnt* this janky and dumb
oat closed this issue 2020-09-04 04:43:27 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: oat/in-the-database-2#2
No description provided.