Technical Preview Launch
Open
Nobody has claimed this yet.
- Dominant language
- Svelte
- Stars
- 1.8k
- Forks
- 150
- Avg merge
- 11h 46m
- Merged PRs (30d)
- 8
Description
- Migration helpers, so it's easier to rename a property and write a migration for it. something that doesn't require writing raw sql queries, but still should be able to run in one transaction
- Make the saving dialog/ui consistent/pretty
- Finish README
- Finish LICENSE
- Mobile gesture for login/edit does not work on Android #119
- Record some demo videos to fill the blanks on the demo page
- Start deploying the official site via fly.io, so we eat our own dogfood, and then we can replace assets easily etc. and we can remove the fixed assets from the the static/ folder
- Write all the pages we need (Imprint etc.)
- Link previews should not break when a markdown page is referenced (how to distinguish?)
- Video poster generated from video
- Sticky TOC for long documents (any way? currently we abuse Listing node as a TOC)
- put migration files into the right place
- review file structure e.g. app vs lib split (last change to mess around with it)
- Disable edit URL, Duplicate etc. for markdown pages
- Settle on type and layout names
- Upgrade to Node 26+
- Add missing node types? (or wait?)
- Do we want custom.css (or better just keep app.css)
- Sticky menu (then we have a place for toc as well maybe?)
- Update default_site to have a suitable starting point
- Update FAQs
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 locating the README and FAQ content referenced by the checklist, then review the existing site and documentation for the unfinished sections. Done means the README is finished and the FAQs are updated consistently with the current project; the issue does not name specific files or required content.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100