search

lotabout / ideas

log for new ideas and the execution of ideas
1 stars 0 forks source link

Github as blogging system #14

Closed lotabout closed 7 years ago

lotabout commented 8 years ago

The main purpose is relying on Github's built in editor so that we can directly write our blogs online.

Work flow

  1. Create a new .md file in the repository, possibly add needed YAML configurations such as categories, tags, etc.
  2. Config CI for gathering these meta info and create a index file(i.e. README) that list all you posts.

    Pros

  3. Out of the box. Do not need extra tools(except for the tools for CI).
  4. Great markdown editor provided by Github.

    Cons

  5. Don't have commenting system.
  6. Lack to ability to customize themes, fonts, etc.
  7. Cannot utilize custom domain name. (Maybe we can if we set it up with Github Pages)

    Difference with Static Blog Generator

If we setup CI to build our blog, there seems to be nothing difference with the one proposed here. We can still modify the content and it will be deployed. And the one for generating README is actually a blog generator, isn't it?

Well, yes, but personally I don't use Github's editor even if I've setup the CI for my blog.

Em... Need to think more about the ideal workflow.

lotabout commented 7 years ago

Now my blog use hexo(static blog generator) + CI deploy. Ideally I can create a new markdown via github and CI will deploy the site automatically. I think it take advantage of the static blog generator as well as github's editor (via all devices).

The proposal above should be deprecated.