Allow extensions to offer home page (and preferences?)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 106
- Forks
- 52
- Avg merge
- 13h 35m
- Merged PRs (30d)
- 10
Description
Extensions which provide views in the data browser world should be able not only to register their views, and they mintNew() functionality, but also components for a person’s home page for others to see, and maybe (less obviously) a component for the person's private preferences.
(The preferences UI could be embedded in the app itself, where the user knows how to find it. the home page things which other users see on YOUR home page -- your blogs, your bookmarks, etc -- need to be injected there.)
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 by tracing how extensions register views and expose mintNew() in solid-panes. Clarify whether extensions should provide public home-page components, private preference components, or both, and how the app would place them. Done means an agreed extension interface and documented behavior for rendering each component.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100