Adding content to the website

[nikopartanen]

Website is now live here:

https://langdoc.github.io/UPA/

There is no real content though. The easiest way to edit it is to type directly here:

https://github.com/langdoc/UPA/edit/gh-pages/README.md

We can also write the text in README.md file of the master branch where @meehkal already wrote a bit, and then copy the parts to the public file once we are happy with it. We maybe need to delegate a bit who writes what? It is also possible to add there automatically generated zip file which has all the content.

But I explain below how it goes on command line as well.

This is the theme I picked now, I'll customize it a bit in some point, but it is also easy to change:

https://pages-themes.github.io/leap-day/

If you would add a file called whatever.md, content of that would be rendered into langdoc.github.io/UPA/whatever, and link [whatever page](./whatever) would lead there. Same with images, if there was folder images, you could refer to those by writing ![images/image.jpg].

So there could be folders for different types of resources and they would be described and linked in the text with lists or other structures, you can see from the theme demo page above what all can be used.

Command line part

GitHub pages can be used very easily to build a website. Basically what it does is to take README file and some other content from the repository and render that as index.html file of the website. GitHub pages are always public. So what I did now is to have two branches in UPA repository:

If you just do git clone https://github.com/langdoc/UPA you will get only the master branch. You need to do: git clone -b gh-pages https://github.com/langdoc/UPA in order to get the public branch. I assume in some point we can use just the master branch to deploy all content and this gh-pages branch will not be necessary, but for now it is quite convenient.

niko:UPA niko$ git branch
* gh-pages
  master

The gh-pages branch has no shared history with the master branch, so content there is still private. If you are still in master branch, you can do:

niko:UPA niko$ git checkout gh-pages
Switched to branch 'gh-pages'
niko:UPA niko$ git checkout master
Switched to branch 'master'

It is bit scary as you actually see entirely different README file in front of you when you switch the branch, but this is how it works. It doesn't allow you to switch branches if you have uncommitted changes in other one.