Upgrading the README file (#2034)
I decided to break the README file into different ones to declutter it from the main page. Also adding some more explanation on the structure of the template. Tackling #2032 and #2033 --------- Signed-off-by: George Araujo <george.gcac@gmail.com>
This commit is contained in:
George
GitHub
parent
92ac10ad82
commit
4a55cd1bd1
|
|
@ -0,0 +1,147 @@
|
|||
# Customize
|
||||
|
||||
Here we will give you some tips on how to customize the website.
|
||||
|
||||
## Project structure
|
||||
|
||||
The project is structured as follows, focusing on the main components that you will need to modify:
|
||||
|
||||
```txt
|
||||
.
|
||||
├── 📄 404.html: 404 page (page not found)
|
||||
├── 📂 assets/: contains the assets that are displayed in the website
|
||||
│ └── 📂 json/
|
||||
│ └── 📄 resume.json: CV in JSON format (https://jsonresume.org/)
|
||||
├── 📂 _bibliography/
|
||||
│ └── 📄 papers.bib: bibliography in BibTeX format
|
||||
├── 📄 _config.yml: the configuration file of the template
|
||||
├── 📂 _data/: contains some of the data used in the template
|
||||
│ ├── 📄 cv.yml: CV in YAML format, used when assets/json/resume.json is not found
|
||||
│ └── 📄 repositories.yml: users and repositories info in YAML format
|
||||
├── 📂 _includes/: contains code parts that are included in the main HTML file
|
||||
├── 📂 _layouts/: contains the layouts to choose from in the frontmatter of the Markdown files
|
||||
├── 📂 _news/: the news that will appear in the news section in the about page
|
||||
├── 📄 news.html: defines the news section layout in the about page
|
||||
├── 📂 _pages/: contains the pages of the website that are shown in the header
|
||||
├── 📂 _posts/: contains the blog posts
|
||||
├── 📂 _projects/: contains the projects
|
||||
└── 📂 _sass/: contains the SASS files that define the style of the website
|
||||
├── 📄 _base.scss: base style of the website
|
||||
├── 📄 _cv.scss: style of the CV page
|
||||
├── 📄 _distill.scss: style of the Distill articles
|
||||
├── 📄 _layout.scss: style of the overall layout
|
||||
├── 📄 _themes.scss: themes colors and a few icons
|
||||
└── 📄 _variables.scss: variables used in the SASS files
|
||||
```
|
||||
|
||||
## Configuration
|
||||
|
||||
The configuration file [_config.yml](_config.yml) contains the main configuration of the website. Most of the settings is self-explanatory and we also tried to add as much comments as possible. If you have any questions, please check if it was not already answered in the [FAQ](FAQ.md).
|
||||
|
||||
> Note that the `url` and `baseurl` settings are used to generate the links of the website, as explained in the [install instructions](INSTALL.md).
|
||||
|
||||
All changes made to this file are only visible after you rebuild the website. That means that you need to run `bundle exec jekyll serve --lsi` again if you are running the website locally or push your changes to GitHub if you are using GitHub Pages. All other changes are visible immediately, you only need to refresh the page.
|
||||
|
||||
## Modifying the CV information
|
||||
|
||||
There are currently 2 different ways of generating the CV page content. The first one is by using a json file located in [assets/json/resume.json](assets/json/resume.json). It is a [known standard](https://jsonresume.org/) for creating a CV programmatically. The second one, currently used as a fallback when the json file is not found, is by using a yml file located in [_data/cv.yml](_data/cv.yml). This was the original way of creating the CV page content and since it is more human readable than a json file we decided to keep it as an option.
|
||||
|
||||
What this means is, if there is no resume data defined in [_config.yml](_config.yml) and loaded via a json file, it will load the contents of [_data/cv.yml](_data/cv.yml). If you want to use the [_data/cv.yml](_data/cv.yml) file as the source of your CV, you must delete the [assets/json/resume.json](assets/json/resume.json) file.
|
||||
|
||||
## Modifying the user and repository information
|
||||
|
||||
The user and repository information is defined in [_data/repositories.yml](_data/repositories.yml). You can add as many users and repositories as you want. Both informations are used in the `repositories` section.
|
||||
|
||||
## Creating new pages
|
||||
|
||||
You can create new pages by adding new Markdown files in the [_pages](_pages/) directory. The easiest way to do this is to copy an existing page and modify it. You can choose the layout of the page in the [frontmatter](https://jekyllrb.com/docs/front-matter/) of the Markdown file. You can also add new layouts in the [_layouts](_layouts/) directory if you feel the need for it.
|
||||
|
||||
## Creating new blog posts
|
||||
|
||||
To create a new blog post, you can add a new Markdown file in the [_posts](_posts/) directory. The name of the file must follow the format `YYYY-MM-DD-title.md`. The easiest way to do this is to copy an existing blog post and modify it. Note that some blog posts have optional fields in the [frontmatter](https://jekyllrb.com/docs/front-matter/) that are used to enable specific behaviors or functions.
|
||||
|
||||
If you want to create blog posts that are not ready to be published, but you want to track it with git, you can create a [_drafts](https://jekyllrb.com/docs/posts/#drafts) directory and store them there.
|
||||
|
||||
## Creating new projects
|
||||
|
||||
You can create new projects by adding new Markdown files in the [_projects](_projects/) directory. The easiest way to do this is to copy an existing project and modify it.
|
||||
|
||||
## Adding some news
|
||||
|
||||
You can add news in the about page by adding new Markdown files in the [_news](_news/) directory. There are currently two types of news: inline news and news with a link. News with a link take you to a new page while inline news are displayed directly in the about page. The easiest way to create yours is to copy an existing news and modify it.
|
||||
|
||||
## Adding 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](_config.yml) file, create a corresponding folder, and create a landing page for your collection, similar to [_pages/projects.md](_pages/projects.md).
|
||||
|
||||
## Adding a new publication
|
||||
|
||||
To add publications create a new entry in the [_bibliography/papers.bib](_bibliography/papers.bib) file. You can find the BibTeX entry of a publication in Google Scholar by clicking on the quotation marks below the publication title, then clicking on "BibTeX", or also in the conference page itself. By default, the publications will be sorted by year and the most recent will be displayed first. You can change this behavior and more in the `Jekyll Scholar` section in [_config.yml](_config.yml) file.
|
||||
|
||||
You can add extra information to a publication, like a PDF file in the `assets/pdfs/` directory and add the path to the PDF file in the BibTeX entry with the `pdf` field. Some of the supported fields are: `abstract`, `altmetric`, `arxiv`, `bibtex_show`, `blog`, `code`, `dimensions`, `doi`, `eprint`, `html`, `isbn`, `pdf`, `pmid`, `poster`, `slides`, `supp`, `video`, and `website`.
|
||||
|
||||
### 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](_config.yml). For example, if you have the following entry in your [_config.yml](_config.yml):
|
||||
|
||||
```yaml
|
||||
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](_data/coauthors.yml) and Jekyll will insert links to their webpages automatically. The co-author data format is as follows,
|
||||
|
||||
```yaml
|
||||
"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.
|
||||
|
||||
### 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
|
||||
- `altmetric`: Adds an [Altmetric](https://www.altmetric.com/) badge (Note: if DOI is provided just use `true`, otherwise only add the altmetric identifier here - the link is generated automatically)
|
||||
- `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
|
||||
- `blog`: Adds a "Blog" button redirecting to the specified link
|
||||
- `code`: Adds a "Code" button redirecting to the specified link
|
||||
- `dimensions`: Adds a [Dimensions](https://www.dimensions.ai/) badge (Note: if DOI or PMID is provided just use `true`, otherwise only add the Dimensions' identifier here - the link is generated automatically)
|
||||
- `html`: Inserts an "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)
|
||||
- `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)
|
||||
- `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)
|
||||
- `website`: Adds a "Website" button redirecting to the specified link
|
||||
|
||||
You can implement your own buttons by editing the [_layouts/bib.html](_layouts/bib.html) file.
|
||||
|
||||
## Changing theme color
|
||||
|
||||
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](_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](_sass/_variables.scss). You can also add your own colors to this file assigning each a name for ease of use across the template.
|
||||
|
||||
## Adding social media information
|
||||
|
||||
You can add your social media links by adding the specified information at the `Social integration` section in the [_config.yml](_config.yml) file. This information will appear at the bottom of the `About` page.
|
||||
|
|
@ -0,0 +1,41 @@
|
|||
# Frequently Asked Questions
|
||||
|
||||
Here are some frequently asked questions. If you have a different question, please check if it was not already answered in the Q&A section of the [GitHub Discussions](https://github.com/alshedivat/al-folio/discussions/categories/q-a). If not, feel free to ask a new question there.
|
||||
|
||||
- [After I create a new repository from this template and setup the repo, I get a deployment error. Isn't the website supposed to correctly deploy automatically?](#after-i-create-a-new-repository-from-this-template-and-setup-the-repo-i-get-a-deployment-error-isnt-the-website-supposed-to-correctly-deploy-automatically)
|
||||
- [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?](#i-am-using-a-custom-domain-eg-foocom-my-custom-domain-becomes-blank-in-the-repository-settings-after-each-deployment-how-do-i-fix-that)
|
||||
- [My webpage works locally. But after deploying, it fails to build and throws `Unknown tag 'toc'`. How do I fix that?](#my-webpage-works-locally-but-after-deploying-it-fails-to-build-and-throws-unknown-tag-toc-how-do-i-fix-that)
|
||||
- [My webpage works locally. But after deploying, it is not displayed correctly (CSS and JS is not loaded properly). How do I fix that?](#my-webpage-works-locally-but-after-deploying-it-is-not-displayed-correctly-css-and-js-is-not-loaded-properly-how-do-i-fix-that)
|
||||
- [Atom feed doesn't work. Why?](#atom-feed-doesnt-work-why)
|
||||
- [My site doesn't work when I enable `related_blog_posts`. Why?](#my-site-doesnt-work-when-i-enable-related_blog_posts-why)
|
||||
- [When trying to deploy, it's asking for github login credentials, which github disabled password authentication and it exits with an error. How to fix?](#when-trying-to-deploy-its-asking-for-github-login-credentials-which-github-disabled-password-authentication-and-it-exits-with-an-error-how-to-fix)
|
||||
|
||||
---
|
||||
|
||||
#### After I create a new repository from this template and setup the repo, I get a deployment error. Isn't the website supposed to correctly deploy automatically?
|
||||
|
||||
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](https://github.com/alshedivat/al-folio#deployment). (Relevant issue: [209](https://github.com/alshedivat/al-folio/issues/209#issuecomment-798849211).)
|
||||
|
||||
#### 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?
|
||||
|
||||
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](https://github.com/alshedivat/al-folio/issues/130).)
|
||||
|
||||
#### My webpage works locally. But after deploying, it fails to build and throws `Unknown tag 'toc'`. How do I fix that?
|
||||
|
||||
Make sure you followed through the [deployment instructions](#deployment) in the previous section. You should have set the deployment branch to `gh-pages`. (Related issue: [1438](https://github.com/alshedivat/al-folio/issues/1438).)
|
||||
|
||||
#### My webpage works locally. But after deploying, it is not displayed correctly (CSS and JS is not loaded properly). How do I fix that?
|
||||
|
||||
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>/`. If all previous steps were done correctly, all is missing is [for your browser to fetch again the site stylesheet](https://github.com/alshedivat/al-folio/issues/1398#issuecomment-1609518404).
|
||||
|
||||
#### Atom feed doesn't work. Why?
|
||||
|
||||
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.
|
||||
|
||||
#### My site doesn't work when I enable `related_blog_posts`. Why?
|
||||
|
||||
This is probably due to the [classifier reborn](https://github.com/jekyll/classifier-reborn) plugin, which is used to calculate related posts. If the error states `Liquid Exception: Zero vectors can not be normalized...`, it means that it could not calculate related posts for a specific post. This is usually caused by [empty or minimal blog posts](https://github.com/jekyll/classifier-reborn/issues/64) without meaningful words (i.e. only [stop words](https://en.wikipedia.org/wiki/Stop_words)) or even [specific characters](https://github.com/jekyll/classifier-reborn/issues/194) you used in your posts. Also, the calculus for similar posts are made for every `post`, which means every page that uses `layout: post`, including the announcements. To change this behavior, simply add `related_posts: false` to the front matter of the page you don't want to display related posts on.
|
||||
|
||||
#### When trying to deploy, it's asking for github login credentials, which github disabled password authentication and it exits with an error. How to fix?
|
||||
|
||||
Open .git/config file using your preferred editor. Change the `https` portion of the `url` variable to `ssh`. Try deploying again.
|
||||
|
|
@ -0,0 +1,203 @@
|
|||
# Installing and Deploying
|
||||
|
||||
The recommended approach for using **al-folio** is to first create your own site using the template with as few changes as possible, and only when it is up and running customize it however you like. This way it is easier to pinpoint what causes a potential issue in case of a bug. The minimum steps required to create your own site are:
|
||||
|
||||
1. Create a new repository using this template. For this, click on `Use this template -> Create a new repository` above the file list. If you plan to upload your site to `<your-github-username>.github.io`, note that the name of your repository MUST BE `<your-github-username>.github.io` or `<your-github-orgname>.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).
|
||||
2. In this new repository, go to `Settings -> Actions -> General -> Workflow permissions` and give `Read and write permissions` to GitHub Actions.
|
||||
3. Open file `_config.yml`, set `url` to `https://<your-github-username>.github.io` and leave `baseurl` **empty**.
|
||||
4. Finally, in the repository page go to `Settings -> Pages -> Build and deployment`, make sure that `Source` is set to `Deploy from a branch` and set the branch to `gh-pages` (NOT to master).
|
||||
5. Wait until the GitHub actions finish, then simply navigate to `https://<your-github-username>.github.io` in your browser. At this point you should see a copy of the theme's [demo website](https://alshedivat.github.io/al-folio/).
|
||||
|
||||
After everything is set up, you can download the repository to your machine and start customizing it. To do so, run the following commands:
|
||||
|
||||
```bash
|
||||
$ git clone git@github.com:<your-username>/<your-repo-name>.git
|
||||
```
|
||||
|
||||
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:
|
||||
|
||||
## 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. To see the template running, open your browser and go to [http://localhost:8888](http://localhost:8888). You should see a copy of the theme's demo website.
|
||||
|
||||
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.
|
||||
|
||||
### 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 the previous command! It will download Ruby and Jekyll and install all Ruby packages again from scratch.
|
||||
|
||||
If you want to use a specific docker version, you can do so by changing `latest` tag to `your_version` in `docker-compose.yaml`. For example, you might have created your website on `v0.10.0` and you want to stick with that.
|
||||
|
||||
- Beta
|
||||
You can also change the docker image tag to slim! It is a slimmed docker image with a size of below 100MBs (same functionality).
|
||||
|
||||
## Local Setup (Legacy)
|
||||
|
||||
For a hands-on walkthrough of running al-folio locally without using Docker, check out [this cool blog post](https://george-gca.github.io/blog/2022/running-local-al-folio/) by one of the community members!
|
||||
|
||||
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/)*).
|
||||
|
||||
```bash
|
||||
$ bundle install
|
||||
# assuming pip is your Python package manager
|
||||
$ pip install jupyter
|
||||
$ bundle exec jekyll serve --lsi
|
||||
```
|
||||
|
||||
To see the template running, open your browser and go to [http://localhost:4000](http://localhost:4000). You should see a copy of the theme's [demo website](https://alshedivat.github.io/al-folio/). Now, feel free to customize the theme however you like. After you are done, remember to **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** `<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>/`.
|
||||
|
||||
### Enabling 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.
|
||||
|
||||
### 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."
|
||||
|
||||
### 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
|
||||
```
|
||||
|
||||
which will (re-)generate the static webpage in the `_site/` folder.
|
||||
Then simply copy the contents of the `_site/` directory to your hosting server.
|
||||
|
||||
If you also want to remove unused css classes from your file, run:
|
||||
|
||||
```bash
|
||||
$ purgecss -c purgecss.config.js
|
||||
```
|
||||
|
||||
which will replace the css files in the `_site/assets/css/` folder with the purged css files.
|
||||
|
||||
**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 deploying directly to `your-domain.com`, leave `baseurl` blank.
|
||||
|
||||
### 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](https://help.github.com/en/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites)). 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` subdirectory 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):
|
||||
|
||||
```bash
|
||||
$ bundle exec jekyll build --lsi --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](https://jekyllrb.com/docs/configuration/options/):
|
||||
|
||||
> 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 behavior, 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`.
|
||||
|
||||
### Upgrading from a previous version
|
||||
|
||||
If you installed **al-folio** as described above, you can configure a [GitHub action](https://github.com/AndreasAugustin/actions-template-sync) to automatically sync your repository with the latest version of the theme.
|
||||
|
||||
Go to Settings -> Actions -> General -> Workflow permissions, give Read and write permissions to GitHub Actions, check "Allow GitHub Actions to create and approve pull requests", and save your changes.
|
||||
|
||||
Then go to Actions -> New workflow -> set up a workflow yourself, setup the following workflow and commit your changes:
|
||||
|
||||
```yaml
|
||||
name: Sync from template
|
||||
on:
|
||||
# cronjob trigger
|
||||
schedule:
|
||||
- cron: "0 0 1 * *"
|
||||
# manual trigger
|
||||
workflow_dispatch:
|
||||
jobs:
|
||||
repo-sync:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
# To use this repository's private action, you must check out the repository
|
||||
- name: Checkout
|
||||
uses: actions/checkout@v3
|
||||
- name: actions-template-sync
|
||||
uses: AndreasAugustin/actions-template-sync@v0.7.3
|
||||
with:
|
||||
github_token: ${{ secrets.GITHUB_TOKEN }}
|
||||
source_repo_path: alshedivat/al-folio
|
||||
upstream_branch: master
|
||||
```
|
||||
|
||||
You will receive a pull request within your repository if there are some changes available in the template.
|
||||
|
||||
Another option is to manually update your code by following the steps below:
|
||||
|
||||
```bash
|
||||
# Assuming the current directory is <your-repo-name>
|
||||
$ git remote add upstream https://github.com/alshedivat/al-folio.git
|
||||
$ git fetch upstream
|
||||
$ git rebase v0.9.0
|
||||
```
|
||||
|
||||
If you have extensively customized a previous version, it might be trickier to upgrade.
|
||||
You can still follow the steps above, but `git rebase` may result in merge conflicts that must be resolved.
|
||||
See [git rebase manual](https://help.github.com/en/github/using-git/about-git-rebase) and how to [resolve conflicts](https://help.github.com/en/github/using-git/resolving-merge-conflicts-after-a-git-rebase) for more information.
|
||||
If rebasing is too complicated, we recommend re-installing the new version of the theme from scratch and port over your content and changes from the previous version manually.
|
||||
496
README.md
496
README.md
|
|
@ -1,25 +1,26 @@
|
|||
# al-folio
|
||||
<!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section -->
|
||||
[maintainers]: https://img.shields.io/badge/maintainers-4-success.svg 'Number of maintainers'
|
||||
<!-- ALL-CONTRIBUTORS-BADGE:END -->
|
||||
|
||||
<div align="center">
|
||||
|
||||
[](https://alshedivat.github.io/al-folio/)
|
||||
|
||||
**A simple, clean, and responsive [Jekyll](https://jekyllrb.com/) theme for academics.**
|
||||
|
||||
---
|
||||
|
||||
[](https://github.com/alshedivat/al-folio/actions/workflows/deploy.yml)
|
||||
[](https://alshedivat.github.io/al-folio/)
|
||||
[](#maintainers)
|
||||
[](https://github.com/alshedivat/al-folio/graphs/contributors/)
|
||||
[![Maintainers][maintainers]](#maintainers)
|
||||
[](https://hub.docker.com/r/amirpourmand/al-folio)
|
||||
[](https://hub.docker.com/r/amirpourmand/al-folio)
|
||||
[](https://hub.docker.com/r/amirpourmand/al-folio)
|
||||
|
||||
[](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/)
|
||||
</div>
|
||||
|
||||
## User community
|
||||
|
||||
|
|
@ -180,26 +181,25 @@ Workshop on Diffusion Models (NeurIPS: <a href="https://diffusionworkshop.github
|
|||
- [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)
|
||||
- [Installing](#installing)
|
||||
- [Customizing](#customizing)
|
||||
- [Features](#features)
|
||||
- [Light/Dark Mode](#lightdark-mode)
|
||||
- [CV](#cv)
|
||||
- [People](#people)
|
||||
- [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)
|
||||
- [Photos, Audio, Video and more](#photos-audio-video-and-more)
|
||||
- [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)
|
||||
- [FAQ](#faq)
|
||||
- [Contributing](#contributing)
|
||||
- [Maintainers](#maintainers)
|
||||
- [All Contributors](#all-contributors)
|
||||
|
|
@ -207,374 +207,64 @@ Workshop on Diffusion Models (NeurIPS: <a href="https://diffusionworkshop.github
|
|||
|
||||
## 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/)!
|
||||
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
|
||||
## Installing
|
||||
|
||||
The recommended approach for using **al-folio** is to first create your own site using the template with as few changes as possible, and only when it is up and running customize it however you like. This way it is easier to pinpoint what causes a potential issue in case of a bug. The minimum steps required to create your own site are:
|
||||
For instalation details please refer to [INSTALL.md](INSTALL.md).
|
||||
|
||||
1. Create a new repository using this template. For this, click on `Use this template -> Create a new repository` above the file list. If you plan to upload your site to `<your-github-username>.github.io`, note that the name of your repository MUST BE `<your-github-username>.github.io` or `<your-github-orgname>.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).
|
||||
2. In this new repository, go to `Settings -> Actions -> General -> Workflow permissions` and give `Read and write permissions` to GitHub Actions.
|
||||
3. Open file `_config.yml`, set `url` to `https://<your-github-username>.github.io` and leave `baseurl` **empty**.
|
||||
4. Finally, in the repository page go to `Settings -> Pages -> Build and deployment`, make sure that `Source` is set to `Deploy from a branch` and set the branch to `gh-pages` (NOT to master).
|
||||
5. Wait until the GitHub actions finish, then simply navigate to `https://<your-github-username>.github.io` in your browser. At this point you should see a copy of the theme's demo website.
|
||||
## Customizing
|
||||
|
||||
After everything is set up, you can download the repository to your machine and start customizing it. To do so, run the following commands:
|
||||
|
||||
```bash
|
||||
$ git clone git@github.com:<your-username>/<your-repo-name>.git
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
#### 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. To see the template running, open your browser and go to `http://localhost:8888`. You should see a copy of the theme's demo website.
|
||||
|
||||
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.
|
||||
|
||||
<details><summary>(click to expand) <strong>Build your own docker image:</strong></summary>
|
||||
|
||||
> 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 the previous command! It will download Ruby and Jekyll and install all Ruby packages again from scratch.
|
||||
|
||||
If you want to use a specific docker version, you can do so by changing `latest` tag to `your_version` in `docker-compose.yaml`. For example, you might have created your website on `v0.10.0` and you want to stick with that.
|
||||
|
||||
- Beta
|
||||
You can also change the docker image tag to slim! It is a slimmed docker image with a size of below 100MBs (same functionality).
|
||||
|
||||
</details>
|
||||
|
||||
---
|
||||
|
||||
#### Local Setup (Legacy)
|
||||
|
||||
For a hands-on walkthrough of running al-folio locally without using Docker, check out [this cool blog post](https://george-gca.github.io/blog/2022/running-local-al-folio/) by one of the community members!
|
||||
|
||||
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
|
||||
```
|
||||
|
||||
To see the template running, open your browser and go to `http://localhost:4000`. You should see a copy of the theme's demo website. Now, feel free to customize the theme however you like. After you are done, remember to **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** `<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. 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.
|
||||
|
||||
<details><summary>(click to expand) <strong>Manual deployment to GitHub Pages:</strong></summary>
|
||||
|
||||
If you need to manually re-deploy your website to GitHub pages, go to Actions, click "Deploy" in the left sidebar, then "Run workflow."
|
||||
|
||||
</details>
|
||||
|
||||
<details><summary>(click to expand) <strong>Deployment to another hosting server (non GitHub Pages):</strong></summary>
|
||||
|
||||
If you decide to not use GitHub Pages and host your page elsewhere, simply run:
|
||||
|
||||
```bash
|
||||
$ bundle exec jekyll build --lsi
|
||||
```
|
||||
|
||||
which will (re-)generate the static webpage in the `_site/` folder.
|
||||
Then simply copy the contents of the `_site/` directory to your hosting server.
|
||||
|
||||
If you also want to remove unused css classes from your file, run:
|
||||
|
||||
```bash
|
||||
$ purgecss -c purgecss.config.js
|
||||
```
|
||||
|
||||
which will replace the css files in the `_site/assets/css/` folder with the purged css files.
|
||||
|
||||
**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 deploying directly to `your-domain.com`, leave `baseurl` blank.
|
||||
|
||||
</details>
|
||||
|
||||
<details><summary>(click to expand) <strong>Deployment to a separate repository (advanced users only):</strong></summary>
|
||||
|
||||
**Note:** Do not try using this method unless you know what you are doing (make sure you are familiar with [publishing sources](https://help.github.com/en/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites)). 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` subdirectory 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):
|
||||
|
||||
```bash
|
||||
$ bundle exec jekyll build --lsi --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](https://jekyllrb.com/docs/configuration/options/):
|
||||
|
||||
> 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 behavior, 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`.
|
||||
|
||||
</details>
|
||||
|
||||
---
|
||||
|
||||
#### Upgrading from a previous version
|
||||
|
||||
If you installed **al-folio** as described above, you can configure a [GitHub action](https://github.com/AndreasAugustin/actions-template-sync) to automatically sync your repository with the latest version of the theme.
|
||||
|
||||
Go to Settings -> Actions -> General -> Workflow permissions, give Read and write permissions to GitHub Actions, check "Allow GitHub Actions to create and approve pull requests", and save your changes.
|
||||
|
||||
Then go to Actions -> New workflow -> set up a workflow yourself, setup the following workflow and commit your changes:
|
||||
|
||||
```yaml
|
||||
name: Sync from template
|
||||
on:
|
||||
# cronjob trigger
|
||||
schedule:
|
||||
- cron: "0 0 1 * *"
|
||||
# manual trigger
|
||||
workflow_dispatch:
|
||||
jobs:
|
||||
repo-sync:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
# To use this repository's private action, you must check out the repository
|
||||
- name: Checkout
|
||||
uses: actions/checkout@v3
|
||||
- name: actions-template-sync
|
||||
uses: AndreasAugustin/actions-template-sync@v0.7.3
|
||||
with:
|
||||
github_token: ${{ secrets.GITHUB_TOKEN }}
|
||||
source_repo_path: alshedivat/al-folio
|
||||
upstream_branch: master
|
||||
```
|
||||
|
||||
You will receive a pull request within your repository if there are some changes available in the template.
|
||||
|
||||
Another option is to manually update your code by following the steps below:
|
||||
|
||||
```bash
|
||||
# Assuming the current directory is <your-repo-name>
|
||||
$ git remote add upstream https://github.com/alshedivat/al-folio.git
|
||||
$ git fetch upstream
|
||||
$ git rebase v0.9.0
|
||||
```
|
||||
|
||||
If you have extensively customized a previous version, it might be trickier to upgrade.
|
||||
You can still follow the steps above, but `git rebase` may result in merge conflicts that must be resolved.
|
||||
See [git rebase manual](https://help.github.com/en/github/using-git/about-git-rebase) and how to [resolve conflicts](https://help.github.com/en/github/using-git/resolving-merge-conflicts-after-a-git-rebase) for more information.
|
||||
If rebasing is too complicated, we recommend re-installing the new version of the theme from scratch and port over your content and changes from the previous version manually.
|
||||
|
||||
---
|
||||
|
||||
### FAQ
|
||||
|
||||
Here are some frequently asked questions.
|
||||
If you have a different question, please ask using [Discussions](https://github.com/alshedivat/al-folio/discussions/categories/q-a).
|
||||
|
||||
1. **Q:** After I create a new repository from this template and setup the repo, I get a deployment error.
|
||||
Isn't the website supposed to correctly deploy automatically? <br>
|
||||
**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](https://github.com/alshedivat/al-folio#deployment) in the previous section.
|
||||
(Relevant issue: [209](https://github.com/alshedivat/al-folio/issues/209#issuecomment-798849211).)
|
||||
|
||||
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? <br>
|
||||
**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](https://github.com/alshedivat/al-folio/issues/130).)
|
||||
|
||||
3. **Q:** My webpage works locally.
|
||||
But after deploying, it fails to build and throws `Unknown tag 'toc'`.
|
||||
How do I fix that? <br>
|
||||
**A:** Make sure you followed through the [deployment instructions](#deployment) in the previous section.
|
||||
You should have set the deployment branch to `gh-pages`.
|
||||
(Related issue: [1438](https://github.com/alshedivat/al-folio/issues/1438).)
|
||||
|
||||
4. **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? <br>
|
||||
**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>/`.
|
||||
If all previous steps were done correctly, all is missing is
|
||||
[for your browser to fetch again the site stylesheet](https://github.com/alshedivat/al-folio/issues/1398#issuecomment-1609518404).
|
||||
|
||||
5. **Q:** Atom feed doesn't work. Why?
|
||||
<br>
|
||||
**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.
|
||||
|
||||
6. **Q:** My site doesn't work when I enable `related_blog_posts`. Why? <br>
|
||||
**A:** This is probably due to the [classifier reborn](https://github.com/jekyll/classifier-reborn) plugin, which is used to calculate
|
||||
related posts. If the error states `Liquid Exception: Zero vectors can not be normalized...`, it means that it could not calculate related
|
||||
posts for a specific post. This is usually caused by [empty or minimal blog posts](https://github.com/jekyll/classifier-reborn/issues/64)
|
||||
without meaningful words (i.e. only [stop words](https://en.wikipedia.org/wiki/Stop_words)) or even
|
||||
[specific characters](https://github.com/jekyll/classifier-reborn/issues/194) you used in your posts. Also, the calculus for similar posts are
|
||||
made for every `post`, which means every page that uses `layout: post`, including the announcements. To change this behavior, simply add
|
||||
`related_posts: false` to the front matter of the page you don't want to display related posts on.
|
||||
|
||||
7. **Q:** When trying to deploy, it's asking for github login credentials, which github disabled password authentication and it exits with an error. How to fix? <br>
|
||||
**A:** Open .git/config file using your preferred editor. Change the `https` portion of the `url` variable to `ssh`. Try deploying again.
|
||||
For customization details please refer to [CUSTOMIZE.md](CUSTOMIZE.md).
|
||||
|
||||
## Features
|
||||
|
||||
### Light/Dark Mode
|
||||
|
||||
This template has a built-in light/dark mode. It detects the user preferred color scheme and automatically switches to it. You can also manually switch between light and dark mode by clicking on the sun/moon icon in the top right corner of the page.
|
||||
|
||||
<p align="center">
|
||||
<img src="assets/img/readme_preview/light.png" width=400>
|
||||
<img src="assets/img/readme_preview/dark.png" width=400>
|
||||
</p>
|
||||
|
||||
---
|
||||
|
||||
### CV
|
||||
|
||||
There are currently 2 different ways of generating the CV page content. The first one is by using a json file located in `assets/json/resume.json`. It is a [known standard](https://jsonresume.org/) for creating a CV programmatically. The second one, currently used as a fallback when the json file is not found, is by using a yml file located in `_data/cv.yml`. This was the original way of creating the CV page content and since it is more human readable than a json file we decided to keep it as an option.
|
||||
There are currently 2 different ways of generating the CV page content. The first one is by using a json file located in [assets/json/resume.json](assets/json/resume.json). It is a [known standard](https://jsonresume.org/) for creating a CV programmatically. The second one, currently used as a fallback when the json file is not found, is by using a yml file located in [_data/cv.yml](_data/cv.yml). This was the original way of creating the CV page content and since it is more human readable than a json file we decided to keep it as an option.
|
||||
|
||||
What this means is, if there is no resume data defined in `_config.yml` and loaded via a json file, it will load the contents of `_data/cv.yml` as fallback.
|
||||
What this means is, if there is no resume data defined in [_config.yml](_config.yml) and loaded via a json file, it will load the contents of [_data/cv.yml](_data/cv.yml) as fallback.
|
||||
|
||||
[](https://alshedivat.github.io/al-folio/cv/)
|
||||
|
||||
---
|
||||
|
||||
### People
|
||||
|
||||
You can create a people page if you want to feature more than one person. Each person can have its own short bio, profile picture, and you can also set if every person will appear at the same or opposite sides.
|
||||
|
||||
[](https://alshedivat.github.io/al-folio/people/)
|
||||
|
||||
---
|
||||
|
||||
### 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`.
|
||||
Your publications' page is generated automatically from your BibTex bibliography. Simply edit [_bibliography/papers.bib](_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](_pages/publications.md). By default, the publications will be sorted by year and the most recent will be displayed first. You can change this behavior and more in the `Jekyll Scholar` section in [_config.yml](_config.yml) file.
|
||||
|
||||
<p align="center"><img src="https://raw.githubusercontent.com/alshedivat/al-folio/master/assets/img/publications-screenshot.png" width=800></p>
|
||||
You can add extra information to a publication, like a PDF file in the [assets/pdf/](assets/pdf/) directory and add the path to the PDF file in the BibTeX entry with the `pdf` field. Some of the supported fields are: `abstract`, `altmetric`, `arxiv`, `bibtex_show`, `blog`, `code`, `dimensions`, `doi`, `eprint`, `html`, `isbn`, `pdf`, `pmid`, `poster`, `slides`, `supp`, `video`, and `website`.
|
||||
|
||||
<details><summary>(click to expand) <strong>Author annotation:</strong></summary>
|
||||
|
||||
In publications, the author entry for yourself is identified by string array `scholar:last_name` and string array `scholar:first_name` in `_config.yml`:
|
||||
|
||||
```yaml
|
||||
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 co-author data format in `_data/coauthors.yml` is as follows,
|
||||
|
||||
```yaml
|
||||
"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.
|
||||
|
||||
</details>
|
||||
|
||||
<details><summary>(click to expand) <strong>Buttons (through custom bibtex keywords):</strong></summary>
|
||||
|
||||
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 an "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
|
||||
- `altmetric`: Adds an [Altmetric](https://www.altmetric.com/) badge (Note: if DOI is provided just use `true`, otherwise only add the altmetric identifier here - the link is generated automatically)
|
||||
- `dimensions`: Adds a [Dimensions](https://www.dimensions.ai/) badge (Note: if DOI or PMID is provided just use `true`, otherwise only add the Dimensions' identifier here - the link is generated automatically)
|
||||
|
||||
You can implement your own buttons by editing the bib.html file.
|
||||
|
||||
</details>
|
||||
[](https://alshedivat.github.io/al-folio/publications/)
|
||||
|
||||
---
|
||||
|
||||
### 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.
|
||||
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.
|
||||
|
||||
<p align="center"><img src="https://raw.githubusercontent.com/alshedivat/al-folio/master/assets/img/projects-screenshot.png" width=700></p>
|
||||
[](https://alshedivat.github.io/al-folio/projects/)
|
||||
|
||||
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`.
|
||||
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](_config.yml) file, create a corresponding folder, and create a landing page for your collection, similar to `_pages/projects.md`.
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -586,23 +276,22 @@ To do this, edit the collections in the `_config.yml` file, create a correspondi
|
|||
|
||||
The theme allows you to create blog posts in the [distill.pub](https://distill.pub/) style:
|
||||
|
||||
<p align="center"><a href="https://alshedivat.github.io/al-folio/blog/2021/distill/" target="_blank"><img src="https://raw.githubusercontent.com/alshedivat/al-folio/master/assets/img/distill-screenshot.png" width=700></a></p>
|
||||
[](https://alshedivat.github.io/al-folio/blog/2021/distill/)
|
||||
|
||||
For more details on how to create distill-styled posts using `<d-*>` tags, please refer to [the example](https://alshedivat.github.io/al-folio/blog/2021/distill/).
|
||||
|
||||
#### Full support for math & code
|
||||
|
||||
**al-folio** supports fast math typesetting through [MathJax](https://www.mathjax.org/) and code syntax highlighting using [GitHub style](https://github.com/jwarby/jekyll-pygments-themes):
|
||||
**al-folio** supports fast math typesetting through [MathJax](https://www.mathjax.org/) and code syntax highlighting using [GitHub style](https://github.com/jwarby/jekyll-pygments-themes). Also supports [mermaid diagrams](https://mermaid-js.github.io/mermaid/#/) and [TikZ figures](https://tikzjax.com/).
|
||||
|
||||
<p align="center">
|
||||
<a href="https://alshedivat.github.io/al-folio/blog/2015/math/" target="_blank"><img src="https://raw.githubusercontent.com/alshedivat/al-folio/master/assets/img/math-screenshot.png" width=400></a>
|
||||
<a href="https://alshedivat.github.io/al-folio/blog/2015/code/" target="_blank"><img src="https://raw.githubusercontent.com/alshedivat/al-folio/master/assets/img/code-screenshot.png" width=400></a>
|
||||
<a href="https://alshedivat.github.io/al-folio/blog/2015/math/" target="_blank"><img src="assets/img/readme_preview/math.png" width=400></a>
|
||||
<a href="https://alshedivat.github.io/al-folio/blog/2015/code/" target="_blank"><img src="assets/img/readme_preview/code.png" width=400></a>
|
||||
</p>
|
||||
|
||||
#### Photos
|
||||
#### Photos, Audio, Video and more
|
||||
|
||||
Photo formatting is made simple using [Bootstrap's grid system](https://getbootstrap.com/docs/4.4/layout/grid/).
|
||||
Easily create beautiful grids within your blog posts and project pages:
|
||||
Photo formatting is made simple using [Bootstrap's grid system](https://getbootstrap.com/docs/4.4/layout/grid/). Easily create beautiful grids within your blog posts and project pages, also with support for [video](https://alshedivat.github.io/al-folio/blog/2023/videos/) and [audio](https://alshedivat.github.io/al-folio/blog/2023/audios/) embeds:
|
||||
|
||||
<p align="center">
|
||||
<a href="https://alshedivat.github.io/al-folio/projects/1_project/">
|
||||
|
|
@ -616,8 +305,9 @@ Easily create beautiful grids within your blog posts and project pages:
|
|||
|
||||
#### GitHub's repositories and user stats
|
||||
|
||||
**al-folio** uses [github-readme-stats](https://github.com/anuraghazra/github-readme-stats) and [github-profile-trophy](https://github.com/ryo-ma/github-profile-trophy)
|
||||
to display GitHub repositories and user stats on the `/repositories/` page.
|
||||
**al-folio** uses [github-readme-stats](https://github.com/anuraghazra/github-readme-stats) and [github-profile-trophy](https://github.com/ryo-ma/github-profile-trophy) to display GitHub repositories and user stats on the `/repositories/` page.
|
||||
|
||||
[](https://alshedivat.github.io/al-folio/repositories/)
|
||||
|
||||
Edit the `_data/repositories.yml` and change the `github_users` and `github_repos` lists to include your own GitHub profile and repositories to the `/repositories/` page.
|
||||
|
||||
|
|
@ -655,52 +345,45 @@ You may also use the following codes for displaying this in any other pages.
|
|||
{% 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.
|
||||
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](_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.
|
||||
**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](_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.
|
||||
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](_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`
|
||||
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`
|
||||
|
||||
---
|
||||
|
||||
#### Related posts
|
||||
|
||||
By default, there will be a related posts section on the bottom of the blog posts.
|
||||
These are generated by selecting the `max_related` most recent posts that share at least `min_common_tags` tags with the current post.
|
||||
If you do not want to display related posts on a specific post, simply add `related_posts: false` to the front matter of the post.
|
||||
If you want to disable it for all posts, simply set `enabled` to false in the `related_blog_posts` section in `_config.yml`.
|
||||
By default, there will be a related posts section on the bottom of the blog posts. These are generated by selecting the `max_related` most recent posts that share at least `min_common_tags` tags with the current post. If you do not want to display related posts on a specific post, simply add `related_posts: false` to the front matter of the post. If you want to disable it for all posts, simply set `enabled` to false in the `related_blog_posts` section in [_config.yml](_config.yml).
|
||||
|
||||
## FAQ
|
||||
|
||||
For frequently asked questions, please refer to [FAQ.md](FAQ.md).
|
||||
|
||||
## Contributing
|
||||
|
||||
Contributions to al-folio are very welcome!
|
||||
Before you get started, please take a look at [the guidelines](CONTRIBUTING.md).
|
||||
Contributions to al-folio are very welcome! Before you get started, please take a look at [the guidelines](CONTRIBUTING.md).
|
||||
|
||||
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.
|
||||
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
|
||||
|
||||
Our most active contributors are welcome to join the maintainers team.
|
||||
If you are interested, please reach out!
|
||||
Our most active contributors are welcome to join the maintainers team. If you are interested, please reach out!
|
||||
|
||||
<!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->
|
||||
<!-- prettier-ignore-start -->
|
||||
|
|
@ -723,15 +406,12 @@ If you are interested, please reach out!
|
|||
|
||||
### All Contributors
|
||||
|
||||
<a href="https://github.com/alshedivat/al-folio/graphs/contributors">
|
||||
<img src="https://contrib.rocks/image?repo=alshedivat/al-folio&max=36" />
|
||||
<a href="https://contrib.rocks">
|
||||
<img src="https://contrib.rocks/image?repo=alshedivat/al-folio" />
|
||||
</a>
|
||||
|
||||
Made with [contrib.rocks](https://contrib.rocks).
|
||||
|
||||
## License
|
||||
|
||||
The theme is available as open source under the terms of the [MIT License](https://github.com/alshedivat/al-folio/blob/master/LICENSE).
|
||||
|
||||
Originally, **al-folio** was based on the [\*folio theme](https://github.com/bogoli/-folio) (published by [Lia Bogoev](https://liabogoev.com) and under the MIT license).
|
||||
Since then, it got a full re-write of the styles and many additional cool features.
|
||||
Originally, **al-folio** was based on the [\*folio theme](https://github.com/bogoli/-folio) (published by [Lia Bogoev](https://liabogoev.com) and under the MIT license). Since then, it got a full re-write of the styles and many additional cool features.
|
||||
|
|
|
|||
24
_config.yml
24
_config.yml
|
|
@ -59,6 +59,7 @@ max_width: 800px
|
|||
# Open Graph & Schema.org
|
||||
# -----------------------------------------------------------------------------
|
||||
# Display links to the page with a preview object on social media.
|
||||
# see https://schema.org/docs/faq.html for more information
|
||||
serve_og_meta: false # Include Open Graph meta tags in the HTML head
|
||||
serve_schema_org: false # Include Schema.org in the HTML head
|
||||
og_image: # The site-wide (default for all links) Open Graph preview image
|
||||
|
|
@ -110,9 +111,12 @@ contact_note: >
|
|||
# Analytics and search engine verification
|
||||
# -----------------------------------------------------------------------------
|
||||
|
||||
# For Google Analytics, see https://support.google.com/analytics/answer/10447272?hl=en&ref_topic=14088998&sjid=5129943941510317771-SA#zippy=%2Cgoogle-sites
|
||||
# and follow the instructions for Google Sites. You will need to create a Google Analytics property and copy the Google tag ID.
|
||||
google_analytics: # your Google Analytics measurement ID (format: G-XXXXXXXXXX)
|
||||
cronitor_analytics: # cronitor RUM analytics site ID (format: XXXXXXXXX)
|
||||
|
||||
# For Google Search Console, see https://support.google.com/webmasters/answer/9008080?hl=en#meta_tag_verification&zippy=%2Chtml-tag
|
||||
google_site_verification: # your google-site-verification ID (Google Search Console)
|
||||
bing_site_verification: # out your bing-site-verification ID (Bing Webmaster)
|
||||
|
||||
|
|
@ -133,13 +137,12 @@ related_blog_posts:
|
|||
max_related: 5
|
||||
|
||||
# Giscus comments (RECOMMENDED)
|
||||
# Follow instructions on https://giscus.app/ to setup for your repo to fill out
|
||||
# the information below.
|
||||
# Follow instructions on https://giscus.app/ to setup for your repo to fill out the information below.
|
||||
giscus:
|
||||
repo: # <your-github-user-name>/<your-github-repo-name>
|
||||
repo_id: # leave empty or specify your repo_id (see https://giscus.app/)
|
||||
repo_id: # leave empty or specify your repo_id (see https://giscus.app/)
|
||||
category: Comments # name of the category under which discussions will be created
|
||||
category_id: # leave empty or specify your category_id (see https://giscus.app/)
|
||||
category_id: # leave empty or specify your category_id (see https://giscus.app/)
|
||||
mapping: title # identify discussions by post title
|
||||
strict: 1 # use strict identification mode
|
||||
reactions_enabled: 1 # enable (1) or disable (0) emoji reactions
|
||||
|
|
@ -303,7 +306,7 @@ enable_publication_badges:
|
|||
dimensions: true # Dimensions badge (https://badge.dimensions.ai/)
|
||||
|
||||
# Filter out certain bibtex entry keywords used internally from the bib output
|
||||
filtered_bibtex_keywords: [abbr, abstract, arxiv, bibtex_show, html, pdf, selected, supp, blog, code, poster, video, slides, website, preview, altmetric]
|
||||
filtered_bibtex_keywords: [abbr, abstract, altmetric, arxiv, bibtex_show, blog, code, html, pdf, poster, preview, selected, slides, supp, video, website]
|
||||
|
||||
# Maximum number of authors to be shown for each publication (more authors are visible on click)
|
||||
max_author_limit: 3 # leave blank to always show all authors
|
||||
|
|
@ -353,18 +356,15 @@ imagemagick:
|
|||
# -----------------------------------------------------------------------------
|
||||
|
||||
enable_google_analytics: false # enables google analytics
|
||||
enable_cronitor_analytics: false # enables cronitor RUM analytics
|
||||
enable_cronitor_analytics: false # enables cronitor RUM analytics
|
||||
enable_google_verification: false # enables google site verification
|
||||
enable_bing_verification: false # enables bing site verification
|
||||
enable_masonry: true # enables automatic project cards arrangement
|
||||
enable_math: true # enables math typesetting (uses MathJax)
|
||||
enable_tooltips: false # enables automatic tooltip links generated
|
||||
# for each section titles on pages and posts
|
||||
enable_tooltips: false # enables automatic tooltip links generated for each section titles on pages and posts
|
||||
enable_darkmode: true # enables switching between light/dark modes
|
||||
enable_navbar_social: false # enables displaying social links in the
|
||||
# navbar on the about page
|
||||
enable_project_categories: true # enables categorization of projects into
|
||||
# multiple categories
|
||||
enable_navbar_social: false # enables displaying social links in the navbar on the about page
|
||||
enable_project_categories: true # enables categorization of projects into multiple categories
|
||||
enable_medium_zoom: true # enables image zoom feature (as on medium.com)
|
||||
enable_progressbar: true # enables a horizontal progress bar linked to the vertical scroll position
|
||||
|
||||
|
|
|
|||
Binary file not shown.
|
Before Width: | Height: | Size: 800 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 182 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 186 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 188 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 842 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 211 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 216 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 86 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 70 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 100 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 236 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 111 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 149 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 233 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 101 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 352 KiB |
|
Before Width: | Height: | Size: 950 KiB After Width: | Height: | Size: 950 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 317 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 165 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 134 KiB |
Loading…
Reference in New Issue