Alex Suraci

better handling of --plugin and go.mod

1

getting errors like this when adding `--plugin github.com/vito/booklit/chroma/plugin`: ``` ❯ ./scripts/build -s 3001 INFO[0000] plugin registered plugin=baselit ../../../go/pkg/mod/github.com/vito/[email protected]/chroma/booklit_lexer.go:4:2: missing go.sum entry for module providing package github.com/alecthomas/chroma; to add: go mod...

quality-of-life improvement for plugin functions which take numeric args like `\foos{5}`: ```go func (plug MyPlugin) Foos(count int) booklit.Content { // ... } ``` instead of ```go func (plug MyPlugin) Foos(countStr...

this would make it a lot easier to clean up cruft left over from docs refactors/restructures

would be pretty nice to have auto-completion for `\` when writing .lit files

currently flags like `--html-templates` and `--plugin` have to be passed on every command. maybe these could be in a config file instead? then we wouldn't need to keep writing scripts...

put these somewhere on the website: | website | source | | - | - | | https://concourse-ci.org | https://github.com/concourse/docs | | https://booklit.page | https://github.com/vito/booklit/tree/master/docs | | https://vito.github.io/slides/v10.html | https://github.com/vito/slides...

copyright, etc

could help alleviate fears of tying your content to Booklit forever - just convert it once and maintain the Markdown content directly from then on

Inline URLs tend to make the content flow awkwardly and force dramatic word wrapping. It'd be cool if I could write like this: ```tex Foo \link{Bar}, fizz buzz baz. ......