amagaki
amagaki copied to clipboard
A high-performance TypeScript static website generator for building highly-interactive websites. Localization inbuilt. Flexible URLs. Content managed and templates separated.
Adds a hook for amagaki that triggers before the manifest is built (allowing the plugin to generate more content outside of normal routes and after all routes have been processed)....
I was writing a `LitEnginePlugin` using the same format as the `PreactEnginePlugin` (referencing [this code](https://github.com/blinkk/amagaki/blob/main/packages/amagaki-engine-preact/src/preact-engine.ts)) and when I import and try and use render from `@lit-labs/ssr` it breaks and shows...
Right now we have a shortcuts menu on the page builder plugin but would like to evolve this to a "control panel" to house the available features to the user....
The environment isn't properly updating the generated `Url` objects throughout a site
When a project is running in editor.dev the editor is going to communicate with the preview using `postMessage`. The JS for the page builder can use that information to interact...
Step 1: Timestamp added to staging showing when the page was last built (but this will show anything) Step 2: add the ability to specify what data sources were updated...
Add the ability to see the current screen size without opening devtools or howbigismybrowser.com on staging
“File bug” icon → this can already include the device, screen size, and browser info
Add the ability to view image attributes (dimensions, size, file type) to the client or design team on staging. This should also be included in our inspector feature.