文件列表:

_bibliography/
_data/
_includes/
_layouts/
_news/
_pages/
_paper-reviews/
_plugins/
_posts/
_projects/
_sass/
assets/
bin/
blog/
reports/
.all-contributorsrc
.dockerignore
.pre-commit-config.yaml
404.html
CONTRIBUTING.md
Dockerfile
Gemfile
LICENSE
_config.yml
docker-compose.yml
news.html
purgecss.config.js
robots.txt

# al-folio [maintainers]: https://img.shields.io/badge/maintainers-4-success.svg 'Number of maintainers' [](https://github.com/alshedivat/al-folio/actions/workflows/deploy.yml) [](https://alshedivat.github.io/al-folio/) [](https://github.com/alshedivat/al-folio/graphs/contributors/) [![Maintainers][maintainers]](#maintainers) [](https://github.com/alshedivat/al-folio/releases/latest) [](https://github.com/alshedivat/al-folio/blob/master/LICENSE) [](https://github.com/alshedivat/al-folio) [](https://github.com/alshedivat/al-folio/fork) [](https://hub.docker.com/r/amirpourmand/al-folio) [](https://hub.docker.com/r/amirpourmand/al-folio) [](https://hub.docker.com/r/amirpourmand/al-folio) A simple, clean, and responsive [Jekyll](https://jekyllrb.com/) theme for academics. If you like the theme, give it a star! [](https://alshedivat.github.io/al-folio/) ## User community The vibrant community of **al-folio** users is growing! Academics around the world use this theme for their homepages, blogs, lab pages, as well as webpages for courses, workshops, conferences, meetups, and more. Check out the community webpages below. Feel free to add your own page(s) by sending a PR.

Academics	★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★
Labs	★ ★ ★ ★ ★ ★ ★
Courses	CMU PGM (S-19) CMU DeepRL (F-19, S-20, F-20, S-21, F-21, S-22) CMU MMML (F-20, F-22) CMU AMMML (S-22, S-23) CMU ASI (S-23) CMU Distributed Systems (S-21)
Conferences & workshops	ICLR Blog Post Track (2023, 2024) ML Retrospectives (NeurIPS: 2019, 2020; ICML: 2020) HAMLETS (NeurIPS: 2020) ICBINB (NeurIPS: 2020, 2021) Neural Compression (ICLR: 2021) Score Based Methods (NeurIPS: 2022) Images2Symbols (CogSci: 2022) Medical Robotics Junior Faculty Forum (ISMR: 2023) Beyond Vision: Physics meets AI (ICIAP: 2023) Workshop on Diffusion Models (NeurIPS: 2023)

