UX: add a site footer (docs, jobs, imprint)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Part of the UX backlog. Raised in a planning session on 2026-06-11 against the old static site; re-scoped here for course-v2.
There is currently no footer at all — the page ends with content.
Scope
Add a site footer rendered on every page.
Links to include:
- Nextcloud developer documentation
- Nextcloud jobs
- Imprint / legal
- The course repository
Where
A new components/Footer.tsx, rendered from app/layout.tsx so it applies to the catalog, level and module pages alike. Note that ModulePlayerClient uses a min-h-screen flex flex-col layout with an overflow-hidden content area, so check the footer does not fight the module player's scrolling.
Out of scope
Anything that needs a CMS or per-locale content. Plain links.
Done when
A footer appears on all three page types, the links resolve, and the module player still scrolls correctly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Create components/Footer.tsx and render it from app/layout.tsx so it appears on the catalog, level, and module pages. Check the ModulePlayerClient min-h-screen flex flex-col layout and overflow-hidden content area while integrating it. Done means the footer appears everywhere, all four links resolve, and the module player still scrolls correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 82/100