Ahmet Cecen edited this page Dec 13, 2016 · 7 revisions

Welcome to the project-pages wiki! Hopefully this will eventually become a decent source of information about project-pages.

Quick Start

Project-Pages can be setup in a similar manner to any other Jekyll template. For the non-code savvy user, there is a graphical setup process that requires minimal user input and no coding.

You can setup your own Project-Pages instance with very little effort in 5-7 minutes. Do it now!

Casual Layouts

Project-Pages includes basic layouts for posts and presentations intended for the casual user. These can be created by copying the examples from the _posts folder.

Project-Pages Editor provides a graphical posting workflow for the non-code savvy user.

Advanced Layouts

Project-Pages also includes advanced layouts for the coding scientist. MATLAB and Jupyter layouts provide a framework for direct to post functionality. Surface and Projector layouts provide 3D visualization methods.


Installation Guide Added! Content creation guide is coming soon!

Nav Bar Jumbles

If you have seemingly random pages popping up on your Nav Bar recently, this is due to the fact that GitHub/Jekyll changed a fundemental rule they used to render pages.


It used to be that if a markdown file didn't have --- frontmatter at the beginning, it wasn't rendered as a page. This was changed very recently (like in the last 2 days) so that every markdown file anywhere no matter what gets rendered as a page.


1) Go to:

project-pages/plugin/markdown/ or yourreponame/plugin/markdown/ and delete example.html and example.md files. This can be done graphically for the non-Git-savvy by simply going to your:

GitHub account -> Your Profile -> Repositories -> Project-Pages/Your Repo -> Pluging -> Markdown

and clicking on the files, then clicking on the "thrash can / delete this file" icon on the top right corner of the file.

2) You need to change the LICENSES.md at:

GitHub account -> Your Profile -> Repositories -> Project-Pages/Your Repo

to License.md by clicking on the file and changing the name.

The fixes are already implemented here so new forks won't have a problem, and old forks should be able merge without conflict if they know how to.