## Lighthouse PageSpeed Insights [](https://pagespeed.web.dev/report?url=https%3A%2F%2Falshedivat.github.io%2Fal-folio%2F&form_factor=desktop) ## Table Of Contents - [User community](#user-community) - [Lighthouse PageSpeed Insights](#lighthouse-pagespeed-insights) - [Table Of Contents](#table-of-contents) - [Getting started](#getting-started) - [Installation](#installation) - [Local setup using Docker (Recommended)](#local-setup-using-docker-recommended) - [Local Setup (Legacy)](#local-setup-legacy) - [Deployment](#deployment) - [Upgrading from a previous version](#upgrading-from-a-previous-version) - [FAQ](#faq) - [Features](#features) - [Publications](#publications) - [Collections](#collections) - [Layouts](#layouts) - [The iconic style of Distill](#the-iconic-style-of-distill) - [Full support for math \& code](#full-support-for-math--code) - [Photos](#photos) - [Other features](#other-features) - [GitHub's repositories and user stats](#githubs-repositories-and-user-stats) - [Theming](#theming) - [Social media previews](#social-media-previews) - [Atom (RSS-like) Feed](#atom-rss-like-feed) - [Related posts](#related-posts) - [Contributing](#contributing) - [Maintainers](#maintainers) - [All Contributors](#all-contributors) - [License](#license) ## Getting started Want to learn more about Jekyll? Check out [this tutorial](https://www.taniarascia.com/make-a-static-website-with-jekyll/). Why Jekyll? Read [Andrej Karpathy's blog post](https://karpathy.github.io/2014/07/01/switching-to-jekyll/)! ### Installation For a hands-on walkthrough of al-folio installation, check out [this cool video tutorial](https://www.youtube.com/watch?v=g6AJ9qPPoyc) by one of the community members! The preferred way of using this template is by clicking in [Use this template](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template#creating-a-repository-from-a-template) above the file list. Then, create a new repository at `github.com:/`. If you plan to upload your site to `.github.io`, note that the name of your repository must be `.github.io` or `.github.io`, as stated in the [GitHub pages docs](https://docs.github.com/en/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites). For more information on how to deploy your site, check the [Deployment](#deployment) section below. After you created your new repository, just download it to your machine: ```bash $ git clone git@github.com:/.git $ cd ``` --- #### Local setup using Docker (Recommended) Using Docker to install Jekyll and Ruby dependencies is the easiest way. You need to take the following steps to get `al-folio` up and running on your local machine: - First, install [docker](https://docs.docker.com/get-docker/) and [docker-compose](https://docs.docker.com/compose/install/). - Finally, run the following command that will pull the latest pre-built image from DockerHub and will run your website. ```bash $ docker compose pull $ docker compose up ``` Note that when you run it for the first time, it will download a docker image of size 400MB 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 (`docker compose up`) to render the webpage with all you changes. Also, make sure to commit your final changes. > To change port number, you can edit `docker-compose.yml` file.

(click to expand) Build your own docker image:

> Note: this approach is only necessary if you would like to build an older or very custom version of al-folio. Build and run a new docker image using: ```bash $ docker compose up --build ``` > If you want to update jekyll, install new ruby packages, etc., all you have to do is build the image again using `--force-recreate` argument at the end of previous command! It will download ruby and jekyll and install all ruby packages again from scratch.

--- #### Local Setup (Legacy) Assuming you have [Ruby](https://www.ruby-lang.org/en/downloads/) and [Bundler](https://bundler.io/) installed on your system (*hint: for ease of managing ruby gems, consider using [rbenv](https://github.com/rbenv/rbenv)*), and also [Python](https://www.python.org/) and [pip](https://pypi.org/project/pip/) (*hint: for ease of managing python packages, consider using a virtual environment, like [venv](https://docs.python.org/pt-br/3/library/venv.html) or [conda](https://docs.conda.io/en/latest/). If you will use only `jupyter`, you can use [pipx](https://pypa.github.io/pipx/)*). ```bash $ bundle install # assuming pip is your Python package manager $ pip install jupyter $ bundle exec jekyll serve --lsi ``` 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](https://pages.github.com/) is the most popular option. Starting version [v0.3.5](https://github.com/alshedivat/al-folio/releases/tag/v0.3.5), **al-folio** will automatically re-deploy your webpage each time you push new changes to your repository! :sparkles: **For personal and organization webpages:** 1. The name of your repository **MUST BE** `.github.io` or `.github.io`. 2. In `_config.yml`, set `url` to `https://.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 `.github.io`. **For project pages:** 1. In `_config.yml`, set `url` to `https://.github.io` and `baseurl` to `//`. 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 `.github.io//`. **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. Go to Settings -> Actions -> General -> Workflow permissions, and give **Read and write permissions** to GitHub Actions 3. Make any other changes to your webpage, commit, and push. This will automatically trigger the **Deploy** action. 4. 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. 5. 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](https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source). If you keep your site on another branch, open `.github/workflows/deploy.yml` **on the branch you keep your website on** and change on->push->branches and on->pull\_request->branches to the branch you keep your website on. This will trigger the action on pulls/pushes on that branch. The action will then deploy the website on the branch it was triggered from.

(click to expand) Manual deployment to GitHub Pages:

If you need to manually re-deploy your website to GitHub pages, go to Actions, click "Deploy" in the left sidebar, then "Run workflow."

(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: ```bash $ bundle exec jekyll build --lsi ` ... ...

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：