The TL;DR:

1. Fork the repository
2. Head to your repository settings and click on the “Pages” tab on the left
3. Under Source, select master
4. Your new site, which will be a copy of nekox.net, can be found at YOUR_USERNAME.github.io/mikanwolfe.github.io
5. Make sure to configure _config.yml!

Nekox.net has a theme!?

Well yes, though not really.

nekox.net is a final hosted website. That being said, it’s very easy to take the core of nekox.net and modify it to your needs. This is in contrast to template repositories, there will be content to be cleared out. This content includes blog posts and so forth. On the other hand, nekox.net is built on whatatheme and contains some useful additions:

• An updated showcase to focus on achievements, projects, and recommendations
• A re-built navbar that can hold any-sized elements
• Lots of minor tweaks!

Translating Blog-Aware to Portfolio-Focused

This site is driven by Jekyll, a static site generator used for blogging. Notably, Jekyll is hosted on GitHub pages which means that repositories that enable pages can host a mini-website, be it for a project or other purpose. It all ties together to be a (pardon the misuse) simple stack.

Jekyll at its core

Jekyll is a static site generator. Jekyll combines authored content in MarkDown format with pre-made layouts to create a website. These layouts are snippets of HTML code interspaced with Liquid to create reponsive websites that can update and change as more authored content is added.

Static Sites can still include dynamic elements using JavaScript. A good example is the navigation bar, which highlights the section based on the current size of each hero showcase division on the main page.

nekox.net’s contributions

Portfolio-focused design decisions

This post is still a work in progress :’(