- Rendering Strategies
- Static
- Client Only
- init impl
- find something that works better. basic hooks don't work with react-dom
- Generate better HTML
- Allow users to add elements to <head> tag
- Server Only
- Self-hosted
- Build
- Built-in Server
- Add back
preact
andpreact-render-to-string
for server-side hydration (from pre-rendered html)
- Self-hosted
- Server and Client
- HTML Layouts
- Plugins?
- Vanilla Extract
- Test the order of HTML, CSS, and JS getting downloaded and painted on the screen
- Defer CSS loading for elements not in view
- Compare Speed of MJS loading and CJS loading in browser
- Use web workers to pre-render pages client side
- Preact example: https://github.com/developit/preact-worker-demo/tree/master
- Use Preact instead of React it's soooo much better
- Compile user scripts to ESM to allow tree shaking
- Clean up Framework & Example dependencies (after done testing rendering methods)
- TS config for example
- TS config for framework
- Better way for JS entrypoint templates
- Experiment with the option to pre-render
- Client Only
- Server Only
- Server and Client
- Use Java Research license for LICENSE.md
- Add licenses folder for dependencies
- Router
- Use a tags w/ onclick e.preventDefault() (links work but won't be optimized until JS loads)
- Generate types based on routes directory structure
- Implement service worker for client side pre rendering
- Fallback to normal worker if service work unavailable
- Use nginx as self-hosted server instead
- DB integration
- FoundationDB