GrapeGrape
Rich block editor for developers

Write anything without fighting the editor.

Everything debugging sessions and design discussions throw at you fits in one note: headings, checklists, tables, images and PDFs, with slash commands instead of menus.
Headings, lists, checklists, quotes, tables and dividers
Pasted Markdown that arrives as formatted text, and export back out to it
Images, audio and PDFs dropped straight into the note
Slash commands, drag handles and note to note links
Read the PDF where you write about it
Page through a document and take notes on it in the same place.
Structure without the menu hunt
Slash commands drop a table, a checklist or a divider where the cursor is.
Nothing is ever really deleted
Version history keeps earlier drafts of every note you write.
Results

Three things that stop being a problem

Feature lists are easy to write and hard to care about. This is what changes for developers.
Stop solving the same bug twice
Describe the symptom in search and get the note where you already worked it out.
Keep decisions where you can defend them
Ask what you decided about a service and get the note, the date and the reasoning.
Point the AI at your own stack
Bring your own key, or run a local model through Ollama, and keep the workspace on disk.
In practice

What that looks like for developers

A few moments in a normal week where the app earns its place.
Debugging
Write the symptom, the theory and the fix in one note, with the log you kept attached.
Architecture review
Record the conversation and keep the decision log next to the diagram.
New project
Keep the setup steps in a runbook that actually gets found again.
FAQ

Questions Before You Install It

The rest of them live in the help center.

Find it next time it breaks.

Runbooks, architecture decisions and the fix you worked out at midnight, in a local library you can search by meaning and keep offline.