gramlot.

Course · Lesson 17 of 20

Organize pages and choose a host

Move from one Page to an application while keeping routing, resources and persistence explicit.

Reading · Practice2 sectionsPrerequisites: Save, restore and send Data deliberately
Course contents
Orientation
  1. 01 Install Gramlot and create Hello world
  2. 02 Connect text and colour to Data
  3. 03 Explore Data and Source with the inspector
  4. 04 Use relative and symbolic paths, then dataFormula
  5. 05 Call the server with dataRpc and .remote
Start a project
  1. 01 Create your first project
  2. 02 Read and compose Source
  3. 03 Initialize structured Data
  4. 04 Connect fields and values
Build a form
  1. 05 Accept values, preserve drafts
  2. 06 Declare a calculation
  3. 07 Run an action at the right time
  4. 08 Name behavior and understand lifecycle
Compose an interface
  1. 09 Arrange an application with containers
  2. 10 Style the page you own
  3. 11 Publish messages and ask before acting
  4. 12 Format values without changing Data
Connect services
  1. 13 Call an endpoint
  2. 14 Load a Source fragment
  3. 15 Load Data when it is read
  4. 16 Save, restore and send Data deliberately
Deliver your work
  1. 17 Organize pages and choose a host
  2. 18 Read the JavaScript edition
  3. 19 Deliver the JavaScript edition offline
  4. 20 Explain and change a complete form

Keep responsibilities visible

A project can contain several Page modules and their companion Logic and CSS files. A server adapter connects these pages to the chosen web framework. Keep page behavior in the page and hosting decisions in the host configuration.

The application-index guide describes a reusable index and an installable root. An installed browser window remains connected to its server or export; an installation icon does not by itself make a Python server application run offline.

Use the host your application needs

Uvicorn is the starting point used by this course. Existing applications can use the Django, Flask, FastAPI or Kajenn adapter. Follow the relevant host guide for resources, authentication and request lifetime.

Core, examples and adapter releases have independent versions. For packaged Python installations, update the active environment and restart. Source checkouts also need the documented browser-bundle rebuilds; pulling new files alone does not refresh a running process.

Your turn

Try it yourself

  1. List your hello project’s Page, Logic, CSS and host files and describe each responsibility.
  2. Read the application-index example and identify which configuration belongs to the root.
  3. Use the update guide to write the correct update-and-restart procedure for your own installation.

Check your understanding

Why can a new menu entry appear while the server still serves older behavior?

Show the answer and expected result

Catalogue files, imported Python modules and built browser assets may come from different updates. Stop the old process, update or rebuild through the documented procedure, restart and verify a concrete example. A browser refresh cannot perform those server-side steps.

Working examples and reference