- Separate pages
- classic approach
- requires includes mechanism
- need to persist state somehow (localstorage?)
- SPA
- too much code, turns messy
- requires inclusion mechanism for separate pages
- raw links are unwieldy (
@click=history.pushState(null,null,path)), we need special directive, eg:to="path"
- If we use react/etc, we include JS that renders content.
- That means that include-fragment is the same tax/method as including script.
- We need to include before running sprae
- We either need github/include-element or some server-side-tech like jekyll
a. github/include-element
- dynamic problem
b. jekyll _includes
- no js-side problems
- keeps static websites going
- CSHTML fully, js makes parts dynamic
- too many pages
- problematic for multiple interactions
- JSON-LD, js makes markup
- too many origin pages
- good for multiple interactions