The process is relatively simple.

  1. Fork this blog. You can use this link to find the github repo:
  2. Make your fork private. To maintain anonymity in our double-blind submission process, we must not see your changes to the blog. After your submission to our OpenReview, we will investigate the accepted posts, and we will reject the forks that are still public.
  3. Add your post to the _posts folder. This new MarkDown file must be your sole change to the entire blog. You can use standard GitHub-flavoured MarkDown. Additionally, you have to edit the file’s header:
     layout: post
     title: Title goes here
     tags: [tag1, tag2, tag3]
     authors: Doe, John, Mila; Doe, Jane, DeepMind

    You must change the title, tags, and authors fields. The authors and title fields accept standard strings, but the tags field must be an array (i.e. a string starting with [, followed by a comma-separated list of tags, followed by ]).

    Don’t worry about using “new” tags. Our blog server will automatically adapt to new tag names without issue.

    If you want to include gifs, images, and the like, you can add them to the public/images folder.

    Read our example posts carefully to make sure that your embedded assets and $ \LaTeX $ work!

  4. Submit an anonymized version of your post to our OpenReview. To do so, simply remove any references to yourself from your MarkDown file, download your fork as a ZIP file, and send it to OpenReview. A link will be provided at a later date.

    Download instructions image Include a README.txt file in the root of that ZIP that mentions which blog post is yours.

  5. Upon acceptance, you will be contacted. You will then make your fork public again, and open a Pull Request to merge your changes with our repository. After asking you to fix any compatibility issues (or fixing them ourselves if they are minor enough), we will then merge your fork into the blog. That way, GitHub will keep track of every single change made to the blog (and if someone wants to find a posts’ authors’ GitHub usernames, they’ll directly be able to find your Pull Request and your fork!).