dbriemann / glyph Goto Github PK

Several planned features rely on deeper access to the blog repository or Github user. Thus an optional configuration for a Github access token is required.

Idea: specify an environment variable in the config.toml which holds the access token. This way users don't accidentally publish their token.

Each tag/label should have its own index site containing links to all issues which have this tag attached.

The idea is to have Glyph export a project for another static site generator like Hugo. This allows to utilize all the existing power of those generators without re-implementing things in Glyph.

I am not convinced here. This feature means that Glyph always has to follow changes in said generators and also adds complexity to the project. This feature was a suggestion and I will keep it here so others can give their opinion/input on it. For now it's just an idea.

Options needed:

• help
• build
• clean
• version
• new? (this would clone the glyph-zero repo)
• etc...

Currently an issue needs to be closed to not have it published. While it is possible to handle drafts this way it is a bit cumbersome.

Idea: As long as an issue has a label called draft attached it is not exported to HTML.

Markdown code blocks like this:

import fmt

func main() {
    fmt.Println("Hi there")
}

shall have syntax coloring after export to HTML. The current plan is to use chroma for this. This feature will be optional and a flag will be provided in config.toml.

If GitHub API allows automated issue creation, it would be nice to use editor of choice for initial authoring of a blog post; then upload from command line. I think this would be fine as a one-shot; future edits could be done in GitHub issues.