Git Product home page Git Product logo

2024's Introduction

ICLR 2024 Blogposts Track

This is the repository for the blogposts track. This website is based off of the al-folio template. Some of their original documentation for using this template is included below, but you can find their full README in the original repo.

Links

Call for blog posts: https://iclr-blogposts.github.io/2024/call

About: https://iclr-blogposts.github.io/2024/about

Submission guide: https://iclr-blogposts.github.io/2024/submitting

Track Chairs

  • Gauthier Gidel, Mila, UdeM
  • David Dobre, Mila, UdeM
  • Charlie Gauthier, Mila, UdeM
  • Claire Vernade, University of Tuebingen
  • Fabian Pedregosa, Google DeepMind
  • Leo Schwinn, Friedrich-Alexander-University Erlangen-Nürnberg

 


 

al-folio

Note: some of the original content of the README is omitted for brevity. Please view the original README on the al-folio github repo.

Table Of Contents

Getting started

Want to learn more about Jekyll? Check out this tutorial. Why Jekyll? Read Andrej Karpathy's blog post!

Installation

For a hands-on walkthrough of al-folio installation, check out this cool video tutorial by one of the community members! 🎬 🍿


Local setup using Docker (Recommended)

You need to take the following steps to get al-folio up and running in your local machine:

git clone [email protected]:<your-username>/<your-repo-name>.git
cd <your-repo-name>

Finally, run the following command that will pull a pre-built image from Docker and will run your website.

./bin/docker_run.sh

Note that when you run it for the first time, it will download a docker image of size 300MB or so.

