To some degree, I understand why this is the way that it is, but still,
this is an absolutely galaxy-brain way of turning markdown into a "static" HTML page.
react-static, **whyyy?**
hopefully I'm doing something wrong. **Surely** I must be doing something wrong here.
At this point, I feel like I'm literally better off re-inventing this from scratch. what the hell.
react-static claims to do three things as I see it:
1. multiple entrypoints into a runtime SPA with progressive fake-links
2. useful defaults for multi-page react development
3. pre-rendering the initial state of every page for fast load and “““SEO”””
afaict, it does the first two.
and really, what I want is number 3.
(correction: I want 2 and 3)
fuchsiaaaaaaaaaaaaaaaaa
@vy I was about to talk about my ssg project but that's not so useful as it currently does not have facilities for client-side stuff, although I might scope-creep that someday hah
@f0x yeah the main difficulty is in orchestrating a multi-page build with proper component splitting
last night I threw together nodejs code for finding markdown files and feeding them into react-static in about an hour, and given how easy that was I might just carry on with that and ditch everything else.
if every page/template’s entrypoint component is tagged with an attribute declaring whether it’s dynamic, it *should* be easy enough to decide whether to drop script tags in the page
@f0x
🔖’d