iokode / butterfly Goto Github PK

Use GH actions to automatically create images when pushing main branch.

Remain discussions for comments, but store post text inside repository code.

Advantages:

• GitHub repository code will not be indexed like the entry, helping me to index the blog instead of GitHub discussions.
• Allow pull-request to fix text in the post.
• Allow use other formats like asciidoc instead of only markdown.

Markdown has some limitations about embedding content or making alerts. Investigate about alternatives (maybe AsciiDoc?) and update publishing format.

While GitHub Discussions only allow Markdown format, I should let GH Discussions only for comments, and publish the content inside the repository. This will allow someone to make pull requests fixing content (cc/ @JaviAibar).

When a blog request occurs, Butterfly queries GitHub API and wait the API response, then it composes the HTML document and it sends the blog response.

Querying GitHub API takes time, so we Butterfly should cache the response and avoid querying GitHub API multiple times to get the same data.

Analytics (#10) requires cookies.

Allow listening address and UNIX Socket

Allow to update social and other blog links directly from GitHub without the need to recompile application.