The progress on the ideas page is current - #174
Merged
Conversation
The GuestGraph connector row said connectors were next on the roadmap, which stopped being true when Apaleo was connected. It now names what it reads, and says in the same line that POS, wifi and booking engines are still ahead; a row reading built would claim an estate where there is one PMS. Three numbers beside it were wrong rather than merely dated. Core is 0.19.0 and carries ten types, where the page said 0.4.1 and eight, and the instance is the 125 entities model.json publishes, where the page said 110 pages. That dataset is built at the commit source.json pins, so a reader who opens the file the footer links counts exactly what the sentence claims. The bars are the page's own record of movement since the last update, so data-prev takes the previous data-now on every row: the drawn slice is what moved, and the rows that did not move draw none. Verified: npm run verify, og:check, design:check, pin-check, conventions-sync check and conventions-check all pass; the page rendered at 1100px in both themes and both languages with every bar scrolled to its final state. og.png is unchanged because the card renders the hero, not the part rows; only its sha moved. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The GuestGraph connector row said connectors were next on the roadmap, which stopped being true
when Apaleo was connected. It now names what it reads — reservations and bookings, by webhook and
by full sync — and says in the same line that POS, wifi and booking engines are still ahead. The
label is first one built rather than built, because a row reading built would claim an estate
where there is one PMS. That matches the amendment to the intro talk's status slide in
guestgraph/guestgraph.github.io#84.
Three numbers beside it were wrong rather than merely dated. Core is 0.19.0 and carries ten
types, where the page said 0.4.1 and eight. The instance is the 125 entities
model.jsonpublishes, where the page said 110 pages. That dataset is built at the commit
source.jsonpins,so a reader who opens the file the footer links counts exactly what the sentence claims.
The bars are the page's own record of movement since the last update, so
data-prevtakes theprevious
data-nowon every row: the drawn slice is what moved, and the rows that did not movedraw none. Two CompanyGraph rows moved for reasons outside this diff — the surface type and R17
landing in core, and the instance checks now shipping from meta-model as a required gate.
Two German terms had to be chosen and are worth recording in
GLOSSARY.mdif they are kept:entity as
Entitäthere, and estate asSystemlandschaftin the talk's amended slide. Neither isin the table yet, so neither has a fixed form to follow.
pin-checknotes the model pin is two commits behind. Left alone: pins are editorial, and bothnew numbers are read from the dataset built at the pinned commit, so they are consistent with what
the site serves today.
Verified: npm run verify, og:check, design:check, pin-check, conventions-sync check and
conventions-check all pass; the page rendered at 1100px in both themes and both languages with
every bar scrolled to its final state. og.png is unchanged because the card renders the hero, not
the part rows; only its sha moved.
🤖 Generated with Claude Code