Skip to content

Add a Decorator Kit (Beta) intro page for the CMS - #8

Merged
chorta merged 1 commit into
mainfrom
claude/decorator-kit-beta-docs-600327
Oct 2, 2026
Merged

chorta merged 1 commit into
mainfrom
claude/decorator-kit-beta-docs-600327

Conversation

@chorta

@chorta chorta commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

What

A ready-to-paste page body introducing the Decorator Kit as a beta, for a Decorator 5 CMS page (e.g. on developer.ucsd.edu):

  • user-guide/decorator-kit-beta-body.html: canvas-only HTML, with no header, nav, footer, <style> block, or inline styles.
  • user-guide/css/kit-beta.css: the page's stylesheet.

The page covers:

  • What the kit is
  • How it differs from the ucsd-decorator-v5 npm package
  • A quick start
  • init vs. add
  • Upgrading with npm install --save-dev ucsd-decorator-kit@latest + sync, plus the sync, check, drift, and verify commands
  • The "help me get started" interview

It sends readers to the GitHub README for the full, current documentation.

Why

We want a short public landing page for the kit, in the style of the official Decorator docs. A first version that used only Decorator classes looked too plain, so this one takes its look from tritonai.ucsd.edu and the Developer Guide:

  • From TritonAI: the gold-topped sand feature card, the navy gradient section, and cards with colored top borders.
  • From the Developer Guide: numbered steps and command blocks with a Copy button.

For reviewers

  • Scoping: every CSS rule sits under main#main-content .kb, and no rule names a chrome class or id. The tinted sections are rounded panels inside the content column, with no full-bleed tricks, so the page ground isn't painted. Fonts are Roboto and Teko only, colors are UC San Diego brand values, and there are no -success, -info, -warning, or -danger classes.
  • Layouts: a container query stacks the side-by-side sections based on the content column's width. I checked the page in full-width and two-column Decorator layouts and at 375px: no horizontal overflow.
  • Copy buttons: they load the live developer.ucsd.edu/design/decorator/user-guide/js/guide.js, the same script as the Developer Guide. Without it, the page still works. In the preview browser, the script loaded and wired the buttons, but I couldn't confirm the clipboard write there.
  • Deploying: upload kit-beta.css alongside the page and point the <link> at the top of the body to it. If the CMS strips body <link> tags, add the file through the page or site CSS setting instead. The comment at the top of the HTML explains this.
  • Accuracy: the content matches the current README (kit 2.4.0, Decorator 5.0.4). The terminal panel in the hero is a trimmed version of init's real output.
  • Tests: npm test passes. These files aren't compiled into any rule file.

🤖 Generated with Claude Code

A canvas-only HTML fragment to paste into the body of a Decorator 5 CMS
page, introducing the kit as a beta: how it differs from the
ucsd-decorator-v5 package, a quick start, init vs. add, upgrading with
sync, and the "help me get started" interview. It points to the GitHub
README as the full and current documentation.

The look borrows from tritonai.ucsd.edu and the Developer Guide, so it
ships with css/kit-beta.css. Every rule is scoped under
main#main-content .kb, no rule paints the page ground or bleeds past its
box, and fonts stay Roboto and Teko. Side-by-side sections stack on the
content column's width via a container query, so the page works in both
full-width and two-column layouts. Copy buttons reuse the live
Developer Guide guide.js.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chorta
chorta merged commit db232cc into main Oct 2, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant