Autonomous Vision Blog

This is the blog of the Autonomous Vision Group at MPI-IS Tübingen and University of Tübingen. You can visit our blog at https://autonomousvision.github.io. Also check out our website to learn more about our research.

Overview

Creating a blog post follows the usual git workflow:

1. clone repository:

   git clone https://github.com/autonomousvision/autonomousvision.github.io.git
   

2. create new branch for your post:

   git branch my-post
   git checkout my-post
   

3. work on branch / push my-post branch for collaboration

4. rebase master on your branch and squash commits (note that all your commits to master will be visible in the git history):

   git checkout master
   git rebase -i my-post
   

5. push master

   git push origin master
   

6. delete your branch

   locally:

   git branch -d my-post
   

   and remotely if you pushed your branch in step 3:

   git push origin --delete my-post
   

Instructions for Authors

To write a new blog entry, first register yourself as an author in authors.yml. Here, you can also add your email address and links to your social media accounts etc.

You can then create a new blog post by adding a markdown or html file in the _posts folder. Please use the format YYYY-MM-DD-YOUR_TITLE.{md,html} for naming the file. You can then create a yaml header where you specify the author, the category of the post, tags, etc. For more information, take a look at existing posts and the Minimal Mistakes documentation.

If you want to include images or other assets, create a subfolder in the assets/posts folder with the same name as the filename of your blog post (without extension). You can simply reference your assets in your post using {{ site.url }}/assets/posts/YYYY-MM-DD-YOUR_TITLE/ followed by the filename of the corresponding asset. Make sure that you don't forget to include the {{ site.url }}! While the post while be rendered correctly without the {{ site.url }}, the images in the newsfeed will break if you don't include it.

Please keep in mind that all your commits to master will appear in the git history. To keep this history clean, it might make sense to edit your post in a separate (private) branch and then merge this branch into master.

Offline editing

When you do offline editing, you probably want to build the website offline for a preview. To this end, you first have to install Ruby and Jekyll. Then, you have to install the dependencies (called Gems) for the website:

bundle

Now, you are ready to build and serve the website using

 bundle exec jekyll serve

Sometimes Jekyll hiccups over character encoding. In this case, try

 LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 bundle exec jekyll serve

If you encounter GemNotFoundException, try to remove

BUNDLED WITH
    2.0.1

from Gemfile.lock.

This command will build the website and serve it at http://localhost:4000. When you save changes, the website will be automatically rebuilt in the background. Note, however, that changes to _config.yaml will not be tracked which means that you have to restart the jekyll server after configuration changes.

References

You can find more information here:

• Jekyll documentation
• Minimal Mistakes documentation