|
| ▲ | fullstacking a minute ago | parent | next [-] |
| To be fair this project uses zero 3rd party npm modules for runtime.
The total runtime JS it uses is 1.76kB in size. |
|
| ▲ | hunter2_ 40 minutes ago | parent | prev | next [-] |
| I agree with no JS, but why PDF over HTML? Hard-wrapping for letter-sized paper (ok, a PDF doesn't need to be letter-sized, but most menus are approximately that) with crapshoot reflow options for soft-wrapping in certain viewer apps is pretty dicey on a phone, mitigated only slightly by rotating the phone sideways. The only benefit I can think of is if it leads to more frequent updates by the restaurant, due to limited skillset. |
|
| ▲ | dugmartin an hour ago | parent | prev | next [-] |
| I agree. There are lots of free AstroJS themes for restaurants that generate static html that you can host somewhere like Firebase hosting for free. - https://astro.build/themes/details/astropie/ - https://astro.build/themes/details/astrorante/ - https://astro.build/themes/details/tastyyy-restaurant-websit... |
| |
| ▲ | adzm an hour ago | parent [-] | | I love Astro; there is so much you can do with it. |
|
|
| ▲ | mvdtnz 22 minutes ago | parent | prev | next [-] |
| No one is browsing the internet without JS today (within margin of error). Whether or not this "should" be the case, it is. |
|
| ▲ | stronglikedan an hour ago | parent | prev | next [-] |
| A PDF can't get the user halfway through the delivery process before seeing the soups. |
|
| ▲ | cess11 23 minutes ago | parent | prev [-] |
| The soup shows for me without JS. |
