[DRAFT]: Added features from issue: 6042

[nairaj2]

Summary

Adds frontend support for organizations in Studio:

• Adds a My organizations navigation item.
• Adds an organizations page listing organizations available to the user.
• Adds a page for creating organizations.
• Adds an organization details page with channels and users.
• Adds an organization filter and organization creation shortcut to My channels.
• Uses KDS components, Composition API composables, and existing organization API endpoints.
• Adds frontend tests covering organization listing, creation, details, filtering, and navigation.

This is a frontend-only change and builds on the organization models and endpoints introduced previously.

References

• Closes [#6042](Organization Pages #6042)
• Builds on [#6126](Add Organizations' User Invitation UI #6126)
• [Organization page designs](https://github.com/user-attachments/files/30723794/pages.pdf)

Reviewer guidance

To verify manually:

1. Log in and open My organizations from the navigation bar.
2. Confirm that organizations available to the user are displayed as portrait cards.
3. Select an organization and verify its details, channels, and users.
4. Select New organization, complete the form, and confirm that the new organization is created and opened.
5. Return to My channels and verify that:
   • The organization filter appears at the top right.
   • The filter does not expand across the page.
   • The Create button beside the filter opens the new organization page.
   • Selecting an organization filters the channel cards.
   • Clearing the filter restores all editable channels.
   • The selected filter is preserved through the URL and browser navigation.
6. Check the layouts at desktop and mobile widths.

Automated verification performed:

node node_modules/jest/bin/jest.js \
  --config jest_config/jest.conf.js \
  contentcuration/contentcuration/frontend/channelList \
  --runInBand

All 24 channel-list test suites and 215 tests pass. Pre-commit frontend checks also pass.

The organization channel list depends on channel responses containing organization association metadata. If that metadata is unavailable, the details page displays an unavailable-state message rather than showing unrelated channels.

Because this PR changes several layouts and workflows, screenshots of My channels, My organizations, and the organization details page would help review.

AI usage

I used OpenAI Codex to analyze the issue, design document, and reference PR; implement the organization pages and channel filter; and write frontend tests. I reviewed and refined the generated changes against the project conventions, corrected invalid API query behavior found during local testing, limited the implementation to frontend files, and ran the focused and full channel-list test suites plus pre-commit checks.

[learning-equality-bot]

👋 Hi @nairaj2, thanks for contributing!

For the review process to begin, please verify that the following is satisfied:

• Contribution is aligned with our contributing guidelines

• Pull request description has correctly filled AI usage section & follows our AI guidance:

  AI guidance

  
  

  State explicitly whether you didn't use or used AI & how.

  If you used it, ensure that the PR is aligned with Using AI as well as our DEEP framework. DEEP asks you:

  • Disclose — Be open about when you've used AI for support.
  • Engage critically — Question what is generated. Review code for correctness and unnecessary complexity.
  • Edit — Review and refine AI output. Remove unnecessary code and verify it still works after your edits.
  • Process sharing — Explain how you used the AI so others can learn.

  
  

  Examples of good disclosures:

  "I used Claude Code to implement the component, prompting it to follow the pattern in ComponentX. I reviewed the generated code, removed unnecessary error handling, and verified the tests pass."

  "I brainstormed the approach with Gemini, then had it write failing tests for the feature. After reviewing the tests, I used Claude Code to generate the implementation. I refactored the output to reduce verbosity and ran the full test suite."

Also check that issue requirements are satisfied & you ran pre-commit locally.

Pull requests that don't follow the guidelines will be closed.

Reviewer assignment can take up to 2 weeks.