life-itself / life-itself/reasoncommons
[inbox] UX ideas about the Reason Commons app(s)
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1
- Forks
- 0
- Avg merge
- 4h 59m
- Merged PRs (30d)
- 11
Description
- Viewer and editor should be split into separate components
- Viewer: standalone, embeddable, even CLI-usable
- Editor: separate concern, possibly a skill or GitHub-native editing
- Deep link to individual trees still missing; hard links needed so trees can be shared directly
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 mapping the current Reason Commons app(s) and how the viewer, editor, and tree URLs are currently organized. Clarify the boundaries for separate viewer and editor components, standalone or CLI use, and direct tree links; done means these responsibilities and sharing behavior are explicitly implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, html
- Domain
- cli, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100