Now, feel free to customize the theme however you like (don't forget to change the name!). After you are done, you can use the same command (bin/docker_run.sh) to render the webpage with all you changes. Also, make sure to commit your final changes. It's also possible to change port number by editing the docker_run.sh file.


Local Setup (Legacy)

Assuming you have Ruby and Bundler installed on your system (hint: for ease of managing ruby gems, consider using rbenv), first fork the theme from github.com:alshedivat/al-folio to github.com:<your-username>/<your-repo-name> and do the following:

git clone [email protected]:<your-username>/<your-repo-name>.git
cd <your-repo-name>
bundle install
bundle exec jekyll serve --future

Now, feel free to customize the theme however you like (don't forget to change the name!). After you are done, commit your final changes.


Deployment

Deploying your website to GitHub Pages is the most popular option. Starting version v0.3.5, al-folio will automatically re-deploy your webpage each time you push new changes to your repository! ✨

For personal and organization webpages:

  1. Rename your repository to <your-github-username>.github.io or <your-github-orgname>.github.io.
  2. In _config.yml, set url to https://<your-github-username>.github.io and leave baseurl empty.
  3. Set up automatic deployment of your webpage (see instructions below).
  4. Make changes, commit, and push!
  5. After deployment, the webpage will become available at <your-github-username>.github.io.

For project pages:

  1. In _config.yml, set url to https://<your-github-username>.github.io and baseurl to /<your-repository-name>/.
  2. Set up automatic deployment of your webpage (see instructions below).
  3. Make changes, commit, and push!
  4. After deployment, the webpage will become available at <your-github-username>.github.io/<your-repository-name>/.

To enable automatic deployment:

  1. Click on Actions tab and Enable GitHub Actions; do not worry about creating any workflows as everything has already been set for you.
  2. Make any other changes to your webpage, commit, and push. This will automatically trigger the Deploy action.
  3. Wait for a few minutes and let the action complete. You can see the progress in the Actions tab. If completed successfully, in addition to the master branch, your repository should now have a newly built gh-pages branch.
  4. Finally, in the Settings of your repository, in the Pages section, set the branch to gh-pages (NOT to master). For more details, see Configuring a publishing source for your GitHub Pages site.
(click to expand) Manual deployment to GitHub Pages:

If you need to manually re-deploy your website to GitHub pages, run the deploy script from the root directory of your repository:

./bin/deploy

uses the master branch for the source code and deploys the webpage to gh-pages.

(click to expand) Deployment to another hosting server (non GitHub Pages):

If you decide to not use GitHub Pages and host your page elsewhere, simply run:

bundle exec jekyll build

which will (re-)generate the static webpage in the _site/ folder. Then simply copy the contents of the _site/ foder to your hosting server.

Note: Make sure to correctly set the url and baseurl fields in _config.yml before building the webpage. If you are deploying your webpage to your-domain.com/your-project/, you must set url: your-domain.com and baseurl: /your-project/. If you are deploing directly to your-domain.com, leave baseurl blank.

(click to expand) Deployment to a separate repository (advanced users only):

Note: Do not try using this method unless you know what you are doing (make sure you are familiar with publishing sources). This approach allows to have the website's source code in one repository and the deployment version in a different repository.

Let's assume that your website's publishing source is a publishing-source sub-directory of a git-versioned repository cloned under $HOME/repo/. For a user site this could well be something like $HOME/<user>.github.io.

Firstly, from the deployment repo dir, checkout the git branch hosting your publishing source.

Then from the website sources dir (commonly your al-folio fork's clone):

bundle exec jekyll build --destination $HOME/repo/publishing-source

This will instruct jekyll to deploy the website under $HOME/repo/publishing-source.

Note: Jekyll will clean $HOME/repo/publishing-source before building!

The quote below is taken directly from the jekyll configuration docs:

Destination folders are cleaned on site builds

The contents of <destination> are automatically cleaned, by default, when the site is built. Files or folders that are not created by your site will be removed. Some files could be retained by specifying them within the <keep_files> configuration directive.

Do not use an important location for <destination>; instead, use it as a staging area and copy files from there to your web server.

If $HOME/repo/publishing-source contains files that you want jekyll to leave untouched, specify them under keep_files in _config.yml. In its default configuration, al-folio will copy the top-level README.md to the publishing source. If you want to change this behaviour, add README.md under exclude in _config.yml.

Note: Do not run jekyll clean on your publishing source repo as this will result in the entire directory getting deleted, irrespective of the content of keep_files in _config.yml.


FAQ

Here are some frequently asked questions. If you have a different question, please ask using Discussions.

  1. Q: After I fork and setup the repo, I get a deployment error. Isn't the website supposed to correctly deploy automatically?
    A: Yes, if you are using release v0.3.5 or later, the website will automatically and correctly re-deploy right after your first commit. Please make some changes (e.g., change your website info in _config.yml), commit, and push. Make sure to follow deployment instructions in the previous section. (Relevant issue: 209.)

  2. Q: I am using a custom domain (e.g., foo.com). My custom domain becomes blank in the repository settings after each deployment. How do I fix that?
    A: You need to add CNAME file to the master or source branch of your repository. The file should contain your custom domain name. (Relevant issue: 130.)

  3. Q: My webpage works locally. But after deploying, it is not displayed correctly (CSS and JS is not loaded properly). How do I fix that?
    A: Make sure to correctly specify the url and baseurl paths in _config.yml. Set url to https://<your-github-username>.github.io or to https://<your.custom.domain> if you are using a custom domain. If you are deploying a personal or organization website, leave baseurl blank. If you are deploying a project page, set baseurl: /<your-project-name>/.

  4. Q: Atom feed doesn't work. Why?
    A: Make sure to correctly specify the url and baseurl paths in _config.yml. RSS Feed plugin works with these correctly set up fields: title, url, description and author. Make sure to fill them in an appropriate way and try again.

Features

Publications

Your publications page is generated automatically from your BibTex bibliography. Simply edit _bibliography/papers.bib. You can also add new *.bib files and customize the look of your publications however you like by editing _pages/publications.md.

(click to expand) Author annotation:

In publications, the author entry for yourself is identified by string array scholar:last_name and string array scholar:first_name in _config.yml:

scholar:
  last_name: [Einstein]
  first_name: [Albert, A.]

If the entry matches one form of the last names and the first names, it will be underlined. Keep meta-information about your co-authors in _data/coauthors.yml and Jekyll will insert links to their webpages automatically. The coauthor data format in _data/coauthors.yml is as follows,

"Adams":
  - firstname: ["Edwin", "E.", "E. P.", "Edwin Plimpton"]
    url: https://en.wikipedia.org/wiki/Edwin_Plimpton_Adams

"Podolsky":
  - firstname: ["Boris", "B.", "B. Y.", "Boris Yakovlevich"]
    url: https://en.wikipedia.org/wiki/Boris_Podolsky

"Rosen":
  - firstname: ["Nathan", "N."]
    url: https://en.wikipedia.org/wiki/Nathan_Rosen

"Bach":
  - firstname: ["Johann Sebastian", "J. S."]
    url: https://en.wikipedia.org/wiki/Johann_Sebastian_Bach

  - firstname: ["Carl Philipp Emanuel", "C. P. E."]
    url: https://en.wikipedia.org/wiki/Carl_Philipp_Emanuel_Bach

If the entry matches one of the combinations of the last names and the first names, it will be highlighted and linked to the url provided.

(click to expand) Buttons (through custom bibtex keywords):

There are several custom bibtex keywords that you can use to affect how the entries are displayed on the webpage:

  • abbr: Adds an abbreviation to the left of the entry. You can add links to these by creating a venue.yaml-file in the _data folder and adding entries that match.
  • abstract: Adds an "Abs" button that expands a hidden text field when clicked to show the abstract text
  • arxiv: Adds a link to the Arxiv website (Note: only add the arxiv identifier here - the link is generated automatically)
  • bibtex_show: Adds a "Bib" button that expands a hidden text field with the full bibliography entry
  • html: Inserts a "HTML" button redirecting to the user-specified link
  • pdf: Adds a "PDF" button redirecting to a specified file (if a full link is not specified, the file will be assumed to be placed in the /assets/pdf/ directory)
  • supp: Adds a "Supp" button to a specified file (if a full link is not specified, the file will be assumed to be placed in the /assets/pdf/ directory)
  • blog: Adds a "Blog" button redirecting to the specified link
  • code: Adds a "Code" button redirecting to the specified link
  • poster: Adds a "Poster" button redirecting to a specified file (if a full link is not specified, the file will be assumed to be placed in the /assets/pdf/ directory)
  • slides: Adds a "Slides" button redirecting to a specified file (if a full link is not specified, the file will be assumed to be placed in the /assets/pdf/ directory)
  • website: Adds a "Website" button redirecting to the specified link

You can implement your own buttons by editing the bib.html file.


Collections

This Jekyll theme implements collections to let you break up your work into categories. The theme comes with two default collections: news and projects. Items from the news collection are automatically displayed on the home page. Items from the projects collection are displayed on a responsive grid on projects page.

You can easily create your own collections, apps, short stories, courses, or whatever your creative work is. To do this, edit the collections in the _config.yml file, create a corresponding folder, and create a landing page for your collection, similar to _pages/projects.md.


Layouts

al-folio comes with stylish layouts for pages and blog posts.

The iconic style of Distill

The theme allows you to create blog posts in the distill.pub style:

For more details on how to create distill-styled posts using <d-*> tags, please refer to the example.

Full support for math & code

al-folio supports fast math typesetting through MathJax and code syntax highlighting using GitHub style:

Photos

Photo formatting is made simple using Bootstrap's grid system. Easily create beautiful grids within your blog posts and project pages:


Other features

GitHub repositories and user stats

al-folio uses github-readme-stats to display GitHub repositories and user stats on the the /repositories/ page.

Edit the _data/repositories.yml and change the github_users and github_repos lists to include your own GitHub profile and repositories to the the /repositories/ page.

You may also use the following codes for displaying this in any other pages.

<!-- code for GitHub users -->
{% if site.data.repositories.github_users %}
<div class="repositories d-flex flex-wrap flex-md-row flex-column justify-content-between align-items-center">
  {% for user in site.data.repositories.github_users %}
    {% include repository/repo_user.html username=user %}
  {% endfor %}
</div>
{% endif %}

<!-- code for GitHub repositories -->
{% if site.data.repositories.github_repos %}
<div class="repositories d-flex flex-wrap flex-md-row flex-column justify-content-between align-items-center">
  {% for repo in site.data.repositories.github_repos %}
    {% include repository/repo.html repository=repo %}
  {% endfor %}
</div>
{% endif %}

Theming

A variety of beautiful theme colors have been selected for you to choose from. The default is purple, but you can quickly change it by editing the --global-theme-color variable in the _sass/_themes.scss file. Other color variables are listed there as well. The stock theme color options available can be found at _sass/variables.scss. You can also add your own colors to this file assigning each a name for ease of use across the template.

Social media previews

al-folio supports preview images on social media. To enable this functionality you will need to set serve_og_meta to true in your _config.yml. Once you have done so, all your site's pages will include Open Graph data in the HTML head element.

You will then need to configure what image to display in your site's social media previews. This can be configured on a per-page basis, by setting the og_image page variable. If for an individual page this variable is not set, then the theme will fall back to a site-wide og_image variable, configurable in your _config.yml. In both the page-specific and site-wide cases, the og_image variable needs to hold the URL for the image you wish to display in social media previews.

Atom (RSS-like) Feed

It generates an Atom (RSS-like) feed of your posts, useful for Atom and RSS readers. The feed is reachable simply by typing after your homepage /feed.xml. E.g. assuming your website mountpoint is the main folder, you can type yourusername.github.io/feed.xml

Contributing

Contributions to al-folio are very welcome! Before you get started, please take a look at the guidelines.

If you would like to improve documentation, add your webpage to the list below, or fix a minor inconsistency or bug, please feel free to send a PR directly to master. For more complex issues/bugs or feature requests, please open an issue using the appropriate template.

Maintainers


Maruan

Rohan Deb Sarkar

Amir Pourmand

License

The theme is available as open source under the terms of the MIT License.

Originally, al-folio was based on the *folio theme (published by Lia Bogoev and under the MIT license). Since then, it got a full re-write of the styles and many additional cool features.

2024's People

Contributors

albertcthomas avatar blackhc avatar busycalibrating avatar calvinmccarter avatar chendaiwei-99 avatar craffel avatar dasayan05 avatar deepqzero avatar eify avatar fabianp avatar godxuxilie avatar janelawrence avatar liutianlin0121 avatar matdag avatar midfranc avatar mischapanch avatar mkielo3 avatar rylanschaeffer avatar schwinnl avatar sophie-xhonneux avatar srossi93 avatar turnmanh avatar velythyl avatar vmerckle avatar vwxyzjn avatar ybwang119 avatar ziksby avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

2024's Issues

Code block syntax highlighting not working properly

The relevant section of the Sample Blog Post is now rendered like this on my Mac, both in Chrome and Safari:

Screenshot 2023-11-26 at 3 09 42 PM

Which doesn't seem correct. If I reload the page, for a split second it seems to show the correct C++ syntax highlights, so I suspect there is some unintended style sheet overwrite going on. The same happens when I work on my own blog post with python syntax highlighting.

Markdown links don't render in footnotes

Markdown links don't appear to be rendering when they are placed in footnotes. When the example below is rendered, the link in the body appears as expected, but the one in the footnote appears as the markdown.

---
layout: distill
title: Example
description: Example
date: 2024-05-07
future: true
authors:
  - name: Anonymous
bibliography: 2024-05-07-distill-example.bib
toc:
  - name: Footnotes
---

## Footnotes

Just wrap the text you would like to show up in a footnote in a `<d-footnote>` tag.
The number of the footnote will be automatically generated.<d-footnote>This will become a hoverable footnote. [Test link](https://www.google.com/)</d-footnote>

***

[Lorem ipsum](https://www.google.com) dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
image

Unable to find image 'al-folio:latest' locally

The download falls when trying to retrieve module from http://deb.debian.org/debian bookworm

Updating package manager, pruning docker image in my local and every step in guide has failed me.

To Reproduce
Steps to reproduce the behavior:

  1. Run ./bin/docker_run.sh
  2. See error in additional context

System (please complete the following information):

  • OS: Ubuntu 16.04.6 LTS
  • Docker version: Docker version 18.09.6, build 481bc77

Additional context

Step 3/16 : RUN apt-get update -y
.
.
.
Err:3 http://deb.debian.org/debian-security bookworm-security InRelease
  At least one invalid signature was encountered.
Reading package lists...
W: GPG error: http://deb.debian.org/debian bookworm InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian bookworm InRelease' is not signed.
W: GPG error: http://deb.debian.org/debian bookworm-updates InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian bookworm-updates InRelease' is not signed.
W: GPG error: http://deb.debian.org/debian-security bookworm-security InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian-security bookworm-security InRelease' is not signed.
E: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true'
E: Sub-process returned an error code
The command '/bin/sh -c apt-get update -y' returned a non-zero code: 100
Unable to find image 'al-folio:latest' locally
docker: Error response from daemon: pull access denied for al-folio, repository does not exist or may require 'docker login'.
See 'docker run --help'.

2024/blog/diffusion-theory-from-scratch/

Building Diffusion Model's theory from ground up | ICLR Blogposts 2024

Diffusion Model, a new generative model family, has taken the world by storm after the seminal paper by Ho et al. [2020]. While diffusion models are often described as a probabilistic Markov Chain, their fundamental principle lies in the decade-old theory of Stochastic Differential Equation (SDE), as found out later by Song et al. [2021]. In this article, we will go back and revisit the 'fundamental ingredients' behind the SDE formulation, and show how the idea can be 'shaped' to get to the modern form of Score-based Diffusion Models. We'll start from the very definition of 'score', how it was used in the context of generative modeling, how we achieve the necessary theoretical guarantees, how the design choices were made and finally

https://dasayan05.github.io/2024/blog/diffusion-theory-from-scratch/

Can't add PR label; and confusion about submission URL

  1. Hi @fabianp, how do I add submission label to PR ?

  2. The URL that I get after the PR build is https://xxxxxxxx.cloudfront.net/2024-05-07-submission-name/. But openreview is expecting (erroring otherwise) something like https://iclr-blogposts.github.io/2024/blog/[YOUR_SUBMISSION]/. Where do I get the submittable URL ?

Command ./bin/dockerhub_run.sh fails

I get the error "

Could not find gem 'jekyll-target-blank' in locally installed gems
Run `bundle install` to install missing gems.

The error message is confusing, as I guess this is an error from docker not having some packages? running locally bundle install doesn't change anything

why two bibliographies?

I currently see in the repo _bibliography/papers.bib and assets/bibliography/2024-05-07-distill-example.bib.

What is the first one used for? do we need both?

Figures not updated on the deployed blogpost

Hi,

When pushing a modified figure in the blogpost repo, the modification is not taken into account in the deployed blogpost under the url https://d2jud02ci9yv69.cloudfront.net/2024-05-07-[SUBMISSION NAME]. The figure https://d2jud02ci9yv69.cloudfront.net/2024-05-07-[SUBMISSION NAME]/assets/img/2024-05-07-[SUBMISSION NAME]/my_figure.png is still the first version of the figure which differs from the one in the repo.

Keep showing 404 Not Found

Hi,

Thanks for the great efforts!

I am trying to submit a PR, which has passed all checks but it returns a website showing 404 Not Found. The error message is below:

404 Not Found

Code: NoSuchKey
Message: The specified key does not exist.
Key: 2024-05-07-seesaw-91/blog/seesaw/index.html
RequestId: J4E4M0M4ZBW8EJ9M
HostId: p3rwnNxc8xkaFfELTj7WY8eFtM9xjfrEWPdCDHaDwkizqAyMLaKM6+lBA/rilGDGBMzRTsjMdFA=

Hope you could help with this issue.

Thanks again :)

Obtaining URL for Blog Post Pull Request?

The submission instructions state:

Open a pull request against the main branch of the [2024 repo](https://github.com/iclr-blogposts/2024). Fill in the checklist provided in the PR template. The title of your pull request should be exactly the name of your markdown/html file.
i.e. _posts/2024-05-07-[SUBMISSION NAME].md would require a PR name 2024-05-07-[SUBMISSION NAME]

(TBD) Your post will automatically run two pipelines: one to verify that you have not modified any other file in the repo, and another that will create a unique URL for your contributed blog post.

Verify that everything looks correct in the given URL.
If the pipelines failed, check if it was because of improper formatting (i.e. you modified restricted files). If this is the case, fix the issues. If the issue persist, please ping one of the repo admins.

I opened a PR here but I've been unable to find out where our submission URL is. I don't see a comment on the PR and I haven't received anything by email.

Could someone please clarify?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.