CMS about us page

[wen-2018]

If this changeset needs to go into the FXC codebase, please add the WMO and FXC label.

One-line summary

This PR adds a CMS based about us page.

Significant changes and points to review

Issue / Bugzilla link

https://mozilla-hub.atlassian.net/browse/WT-573

Testing

• http://localhost:8000/cms-admin/
• add new about us page with about slug
• add all sections data using what is currently on https://www.mozilla.org/en-US/
• publish the page
• review content, seciton id, classes, link attributes etc on http://localhost:8000/en-US/about/
• confirm tests logic and coverage

[codecov]

Codecov Report

❌ Patch coverage is 98.41270% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 81.85%. Comparing base (43a679c) to head (f651865).
⚠️ Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
...drock/mozorg/fixtures/showcase_gallery_fixtures.py	93.33%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #17099      +/-   ##
==========================================
+ Coverage   81.74%   81.85%   +0.10%     
==========================================
  Files         174      175       +1     
  Lines        9347     9409      +62     
==========================================
+ Hits         7641     7702      +61     
- Misses       1706     1707       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[stevejalim]

LGTM - one small thing before I approve

Rather than add a new page with the slug of about-2026 You can add a new page at about if you wrap the Django view at

bedrock/bedrock/mozorg/urls.py

Line 24 in 43a679c

path("about/", views.AboutView.as_view(), name="mozorg.about.index"),

in prefer_cms - that'll make the switchover to the new page easier, too.

If you do this, I'll test drive it locally with about as the slug and see if any child pages complain.

[stevejalim]

Thanks for this @wen-2018 - works for me, but I also had to add LeadershipPage an allowed subpage_type so that we can swap the StructuralPage at about for this new page when we are ready to go live -- the child pages of the current about will need to be moved.

Happy to do the swapping over once the content for the new page is populated (we'll have to make it with a different slug (about-new) and then swap them over quickly while the CDN catches requests.)