Implement About Us Page

[willy1989cv]

Issue: https://github.com/datopian/City-of-Malmo-Open-Data-Portal/issues/37

Changes: added content for en and sv

Summary by CodeRabbit

• Documentation
  • Updated the About Us page with introductory content describing local data production and storage practices.
  • Added information about open data's purpose and its role in enabling reuse by citizens, researchers, media, and businesses.
  • Made content available in English and Swedish languages.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
malmo-data-portal	Ready	Preview, Comment	Feb 10, 2026 10:33am

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Adds English and Swedish about-us content describing Malmö's open data initiatives, and integrates a markdown rendering function into the about-us page to dynamically display the localized content.

Changes

Cohort / File(s)	Summary
Localized About-Us Content content/about-us/en.md, content/about-us/sv.md	Added introductory paragraphs in English and Swedish describing data production, storage, and the role of open data in enabling reuse by citizens, researchers, media, and businesses.
About-Us Page Component src/app/[locale]/about-us/page.tsx	Integrated markdown content fetching via getMarkdownContent function and replaced empty fragment with rendered content div. Updated container styling from relative -mt-6 to relative py-10 to accommodate rendered content.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 Open data hops along,
In English and Swedish song,
Markdown content now displays,
Citizens learn in brilliant ways,
Reuse blooms where data plays! 🌱

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title 'Implement About Use Page' appears to be a typo ('Use' should be 'Us') and is only partially related to the changeset, which primarily adds content/translations rather than implementing a page.	Correct the typo to 'Implement About Us Page' or use a more accurate title like 'Add About Us page content in English and Swedish' to better reflect the actual changes (content additions and page integration).
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/about-us-page

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@src/app/`[locale]/about-us/page.tsx:
- Line 15: The page currently assigns const content = getMarkdownContent(...)
which returns a Promise, so change the page component to be async (e.g., export
default async function Page(...) or add async to the enclosing function) and
await the call: const content = await
getMarkdownContent(`about-us/${locale}.md`); ensure you update any
callers/exports to support an async server component and keep references to
getMarkdownContent and content consistent.

🧹 Nitpick comments (2)

src/app/[locale]/about-us/page.tsx (2)

19-19: Raw markdown is rendered as plain text — no HTML conversion.

The content is inserted directly into a <div> without any markdown-to-HTML processing. Currently the .md files contain only plain paragraphs so this won't cause visible issues, but if any markdown syntax (headings, links, lists, bold, etc.) is added later, it will render as raw text. Consider using a library like react-markdown or converting to HTML with remark/unified before rendering.

Example using dangerouslySetInnerHTML with a remark pipeline

+import { remark } from "remark";
+import html from "remark-html";
+
 // inside the component, after awaiting content:
-       <div>{content}</div>
+       const processed = await remark().use(html).process(content);
+       const htmlContent = processed.toString();
+       // ...
+       <div dangerouslySetInnerHTML={{ __html: htmlContent }} />

Alternatively, use react-markdown for a safer approach without dangerouslySetInnerHTML.

---

12-12: Function is named SearchPage but this is the About Us page.

Looks like a copy-paste artifact. Consider renaming for clarity.

Proposed fix

-export default async function SearchPage({ params }: Props) {
+export default async function AboutUsPage({ params }: Props) {