Feature: public profile pages
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 10
- Forks
- 0
- Avg merge
- 2h 52m
- Merged PRs (30d)
- 20
Description
Tier 4 — feature idea
Why
Resources can already be marked public, and shared collections already have public pages — but there is no way to see everything a person shares in one place, and no organic discovery path into the app. It also finally gives DisplayName a purpose.
Evidence
LearnStack.Core/Services/LearningResourceService.cs:189-200—GetPublicResourcesByUserIdAsyncexists and is only reachable through the friends flowLearnStack/Components/Pages/SharedView.razor— the public-page pattern to follow
Sketch
/u/{handle} listing public resources and active shared collections, with opt-in, a unique handle, OpenGraph tags for link previews, and sitemap inclusion.
Depends on
The DisplayName issue — and the handle must not be derived from the email address.
Contributor guide
No contributing guide indexed for this repository
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
Start with LearnStack.Core/Services/LearningResourceService.cs:189-200 and LearnStack/Components/Pages/SharedView.razor to understand public resource lookup and the existing public-page pattern. Review the DisplayName dependency before defining the profile flow. Done means an opted-in, uniquely handled /u/{handle} page lists public resources and active shared collections, with link previews and sitemap inclusion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100