Pavus roadmap

[kauefraga]

Pavus should be simple, here's the features

Markdown preview

• $ pavus [markdown] and $ pavus with recursive search
• Rendering (markdown to html, markdown-it)
• Hot reloading (fsnotify and server-sent events)
• Syntax highlighting (shiki)
• LaTeX (KaTeX?) and Mermaidjs
• Images (need to adjust the image path in the markdown to point to the server)
• Default theme

Templates

• $ pavus init or $ pavus init --template "x" --output "xyz.md" --language "pt-br" - create markdown based in a template (aliases: create, c) [43d946c]
• $ pavus templates - list available templates [b73cbf9]
• $ pavus fill [markdown] - generate prompts to fill markdown's template gaps
• $ pavus doc - modify a markdown document
  • $ pavus doc add --section "x" - append a template section
  • $ pavus doc remove --section "x" - pop a template section

Helpers

• $ pavus list - recursively find and list markdown files (aliases: find, ls)
• $ pavus open - open a markdown file with the set $EDITOR

Configuration

The idea is to store a pavus.toml in the user's home directory (~).

Dependencies: go-toml, xdg.

• $ pavus config - init config or show where it is (and the values of existing configs)
• $ pavus config [key] [value] - set a config
• Themes (preview render)
• Port (preview server)
• Open browser (preview option)
• AI token
• Custom templates

AI

• Fill template gaps
• Write a markdown based in a prompt

[kauefraga]

Template internationalization would be nice...