Integrate grist databases into docs (Panographix - HackDays 2025) #1082
Conversation
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
SimonClo
force-pushed
the
feat/grist-database-integration
branch
3 times, most recently
from
386ef73 to
cfc4e0b
Compare
SimonClo
force-pushed
the
feat/grist-database-integration
branch
from
cfc4e0b to
757b776
Compare
|
We are closing the pull requests of the Hackathon 2025, thank you for your contributions 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is a spin-off from #1053
Purpose
Merge the HackDays 2025 “database” prototype into the public Docs repository to kick-start native data-driven capabilities for civil-servant users while preserving Docs’ friendly UX.
Proposal
This PR introduces a new custom block developed during HackDays 2025:
DatabaseBlock: lets authors create a new Grist table or pick an existing one directly from the editor, then display and edit the data inline.Behind the scenes we rely on Grist as a lightweight backend, but the UI hides the Grist complexity so that non-technical agents can stay focused on their documents.
Known limitations / next steps
General cleanup of the code
Authentication: today we pass a hard-coded Grist API token (env var GRIST_TOKEN). We aim to fetch it via OIDC (ProConnect) before merge.
Accessibility review (ARIA roles, colour contrast) still pending.