Morenote: project facts
- Project
- Morenote
- Period
- 2023
- Role
- Solo Developer
- Summary
- Note-taking and documentation app
- Description
- A note-taking and documentation app I built to make messy ideas easier to structure. It supports markdown, unlimited nested pages, GitHub sign-in, light and dark themes, and a publish flow that gives each doc a shareable URL.
- Domains
- Productivity, Documentation, Information Architecture, Product Engineering
- Technologies
- Next.js, TypeScript, Markdown, GitHub OAuth
- Ownership
- Product design and full frontend implementation
- Ownership
- GitHub authentication and session handling
- Ownership
- Nested page tree and sidebar navigation
- Ownership
- Markdown editor with tables, photos, and emoji support
- Ownership
- Light and dark theme system
- Ownership
- Public publishing flow with shareable links
- Learning
- Information architecture matters as much as the editor. If people cannot see where they are in a deep tree, the product feels confusing no matter how good the writing tools are.
- Professional signal
- I like building productivity tools where structure and writing experience matter equally.
a note-taking and documentation app I built to make messy ideas easier to structure. it supports markdown, unlimited nested pages, GitHub sign-in, light and dark themes, and a publish flow that gives each doc a shareable URL.
i wanted a documentation tool that felt fast and flexible without the clutter of heavier productivity apps.
i built around a tree of pages with a sidebar for structure, a focused editor in the center, and GitHub OAuth so people could sign in without another password. i added theme switching, a publishing flow for public links, and small quality-of-life pieces like an emoji picker so notes felt personal instead of sterile.
i shipped a working product on Vercel that I still use as a reference for information architecture and editor UX. it was a solo build end to end, from auth to publishing.
- ·product design and full frontend implementation
- ·gitHub authentication and session handling
- ·nested page tree and sidebar navigation
- ·markdown editor with tables, photos, and emoji support
- ·light and dark theme system
- ·public publishing flow with shareable links
nested pages sound simple until you try to build them. navigation has to stay clear when someone creates deep hierarchies, and the editor needs to handle markdown, tables, photos, and emojis without feeling like a different app for each feature.
information architecture matters as much as the editor. if people cannot see where they are in a deep tree, the product feels confusing no matter how good the writing tools are.
i thought the editor would be the hard part. getting nested navigation to feel obvious took longer.
- ·flat note lists
- ·heavy setup for simple docs
- ·hard to share polished pages
- ·unlimited nested pages
- ·markdown-first editing
- ·one-click published URLs
documentation tools fail when structure is an afterthought.
i would add real-time collaboration and offline support, but only after locking down a simpler default structure so new users are not dropped into an empty tree with no guidance.
- ·i renamed the repo a few times before settling on the Zenith codebase that powered Morenote.
- ·testing deep nesting meant creating fake trees with dozens of child pages just to see if the sidebar stayed usable.
i like building productivity tools where structure and writing experience matter equally.