harrisonl / blex Goto Github PK

Have the option to choose between js syntax highlighting or have code blocks turned in to gists automatically.

First one if pretty obvious, although the gist option could be quite useful.

Idea being that we would parse out the code blocks '```' and hit the github api creating a public gist.

This would allow the author to then easily share this around on other platforms if needed

Allow readers to create inline comments by highlight the approriate text.

This would then have a visual marker allowing others to click it and view the comment.

Could be useful for providing more context aware comments.

Allow users to say that these group of posts are all apart of the same series.

Then provide easy navigation links on the page as well as providing some sort of special
markdown syntax e.g. [In part 4]->4<- to create a link to a certain post in that series (i.e. save them time finding the post and then copy and pasting the link).

Post metadata.

In a lot of tutorials it's good to know exactly what versions and tech the author is using so you are able to know if there are any breaking changes between your versions and theirs. This would be displayed near the top of the post (depending on theme) and start collapsable.

Sometimes when your writing a post that's on topic X you will mention something that either you expect the user to know, or is more suited to topic Y.

The idea with a clarification link would be that instead of having to flesh the post explaining to those who don't understand the topic, you simply provide a link to a clarifying post (terrible name) which is a much shorter (think github project vs gist) post explaining that topic.

Then on the article there would be some clear indicator allowing the reader to click that link and be taken to the explanation.

This doesn't have to go to an internal post, could also go to an external page.

Need to come up with a way to simply install blex on a server.

Ideas:

• Use a service like Vultr, create the bare minimum and then create an image.
• Use something like docker

Need to handle the uploading of images and files.

Initially might provide the ability to upload files to the local server as well as in the future offer the option to add in a hosting service e.g. s3

Add site wide settings -> cache in ets for speed and possibly persist to dets for persistence.

Need to provide easy to understand statistics.

Initially ideas include:

• Number of views
• Frequent paths (e.g. post a -> c -> e -> b)
• Which referrers seem to be giving them the most

This one is just an idea - need to explore if feasible

Instead of having phoenix re-render the html for every request, have the post layout generated once and then use send_data in the controller action.

You could then have a channel stream the post body html in chunks and have the JS on page append each chunk to the body element.

Alternatively, render the full html and just send that in one lump

This would allow users to import data from external blogging systems.

First ones to focus on would be:

• Ghost
• Wordpress

Give the ability to link a post or series of posts with a particular git hub repo and then display some sort of widget at the top of the page.