Docs: missing pieces

Comienza revisando el ejemplo mínimo propuesto en page/index.html y page/index.php; después, inspecciona la estructura de documentación existente antes de organizar los temas enumerados. El issue abarca Getting Started, instalación, User Guide, tutoriales y Further Reading; se considerará completado cuando las secciones y explicaciones solicitadas estén documentadas con enlaces y ejemplos adecuados.

Overview:

Explain the following:

• the difference between Page View, Page Logic, API View/Logic, components, partials.
• HTML is concatenated/assembled before DOM processing.
• How the DOM document is manipulated with data-bind.
• PHP is optional and added only when needed by the developer.
• Dynamic route filenames can be used with @.
• Magic files like _header, _footer, and _common, and when not to use with partials.
• Logic methods go, do_* with links to read more about advanced usage (go_after, for example).
• Where client-side build tooling fits.
• Dependency injection and logic files (lazy loading).
• Database access.
• Object oriented alternatives to GLOBAL usage.

A minimal example project can be shown with page/index.html and how to manipulate the page in page/index.php.

Next page: Getting started to get set up for development quickly.

Getting started:

• I want to build my first webpage.
• I want to make my page dynamic.
• I want to build an API.
• I want to update part of a page.
• I want reusable page parts.

Next page: information about installation on different platforms, or using gt commands

Installation:

gt commands:

Blueprints:

After this, Tutorials section.

User guide:

• Request-response lifecycle
• Running your application (gt run = serve + build + cron)
• Project layout
• Application architecture
• Web servers (inbuilt, nginx, lighttpd, apache)
• URIs
• Page View
• Dynamic URIs
• Headers and footers
• Partial template pages
• Page Logic
• Protected globals
• User input
• Cookies
• Sessions
• Dynamic pages with the DOM
• Custom HTML components
• Database
• Client side assets
• API development
• Security
• Configuration
• Client side build system
• Coding styleguide

Further reading:

• Distinct Logic Authority
• SPA, MPA and Hypermedia (SPAs break hypermedia, MPAs often have less UX, multi-pass rendering)
• Fluid User Experience with Flux
• Speed & benchmarks
• Caching
• Service workers
• Repository-Entity pattern