Design and CSS
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Rough overview/draft of things I would like to do here:
- Revisit the overall IA. What I have on v5 is better in most ways than what I had on v4, but it still doesn't quite work.Some inspiration:
- Craig Mod, again
- Robin Sloan
- Maggie Appleton
- Find more!
- It needs to look good with scroll bars turned on (because that's the main way I see it!).
- #6
- Figure out how to relate the "library" to the stream of contents/notes/etc. from it. From an IA POV, posts like this are indicative of the challenge: is that a “Journal” entry or a “Library” post? Well… both? (That’s suggestive of one option: have those be views, not categories, based on various kinds of taxonomical structures I choose to add.)
- Technical details (because fun):
- #5
- Container queries? Seems fun, not sure if applicable.
- Modernize my use of Sass (I would love to drop it, but investigation indicates I cannot!).
- #3
- #4
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 reviewing the current v5 site against this issue's checklist and the linked issues #4, #5, and #6. Done means reaching agreement on the information architecture, library/content relationship, scrollbar presentation, and Sass direction; no files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html, sass
- Domain
- design, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100