One document per component state. Each file under examples/<name>/<state>.html is a whole page: the standard head, the stylesheet and theme, the scripts the markup needs, and the reference markup as its body. Open one in a browser and it works on its own.
4
5
examples.json lists every example in gallery order, with its states, the scripts each needs, and the state later readers use by default. The example package reads it: example.Load for the manifest, example.Markup for one state's body, example.Document for a whole layout page, and example.Slot to put your own content in a layout's slot.
6
7
The markup was seeded from Rastrillo's design-system gallery at the commit named in hack/seed/README.md, and it is Fiesta's own from here on. Edit a document here and the tests read the change; nothing regenerates it. To reseed from Rastrillo, run hack/seed/run.sh, which rewrites every generated file.
8
9
A layout example is a whole page. Its content region sits between <!-- fiesta:slot --> and <!-- /fiesta:slot -->. The scheme menu's standalone state is the one document whose <html> carries data-rst-scheme-store="local": it remembers the choice in the browser, with no server behind it.
10
11
assets/ holds the four sample pictures the media grid shows. The samples' own picture routes, such as /images/checkout.png, are rewritten to these files. The links a sample keeps, such as /orders/AB3PX, are listed in examples.json as its sampleURLs: the application routes the sample stands for.
amadan