Repository navigation
Migrate TagScript playground to Next.js and Fluid Functionalism - #5
Merged
Merged
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
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.
Replaces the legacy Bootstrap site with a Next.js App Router playground built with TypeScript, Tailwind CSS, Fluid Functionalism, and Bun. Preserves TagScript processing, editable seeds, action/debug inspection, Carl imports, and browser/session storage, with a CodeMirror editor and local script import/export.
Adds a visible light/dark toggle with a persistent preference applied before rendering. The app stays focused on the TagScript workspace, examples, and guide; it does not include a component showcase.
Adds a static export and GitHub Pages workflow. Branches and pull requests validate the build; only
masterdeploys. Before merging, set Settings → Pages → Source to GitHub Actions. Local build and deployment commands are documented in the README.Validation: lint, TypeScript checks, eight unit tests, six Chromium tests, and the production export at
/bTagScriptPlayground. Browser coverage includes execution, network failures, duplicate-request prevention, storage, imports/exports, mobile navigation, and dark-mode persistence. A live request to the existing TagScript engine also succeeded.Processing and Carl imports retain their existing external services and require those services to be available and allow the deployed origin.