Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Rename hamburger's Hour of Code / Beyond Code.org to CodeAI branding - #74139

#74139
Open
stephenliang wants to merge 4 commits into
stagingcode-dot-org/code-dot-org:stagingfrom
stephen/hamburger-codeai-rebrandcode-dot-org/code-dot-org:stephen/hamburger-codeai-rebrandCopy head branch name to clipboard
Open

Rename hamburger's Hour of Code / Beyond Code.org to CodeAI branding#74139
stephenliang wants to merge 4 commits into
stagingcode-dot-org/code-dot-org:stagingfrom
stephen/hamburger-codeai-rebrandcode-dot-org/code-dot-org:stephen/hamburger-codeai-rebrandCopy head branch name to clipboard

Conversation

@stephenliang

@stephenliang stephenliang commented Jul 27, 2026

Copy link
Copy Markdown
Member

The hamburger menu's signed-in (teacher/student) "Teach" submenu still said "Hour of Code" (linking to the legacy hourofcode.com campaign site) and "Beyond Code.org", unlike the signed-out marketing nav's already-renamed "Hour of AI" entry added in #74042. This retargets that hamburger entry to the same /hour-of-ai destination and renames the sibling label to match, on both the Rails-rendered dashboard header and the Vite frontend/apps/studio header.

Links

  • Jira:

Testing story

  • dashboard/test/integration/header_test.rb's Teach-submenu assertions updated to the new label/href pairs; ran via bundle exec spring testunit test/integration/header_test.rb — 20 tests, 0 failures.
  • yarn typecheck in frontend/ — 20/20 tasks passing, including @code-dot-org/studio.
  • ./tools/hooks/pre-commit clean.
  • Manually confirmed no other config, locale, or code reference to the removed educate_hoc key remains.

Deployment notes

Standard merge-and-deploy; no migrations or flags involved.

stephenliang and others added 2 commits July 27, 2026 11:23
_header renders this file via File.read + inline, so a mid-deploy
process can pair its old compiled template (no :marketing_nav local)
with the new file and raise NameError on every header render until
restart. local_assigns is nil-safe across the skew, matching
user_header.haml.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…deAI branding

The signed-in teacher/student hamburger's Teach submenu still linked to
the legacy hourofcode.com campaign and said "Beyond Code.org", unlike the
signed-out marketing nav's already-renamed Hour of AI entry. Retarget the
hamburger entry to /hour-of-ai and rename the sibling label to match.
@stephenliang
stephenliang changed the base branch from stephen/hamburger-local-assigns to staging July 27, 2026 19:58
@stephenliang
stephenliang marked this pull request as ready for review July 27, 2026 19:59
@stephenliang
stephenliang requested a review from a team as a code owner July 27, 2026 19:59
GLOBAL_NAV hardcoded //code.org, but marketingUrl is brand/environment-aware
and already used by the sibling signed-out-marketing nav entry. Since it
needs siteConfig fully initialised and test mocks in place, GLOBAL_NAV
becomes a lazily-called buildGlobalNav(), matching buildMarketingGlobalNav
and getFooterLinks.
…marketingUrl

Every //code.org-hosted href in buildGlobalNav, STUDENT_MENU_ITEMS,
TEACHER_MENU_ITEMS, and CREATE_MENU_ITEMS was hardcoded, unlike the already
brand/environment-aware buildMarketingGlobalNav. Since marketingUrl needs
siteConfig fully initialised and test mocks in place, the three static
arrays become lazily-called builders (buildStudentMenuItems,
buildTeacherMenuItems, buildCreateMenuItems), matching the established
buildMarketingGlobalNav/getFooterLinks pattern. Add config.test.ts to pin
every entry to siteConfig.marketingUrl and guard against future //code.org
regressions.
@github-actions

github-actions Bot commented Jul 27, 2026

Copy link
Copy Markdown

🖼️ Storybook Visual Comparison Report

⚠️⚠️⚠️ Detected Storybook eyes differences, see report!

A difference was found in our Storybook front-end visual comparison testing against the staging baseline.
This difference was detected in Applitools Eyes and is viewable in the link above.

Remediation steps:

  1. Open the report
  2. Determine whether the differences are expected based on this PR's changes
    a. If expected: Before merging this PR, accept the new baselines and re-run this action, it should pass.
    b. If not expected: Push updates to this PR to correct the differences.

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.

2 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.