Guide/Lists and data

One price changed, changed everywhere.

"Your menus, opening hours, prices or events, kept in one place. Show a list on any page: change it here, every page updates." That is the Content section's promise, and it holds.

Spreadsheet editingMenu importAirtable, CSV, API

The problem Content solves is as old as shop windows: the same price lives on the page, on the paper menu and on the Instagram background, and one of the three is always wrong. With a list, you fix one cell: the page follows. The blocks that read these lists are described in Your data; this page takes care of the lists themselves and their sources.

Create a list #

The Content section offers ready-made templates: Menu, Opening hours, Events, Products, Team, Prices, or a Blank list. Each template arrives with its columns already in place: the menu with dish, description and price; the team with name, role and photo. Rename, add or delete columns as you like.

Column typeWhat it's for
Text / Long textNames, descriptions, notes.
Price / NumberPrices aligned and sorted correctly.
ImageThe photo of the dish, the product, the person.
LinkThe "learn more" or "book" destination of each row.
Date / TimeEvents, opening hours.
Yes / NoThe "available", "new", "vegetarian" labels.

Edit like a spreadsheet #

Content: Seasonal menu
DishDescriptionPrice
12 €
9 €
14 €

Click a cell, type: saved automatically.

Editing happens on the page, cell by cell, with no "save" button: every change is saved continuously.

"Click a cell to type: changes are saved automatically." Add rows in one click, move them, empty the list. Deleting a list warns you honestly: "the blocks and sections using it will be hidden". Nothing is lost silently.

Import a menu #

The paper menu already exists? Have it read: upload a photo (JPG, PNG, WebP up to 8 MB), a PDF (up to 10 MB), a text file, or paste the content directly ("Read my menu..."). The reader proposes each dish in a review grid: section, dish, description, price. "Uncheck what you don't want, fix names or prices before importing." Nothing enters your list without your approval, and the number of imports per month is displayed.

Import destination: a new list, or an existing menu list you add to.

Clean photo, clean import

For a flawless read: a well-lit photo, the menu flat, sections visible. The review grid catches small mistakes: you approve, the import only proposes.

Show a list on a page #

Three ways, depending on the block:

  • The Content block shows any list as a table, cards, a list, a gallery or a menu layout: it's the one to pick for teams, events, products. Full settings in Your data.
  • The Opening hours and Menu blocks accept the "Fill from Content" checkbox: "keep this block up to date from one of your lists: change the list in Content, the block follows." Your opening hours then live in exactly one place.
  • Page sections with repeated cards (team, services, FAQ) can also pull their cards from a list.

In every case, the link is made through the "Fill from Content" box: pick the list, and for the Menu and Opening hours blocks, say which column goes in which slot (the dish, the price, the description). A linked block shows an "Edit the rows" link that takes you back to the list.

Your data elsewhere #

"Already keeping your menu, prices or products in Airtable, a CSV file or an API? Connect it once, show it on any page." The connections section builds the bridge; the Connected source block displays the result.

Create a connectionPick the type (Airtable, CSV, API), paste your credentials, save. Credentials are stored encrypted and never shown in clear text again after saving.
Test connectionA button checks right away: "connection OK, X bases found" or "X rows, Y columns". The status of each connection (last test OK, in error, never tested) stays visible.
ReuseOne connection feeds as many blocks as you like: the menu and the storefront can read the same base without retyping anything.
Freshness"Data is refreshed every X minutes", and the editor's Refresh now button forces an immediate re-read before publishing.
If the source goes downTwo behaviors to choose from, per block: show your fallback text, or hide the block. You decide what looks best for your visitors.

Insert a field into a text #

Pages that carry a data block gain a Data tab with a discreet setting: field insertion. The principle: in the title or text of any block on the page, a field in double curly braces is replaced with the value of the displayed row. "Use {{Field}} in the title, text or address of any block on this page." Example: a section title reading "Today's menu: {{Dish}}" updates with the row's value, block after block.

Data fields and merge tags look alike (double braces) but do not read the same source: a {{Dish}} field comes from the row your list displays, a {{name}} tag comes from the visitor's address or from a built-in value. Data blocks keep their own field system, described here; for tags, see Merge tags.

Frequently asked questions #

How many lists can I have?

As many as your business calls for: one per topic is the right rule (menu, hours, team), rather than a single do-everything list. Lists are read live on every visit: no cache to clear.

Can one list serve several pages?

Yes, that's the whole point: the same list feeds as many blocks and pages as you want. One correction, and every page follows.

Is my Airtable data copied into Fastpage?

The block reads your source at regular intervals and shows the result on your page; your base stays at Airtable, the source of truth. Fix something there, and the page follows on the next pass.

Can I sort or filter what the block shows?

Yes: both data blocks offer sorting (column and direction) and a filter ("only rows where the column contains / is / is not / is filled..."), plus a maximum number of rows. See the settings in Your data.