gramlot.

Documentation / Code / Community

From first look
to first page.

Start in the gallery, choose a host, then use the reference for the details. Each part of the project has its own repository and Read the Docs manual.

Read the core manual ↗Choose a server →

The four product repositories

Find the right guide.

Gramlot core

Page authoring, Source, Data, bindings, controllers, components, validation, styling and inspection.

Read the Docs ↗GitHub ↗

Developer tools

Take the inspector
into DevTools.

The gallery inspector is built in. The Chrome extension is a separate installation.

Download the extension ZIP from GitHub Releases. Extract it, open chrome://extensions, enable Developer mode, and choose “Load unpacked”. Select the extension directory containing manifest.json.

The published extension documents its supported origins and local-file permissions. Follow those instructions rather than assuming it has access to every site.

Extension releases ↗Installation guide ↗

Packages

Official distributions.

Follow the installation and update guide for the selected environment. Package versions belong in their repository READMEs and release notes.

How do I report a problem?

Use the relevant GitHub repository. Include the host, installed versions, a small reproducible example and the behavior you expected. A gallery lesson is a useful starting point.

Where do I see what is coming next?

The roadmap overview distinguishes available components from planned work. It is a direction of development, not a delivery schedule.

Can I use the gallery without installing Python or Node?

Yes. Use either public gallery, or download the serverless ZIP, extract it and open index.html. The offline version executes JavaScript in browser Workers.

CONTINUE HERE

Stay for the explanation. Leave when you are ready to build.

From a field to a useful application.Understand what each piece is for.Questions before you build.