Pre-ROS

Nice, I'll have to check out how you set up your pages. It looks more elegant than my approach. I used reStructuredText (RST, ReST, or reST) as my markup language and then used sphinx to build the individual .rst files into a structure... Just because that is what I have used before.

@mjwhite, yes I too would like to know what you use to generate your HTML web page content.

I just now got my github io page set up.  All I have right now is a title and a picture of Alysha's face.  

The Alysha Project

I can write my own HTML if needed, but it would be nice if there was an easier way to generate the HTML code by just writing a regular text article.

@twobits

Check out the use of Jekyll.  It's a customizable framework for static pages.  You can pick from a variety of themes, but I just went with the default minima theme.  The easiest way is to download Jekyll onto your desktop.  It comes as a ruby gem so you're going to need a ruby install.  You don't have to know anything about ruby, just follow the instructions.  You can then develop everything on your laptop and push your updates to Github from the command line.

Let me know if you run into any problems and I can try to help, although I just learned it this weekend so my knowledge is limited.

Bye the way, check out this guy's YouTube series of videos for Github pages with Jekyll.  He does and excellent job of stepping you through it.

Thanks,

I am converting my pages to Jekyll.

@mjwhite

Those pages you've created on your Programming Robots page look great!

?

Bill

@mjwhite

I went through the tutorial you suggested. Jekyll seems suitable for the content I would like to present. I think I have to paly around with the TOC plug-in to generate a book-like structure.

In the meantime, do you mind if I clone your ROBOT repo and customize to fit my needs? Your quick weekend project looks better than I could do in a month.

@twobits

Absolutely.  Glad I can save you some time. 

@mjwhite

What is the command line to push what was setup locally to a Github page?

Is it covered in the video tutorial above?  I've only gotten through the first 8 videos.

@codecage

Yes, it's covered in the last video.   You have to init your local repository: 

cd into your site directory.

git init

git checkout -b gh-pages

Then add the files and commit

git add .

git commit -m "initial commit"

git remote add origin "https://github.com/<your github id>/<your repo>.git

git push origin gh-pages

After other updates then just:

git add .

git commit -m "my update comment"

git push origin gh-pages

That's it.  To see what files will get added you can use:

git status

Thanks @mjwhite!

It's starting to be much clearer as I work my way through the video series.

@mjwhite

I know this is really the wrong place for this question, but it looks like you have this figured out.  If you feel I should look elsewhere don't hesitate to say so.

Everything, minimal as it is, seems to be working locally, however on the gh-pages the one photo I placed in my one and only post does not show up on my github,io page, just the alt name.

Any ideas?

@mjwhite

I figured it out!  Has to do with the path to the file!

The big issue is that the path used on my local machine has to have the https://{my github,io path} added in front of what was used locally.  Any idea how to handle that automatically?   It wasn't too bad adding that to the one pic I had in that first post, but will definitely become a big pain in the you know what.

Here is the link to what I just created: https://steveg-n4tty.github.io/WillyNilly/

The RSS feed doesn't work and I haven't even figured out where to get rid of that yet.

Nice web page Steve!

@codecage

Here's what my image links look like:

![image description]({{site.url}}{{site.baseurl}}/assets/images/Two-Wheeled-Robot-Slides.011.jpeg)

Where assets/images is where I keep my images within the directory hierarchy.

One other gotcha is that you will need to put your Github repository name in the _config.yml file like this:

baseurl: "/Robots" # the subpath of your site, e.g. /blog

 which gives you a whole bunch of error when you try and run the site again on your localhost.

To get around this start the Jekyll server with the following command, which will ignore the baseurl when running locally:

jekyll serve --baseurl ''