chore: migration of website repository#2606
Draft
sdirix wants to merge 211 commits into
Draft
Conversation
sdirix
commented
Jul 23, 2026
sdirix
commented
Member
- Moves https://github.com/eclipsesource/jsonforms2-website into this repository, preserving history
- Adds a release-website workflow
The DocPage does not rely on using groupByParent anymore (which should be removed entirely anyway, as it's seems broken, e.g. when filtering via useMenus). An search bar has been added to the SidebarLayout component.
- review feedback
* Update to JSON Forms 3.4.0 and update material deps * Update docusaurus to latest version 3.5.2 * Fix build command in readme * Update API doc for previously existing packages * Add API docs for new renderer set vue-vuetify * Adapt docs for vue-vuetify integration into the main repo * Add release news for 3.4.0 * Fix broken anchors
The CSP needs to be updated whenever the Cloudflare scripts have different content.
The table of supported options for the date picker now correctly lists 'day' instead of 'date'
- Add news - Update dependencies to 3.4.1
Add additional project for react renderers - at the moment the new set is antd but it differs from the one provided by GX Labs
- Update to JSON Forms 3.5.1 - Update API docs - Add release news for 3.5.0 Also updates to latest Docusaurus which fixes search
The generated API docs contain inline scripts, inline styles and data sources. This adapts the Netlify configuration to serve a more relaxed CSP for them.
Fixes an issue in which nested links were not applied to the current route as it did not end in slash. This lead to invalid links and 404 errors when following such links. See eclipsesource/jsonforms2-website#305 for more information.
The GH action we use to daily check our website for issues did no longer work as its implementation is incompatible to the latest Ubuntu (24.04) default settings. Pins the Ubuntu version to 22.04 to fix the issue for now.
Add library by Gérard Paligot
…ailable publicly anymore
* Add release notes for 3.6.0 * Update JSON Forms dependencies to 3.6 * Update api docs * Update node version in .nvmrc to Node 22 * Fix next version calculation by ignoring tag `vv3.5.0-beta.2`
…#278) Closes eclipsesource/jsonforms2-website#270 --------- Co-authored-by: Stefan Dirix <sdirix@eclipsesource.com> Co-authored-by: Lucas Koehler <lkoehler@eclipsesource.com>
* Add Release 3.7.0 news * Update API docs for 3.7 * Update to JSON Forms 3.7 and MUI 7 * Update docusaurus to latest version 3.9.2 * Update vulnerable dependencies via npm audit fix
- Create .prompts/project-info.prompttemplate with repository architecture - Create CLAUDE.md including build instructions - Include guidance to always build and test changes
Removed caution note about SemVer conventions.
* Update to JSON Forms 3.8.0 * Update docusaurus to 3.10.1 * update api docs for 3.8 * add news for 3.8.0 release
The website history was merged under website/ (see the preceding merge commit). This commit adapts it to live inside the monorepo: - website: add an env-gated webpack alias (JSONFORMS_LOCAL=true) so the site can render against the monorepo's locally built @jsonforms/* packages; add start:local / build:local scripts. Default builds still use the published versions, so CI and production are unaffected. - ci: add .github/workflows/website.yaml to build the site on website/** changes (verify only, never deploy); exclude website/** from the library CI matrix. - publish: trigger a Netlify build hook on stable releases only, so the site is published against the latest stable release and never on regular pushes (no rolling website). - netlify: move config to the repo root with base=website and an ignore rule scoping deploy previews to website/ changes. - copy-docs.sh: default the source repo to the monorepo root. - move the daily console-error check workflow to the repo root and refresh its stale action versions.
Standalone, manually-triggered workflow that pins the website's @jsonforms/* dependencies to a given stable release, verifies the site builds, pushes the bump, and triggers the Netlify deploy. Kept separate from publish.yaml so a website failure never blocks a published npm release and the site stays independently redeployable. The optional regenerate_docs input rebuilds the typedoc API docs from the current state of master (no tag checkout) and commits the refreshed website/static/api together with the pin, replacing the manual copy-docs step. Run it right after a stable release, while master still matches the released code. Drop the deploy-hook trigger from publish.yaml in favor of this workflow: it fired before the website's dependencies were bumped, so it deployed the site against the previous release. release-website is now the single deploy path; netlify.toml's comment points at it.
❌ Deploy Preview for jsonforms-examples failed.
|
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
20 participants
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.