Add content to Community page

[jpherr]

Description

The Community page currently has minimal placeholder content, which was required for the launch of something else.

This change updates the content to something more detailed and meaningful.

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Related Tickets & Documents

• Closes Review 'community' page content digital-land#629

QA Instructions, Screenshots, Recordings

Content only update.

Before

After

Added/updated tests?

We encourage you to keep the code coverage percentage at 80% and above.

• Yes
• No, and this is why: Content only update - no functionality
• I need help with writing tests

QA sign off

• Code has been checked and approved
• Design has been checked and approved
• Product and business logic has been checked and proved

[optional] Are there any post-deployment tasks we need to perform?

[optional] Are there any dependencies on other PRs or Work?

Summary by CodeRabbit

• Documentation
  • Updated the Community page with expanded content, including new sections on "Planning data platform" and "Open digital planning" with additional information and external resources for further exploration.

[coderabbitai]

Walkthrough

The Community page content in src/views/community.html is expanded with two new subsections describing the Planning data platform and Open digital planning initiatives, replacing a single paragraph with richer descriptive markup and external links.

Changes

Community page content update

Layer / File(s)	Summary
Community page expanded content src/views/community.html	The Community page markup is expanded to replace the prior single paragraph with two new subsections—"Planning data platform" with a bullet list and "Open digital planning"—each with updated external links.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A community page springs to life,
With platforms and planning, no strife,
New sections bloom, fresh links appear,
Digital openness, crystal clear! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add content to Community page' directly and accurately summarizes the main change in the pull request, which adds expanded content to the Community page section.
Linked Issues check	✅ Passed	The PR successfully addresses issue #629 by preparing and adding reviewed community content as a separate tab with expanded sections on the planning data platform and Open Digital Planning community.
Out of Scope Changes check	✅ Passed	All changes are scoped to the Community page content update as required by issue #629; no out-of-scope modifications are present in this content-only change.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 629-review-community-page-content

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	66.2%	7122 / 10758
🔵	Statements	66.2%	7122 / 10758
🔵	Functions	63.37%	289 / 456
🔵	Branches	77.49%	995 / 1284

File Coverage

No changed files found.

Generated in workflow #1500 for commit daee998 by the Vitest Coverage Report Action

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/views/community.html`:
- Line 17: The anchor element with class "govuk-link" currently displays
"planning.data.gov.uk" but its href points to
"https://design.planning.data.gov.uk/get-involved-in-designing-data"; update the
link text within the <a class="govuk-link"> element (or alternatively change the
href) so the visible text exactly matches the destination (e.g.,
"design.planning.data.gov.uk" or the full descriptive path) to avoid mismatch
and user confusion.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 1bf7eaf6-939f-4141-937b-c3586224b137

📥 Commits

Reviewing files that changed from the base of the PR and between 0fed956 and b8234f7.

📒 Files selected for processing (1)

• src/views/community.html

[gibahjoe]

LGTM