weberc2 / neon Goto Github PK

Run tests in pr job, publish artifact in deploy job

README should succinctly cover:

• Building
• Installation
• Usage
  • neon build
  • neon serve
  • configuration
    • Link to godoc config.Config struct for details (so as to avoid having to keep the docs up to date with the struct)
    • Link to blog/neon.yaml for an example
• Contributing

Today, because my blog theme makes the blog title an <h1>, and the titles <h2>, headings in my blog content must begin with ### to render as <h3>. In order to decouple the markdown source from the details of the theme, the markdown source should be able to start headings with # and neon should coordinate with the theme to figure out the appropriate HTML heading tag to begin with.

There should be anchors in the generated HTML headings such that consumers of the generated HTML can create links to individual headings.

I should be able to tag my posts such that I can click on the tag in the rendered HTML and it will send me to an index page filtered to posts with that tag.

It looks like the Github release action is tagging all releases as master instead of some unique identifier, causing subsequent runs to fail.

For example, this post has a footnote link in the snippet, but when it appears on an index page the footnote link is broken.