chore(api,client): move most certs to legacy #63140

Sembauke · 2025-10-28T11:33:58Z

Checklist:

I have read and followed the contribution guidelines.
I have read and followed the how to open a pull request guide.
My pull request targets the main branch of freeCodeCamp.
I have tested these changes either locally on my machine, or GitHub Codespaces.

Closes https://github.com/freeCodeCamp/fCC10/issues/117

huyenltnguyen

I think we probably need to add "Legacy" next to the old "Responsive Web Design" and "Back End Development and APIs".

Screenshot

I'm more concerned about RWD as it's going to collide with the new one (v9). We aren't showing the v9 Back End yet, so it's fine for now, although we've moved the super block to /archive so technically we can add "Legacy" to it.

shared/config/certification-settings.ts

huyenltnguyen

I went ahead and slapped the "Legacy" prefix on all the old certs and super blocks.

We're going to end up with two "Legacy JavaScript Algorithms and Data Structures" sections, though 🫤. Maybe that's acceptable? The differences are visible in the super block content and certification projects.

Archive page - Screenshot

Settings page - Screen recording (because I can't screenshot that gigantic list)

Screen.Recording.2025-10-31.at.01.18.49.mov

huyenltnguyen · 2025-10-30T18:27:27Z

cc'ing @moT01 for thoughts.

moT01 · 2025-10-30T21:28:21Z

They look good after just a quick glance at the screenshots. Looks like e2e is complaining about finding two elements using the JS title selector. Could probably just fix that in the test, but I wonder if we should put an alternative in front of the RWD and JS at the bottom - or maybe something in parenthesis after - maybe "Original Responsive Web Design" or "Responsive Web Design (First Generation)" or "Legacy Responsive Web Design (Classic)". Perhaps we need a better naming scheme than just putting legacy in front of everything. I'm with with doing that for now though - any thoughts?

ilenia-magoni · 2025-10-31T11:35:32Z

maybe we could add the year of release to the title to distinguish between the legacy certs of the same name?

huyenltnguyen · 2025-10-31T11:58:51Z

Yeah, I think adding the year could work 👍 It helps show how old the super block is, and hopefully nudges campers toward newer content.

We could add that to all legacy certs, or just for the certs with the same/similar name:

Legacy Responsive Web Design (year)
Legacy JavaScript Algorithms and Data Structures (year)

ShaunSHamilton · 2025-10-31T12:14:35Z

Is "year" preferred over "version"? E.g. JavaScript Algorithms and Data Structures v1 (of course, it will be odd to skip straight to 7 🤷‍♂️ )

huyenltnguyen · 2025-10-31T12:24:32Z

The version in the title wouldn't match the one in the slug, then. But do we care?

ShaunSHamilton · 2025-10-31T12:50:39Z

The version in the title wouldn't match the one in the slug, then. But do we care?

I am suggesting the title be made to match the slug.

huyenltnguyen

Edit: Ignore this, see #63140 (comment) instead.

~~Added version to Legacy JS and Legacy Data Viz.~~

Screenshots

client/src/components/settings/certification.tsx

shared/config/certification-settings.ts

…nto pr/63140

huyenltnguyen · 2025-11-01T21:55:26Z

Sorry for the noise. That was me not being able to make up my mind.

I decided to proceed with the following approach:

Add version if the name is the same or similar, so it's easier to tell them apart.
- I'm not using year here just because I'm lazy and don't want to dig back through the release dates
Add "Legacy" if a newer version of the cert is about to be released.
- The other certs can remain current until their replacements are ready or we decide to deprecate them.

Screen shots

moT01

Well, I wouldn't say I love the naming scheme, but I don't really have any better suggestions. I tried making the V# with a lowercase v, and putting it in parenthesis. Didn't really help.

Other than that, we could maybe add "Legacy" back to the Front End Libs, Relational Database, and Backend API's certs - since we plan to have new versions of those coming. Or, we can do that later.

To keep things moving, I would be fine getting it in like this. Gonna bring it up in the meeting tomorrow and see if anyone else has any ideas.

huyenltnguyen · 2025-11-04T23:00:08Z

we could maybe add "Legacy" back to the Front End Libs, Relational Database, and Backend API's certs - since we plan to have new versions of those coming.

Some campers want to list these certs on their resumes, and it wouldn't feel fair to mark the certs as less valuable / less relevant while the new versions aren't out yet. This is why I went back-and-forth with the changes.

We could add "Legacy" to Front End Libs and RDB, but I'm not sure about the Back End one since it's not going to be ready soon.

chore: remove most certs to legacy

8d81be2

github-actions bot added the scope: tools/scripts Scripts for supporting dev work, generating config and build artifacts, etc. label Oct 28, 2025

Sembauke marked this pull request as ready for review October 28, 2025 12:09

Sembauke requested a review from a team as a code owner October 28, 2025 12:09

huyenltnguyen reviewed Oct 28, 2025

View reviewed changes

shared/config/certification-settings.ts Show resolved Hide resolved

shared/config/certification-settings.ts Show resolved Hide resolved

huyenltnguyen changed the title ~~chore: remove most certs to legacy~~ chore(client): move most certs to legacy Oct 28, 2025

moT01 added the status: waiting update Is awaiting update, after feedback or request for changes label Oct 29, 2025

huyenltnguyen self-assigned this Oct 30, 2025

huyenltnguyen added 3 commits October 31, 2025 00:33

fix: reorder the cert list

2eaa893

fix: mark all legacy certs as legacy

ecb0626

fix: mark all legacy super blocks as legacy

a0e7efe

github-actions bot added platform: learn UI side of the client application that needs familiarity with React, Gatsby etc. scope: i18n language translation/internationalization. Often combined with language type label labels Oct 30, 2025

feat: add cert title to v9 certs

a2e8dea

huyenltnguyen reviewed Oct 30, 2025

View reviewed changes

huyenltnguyen added status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. and removed status: waiting update Is awaiting update, after feedback or request for changes labels Oct 30, 2025

fix: add version to cert title

5a9b89f

huyenltnguyen reviewed Oct 31, 2025

View reviewed changes

client/src/components/settings/certification.tsx Show resolved Hide resolved

shared/config/certification-settings.ts Show resolved Hide resolved

huyenltnguyen added status: waiting update Is awaiting update, after feedback or request for changes and removed status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. labels Oct 31, 2025

huyenltnguyen added 2 commits November 1, 2025 05:55

update tests

6172381

rename

1d7d8d1

Merge branch 'main' of https://github.com/freeCodeCamp/freeCodeCamp i…

8fe1ebb

…nto pr/63140

huyenltnguyen force-pushed the chore/move-certs-to-legacy branch from d5ffd38 to 8fe1ebb Compare October 31, 2025 23:51

github-actions bot added the platform: api Server application that needs familiarity with Express, Fastify, MongoDB etc. label Nov 1, 2025

huyenltnguyen force-pushed the chore/move-certs-to-legacy branch from 4d5f324 to a0b1a43 Compare November 1, 2025 11:18

fix: cert order on profile page and correct cert names

06db439

huyenltnguyen force-pushed the chore/move-certs-to-legacy branch from a0b1a43 to 06db439 Compare November 1, 2025 12:30

huyenltnguyen added status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. and removed status: waiting update Is awaiting update, after feedback or request for changes labels Nov 1, 2025

huyenltnguyen changed the title ~~chore(client): move most certs to legacy~~ chore(api,client): move most certs to legacy Nov 1, 2025

moT01 self-assigned this Nov 4, 2025

moT01 reviewed Nov 4, 2025

View reviewed changes

moT01 approved these changes Nov 5, 2025

View reviewed changes

moT01 merged commit f5053b2 into freeCodeCamp:main Nov 5, 2025
11 checks passed

Uh oh!

chore(api,client): move most certs to legacy #63140

chore(api,client): move most certs to legacy #63140

Conversation

Sembauke commented Oct 28, 2025 • edited by huyenltnguyen Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

huyenltnguyen left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

huyenltnguyen left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

huyenltnguyen commented Oct 30, 2025

Uh oh!

moT01 commented Oct 30, 2025

Uh oh!

ilenia-magoni commented Oct 31, 2025

Uh oh!

huyenltnguyen commented Oct 31, 2025

Uh oh!

ShaunSHamilton commented Oct 31, 2025

Uh oh!

huyenltnguyen commented Oct 31, 2025

Uh oh!

ShaunSHamilton commented Oct 31, 2025

Uh oh!

huyenltnguyen left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

huyenltnguyen commented Nov 1, 2025

Uh oh!

moT01 left a comment

Choose a reason for hiding this comment

Uh oh!

huyenltnguyen commented Nov 4, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Sembauke commented Oct 28, 2025 •

edited by huyenltnguyen

Loading

huyenltnguyen left a comment •

edited

Loading

huyenltnguyen left a comment •

edited

Loading

huyenltnguyen left a comment •

edited

Loading