Skip to content

docs: add help file for nvim and rework documentation - #518

Merged
sudo-tee merged 8 commits into
mainfrom
feat/docs-overhaul
Oct 13, 2026
Merged

sudo-tee merged 8 commits into
mainfrom
feat/docs-overhaul

Conversation

@sudo-tee

@sudo-tee sudo-tee commented Oct 9, 2026

Copy link
Copy Markdown
Owner

This is an MR for the future docs rework of this plugin

@sudo-tee

sudo-tee commented Oct 9, 2026

Copy link
Copy Markdown
Owner Author

Documentation screenshots for #518. Overview, context, and review images are reused from the original documentation; health and mention completion were captured with Hollow using the configured Neovim setup.

OpenCode chat panel beside a code buffer

OpenCode health report using the configured Neovim theme

Mention completion menu with files and agents

Context completion menu with current file, diagnostics, and selection

Changed-file tree and side-by-side revisions

Unified patch preview

Message-range picker with start and end markers

Review comment editor

Saved review comment beside its changed line

Review comments in the input context completion menu

@sudo-tee
sudo-tee force-pushed the feat/docs-overhaul branch from 3f38ed0 to e9d0023 Compare October 9, 2026 15:49
@sudo-tee

sudo-tee commented Oct 9, 2026

Copy link
Copy Markdown
Owner Author

New screenshots for docs/usage.md (hosted on the docs-assets branch):

Section Screenshot
Prompt history history picker
Sessions and panel tabs session picker
Sessions and panel tabs panel tabs
Permissions and questions permission prompt
Timeline and session tree timeline picker
Quick chat quick chat

@sudo-tee sudo-tee changed the title docs: add help file for Neovim tag documentation docs: add help file for nvim and rework documentation Oct 9, 2026
Replace the monolithic README with a short overview and a docs/ tree
covering getting started, usage, context, review, configuration,
reference, extensions, servers, and troubleshooting. Trim the vimdoc
entry point to a summary that links into docs/, and add a CONTRIBUTING
guide with the documentation conventions.

Add :Opencode debug events [filename] and :Opencode debug log
commands with matching api.debug_events/api.debug_log helpers, so captured
events can be exported and the plugin log opened without reaching into
Lua. Update the manual testing notes to use the new command.
Document prompt history and Markdown rendering, link each README feature
to its section, and add screenshots for the history, session, and timeline
pickers, panel tabs, permission prompts, and quick chat. Images are hosted
on the docs-assets branch.
Add a worktree sessions recipe showing how to keep a per-worktree
conversation in its own panel tab via api.open_session and a local slash
command, without changing Neovim's working directory.
@jensenojs

Copy link
Copy Markdown
Collaborator

That's great! Also, if you don't mind the theme being a little inconsistent, you could ask the agent to add some of the GIFs I made earlier to this document.

You can still let me know what theme you’re using, so I can match it when I record GIFs in the future

@sudo-tee

sudo-tee commented Oct 12, 2026 •

Copy link
Copy Markdown
Owner Author

I use kanagawa wave as a theme.

I already tasked my agent to generate a bunch of screenshots for me.

For the gifs I tried, but the agent was alittle to slow to execute the commands so the gifs were not really usefull.

But if you want to give it a try you are welcome.

I plan on merging what I have soon so we can iterate on it and improve it.

Just having it splitted in multiple doc is already a huge improvement

@sudo-tee

Copy link
Copy Markdown
Owner Author

Picker screenshots published to the dedicated docs-assets branch in ff7cbdb, keeping binary assets out of plugin installations:

Captured with hollow-cli using safe demo data. Documentation links updated locally to these raw URLs.

@sudo-tee
sudo-tee merged commit 7c67812 into main Oct 13, 2026
12 checks passed
@jensenojs
jensenojs deleted the feat/docs-overhaul branch October 19, 2026 23:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants