JekyllStarter

jekyll-conference-template — Jekyll Starter Template

By hrishikeshrt

A Jekyll-based academic conference website template that configures conference information, news, organization structure, venue, submissions, and registration through YAML files in the _data directory.

Explore the design

Compare the page layouts and mobile experience. Open any screenshot for a closer look.

2 previews
Desktop homepage1 / 2
Desktop captureTop of page

Actual screenshot captured by the server browser.

All pages & views 2

Screenshots show visual appearance; interactive behavior may differ.

Recorded 2026-10-04View source

What stands out

A quick read of the recorded project description.

01

Built with Jekyll, conference information is centrally configured in multiple YAML files under the _data directory

02

conference.yml covers conference full name, abbreviation, description, location, logo, slides, navigation menu, sponsors, important dates, and social media

03

organization.yml distinguishes program chairs, organizing committee, steering committee, and technical program committee

04

venue.yml provides address, accommodation, and route map; submission.yml and registration.yml manage submission and registration information respectively

05

Past deadlines are automatically displayed with strikethrough on the page

06

Supports two publishing methods: manual deployment and GitHub Pages (GitHub Actions)

Template Details

This is an academic conference website template built with Jekyll, intended for scenarios requiring a conference official website. The template splits conference-related content into multiple data files managed centrally in the _data directory, including conference.yml (conference full name, abbreviation, description, location, logo, slides, navigation menu, sponsors, important dates, social media), news.yml (news), organization.yml (program chairs, organizing committee, steering committee, technical program committee), venue.yml (address, accommodation, route map), submission.yml (submission instructions), and registration.yml (registration information). Past deadlines in important dates are automatically displayed with strikethrough. The template supports configuring Google Analytics in _config.yml, and the navigation bar social media currently supports Facebook and Twitter. There are two deployment methods: manual deployment requires installing Ruby, RVM, Jekyll, and Bundler, deleting .github/workflows/, symlinking Gemfile to Gemfile.local, adjusting the publish path in the Makefile, using make serve for local testing, and make publish to build and copy to the publish location; GitHub Pages deployment requires the repository to be public and enabling GitHub Pages to use GitHub Actions, creating .github/workflows/ and copying workflows/release.yml to .github/workflows/release.yml, then symlinking Gemfile to Gemfile.github. The repository uses the MIT license, allowing free use, modification, commercial use, and distribution, but third-party assets such as demo images, fonts, and icons must be checked against their respective licenses.

JekyllStarter

Is it right for your project?

Use Cases

  • Building an official website for an academic conference that includes conference introduction, important dates, organization structure, and venue information
  • Needing to display program chairs, organizing committee, steering committee, and technical program committee separately by committee category
  • Maintaining conference content through YAML data files rather than directly modifying pages
  • Publishing a conference website using GitHub Pages or a self-owned server

Suitable For

  • Developers or conference organizers familiar with Jekyll and YAML configuration
  • Teams needing to quickly build an academic conference official website and centrally manage conference data
  • Users planning to publish a static conference website via GitHub Pages or manual build

Getting started & customization

Use these recorded setup notes alongside the repository instructions for your chosen version.

  1. 1

    Manual deployment requires first installing Ruby, RVM, Jekyll, and Bundler; see INSTALL.md in the repository for specific installation steps

  2. 2

    For manual deployment, delete .github/workflows/, change the Gemfile symlink to point to Gemfile.local, and adjust the publish path in the Makefile

  3. 3

    For GitHub Pages deployment, ensure the repository is public and enable GitHub Pages to use GitHub Actions, copy workflows/release.yml to .github/workflows/release.yml, and change the Gemfile symlink to point to Gemfile.github

  4. 4

    Use make serve for local preview, and make publish to build and copy to the publish location

  5. 5

    Google Analytics is configured in _config.yml; third-party assets such as demo images, fonts, and icons must be checked against their respective licenses

Read repository instructions

License & source material

Usage conditions & limitations

Free to use · keep license notice

This entry covers the free version under the MIT license in the public repository; the free scope is the code of this version and does not mean external services or third-party assets are free.

Must comply with when using

  • Free use, modification, commercial use, and distribution of this version's code are permitted.
  • When distributing copies or substantial portions of the code, retain the original author's copyright notice and the full MIT license notice.
  • The code is provided as is; warranties and limitations of liability are governed by the original license and applicable law.

Additional costs & items to verify

  • The template supports configuring Google Analytics in _config.yml, which is an external third-party service; using this analytics feature requires registering a Google Analytics account and complying with its terms of service, and not configuring it does not affect other website features.
  • When using GitHub Pages deployment, the repository must be public and GitHub Pages must be enabled and set to use GitHub Actions, i.e., it depends on the GitHub platform and its account, which is an external service requirement.
  • Demo images, fonts, icons, and other third-party assets must be checked against their respective licenses and cannot be judged solely by the code's MIT license.
  • External services such as domain, hosting, database, payment, or AI may incur additional charges.
View Original Text Basis

Permission is hereby granted, free of charge

Original License Text

Google Analytics: in `_config.yml`

Original README

Ensure that the repository is public and GitHub Pages are enabled and set to use GitHub Actions.

Original README
https://github.com/hrishikeshrt/jekyll-conference-template/blob/master/LICENSEhttps://github.com/hrishikeshrt/jekyll-conference-template/blob/master/README.md

Compiled by DeepSeek based on repository license and README ·2026-10-04. Results only cover the materials read; dependencies, images, fonts, and subsequent term changes are subject to their respective original texts.

Project checks & description sources

Template Information

Source platforms
GitHub
Documentation and maintenance reference score
Partly documented · 68 / 100
Technologies
Jekyll
Website type
Starter
How this score is calculated

Our heuristic uses license records (up to 30), a demo link (12), a preview (10), stars (15), recorded maintenance (15), description completeness (8), feature records (5) and classification data (5). It is not a code, security or performance test, or a Google score. A link does not establish tested functionality.

What to verify for this project

Repository update recorded
2024-01-21
Screenshot last checked
2026-10-04

A demo link is listed. Check it with your own content and viewport sizes; its presence does not confirm that forms, authentication or payments work.

The catalog identifies Jekyll as the primary stack. Check the actual dependency manifest and lockfile for versions and hosting requirements. These notes use recorded metadata, not a code audit or a deployment test.

Use a selection guide →

How this description was prepared

AI-assisted description based on catalog records and repository material. Repository authors are not automatically the reviewers of this description.

Review declaration: [email protected] · 2026-10-04

Inspect the recorded source material

SHA-256: 9376afe8f66e182eb34571b935d2a43a80c77229cbe84108a802c7bdb9f2af72

2026-10-04T03:21:02.501Z

Source file / repository
# Jekyll-based Conference Template

An academic conference website template built using Jekyll.

## Configuration

Data Files under `_data` to configure all conference related information.

- `conference.yml`
  - `full_title`: conference fullname e.g., First xxx conference on xxxx, 2017.
  - `short_title`: conference shortname e.g., xxxx2017
  - `description`: short description about the conference (< 160 char)
  - `location`: conference location
  - `logo_path`: conference logo
  - `slideshow`: images slideshow
  - `navbar`: navigation menu.
  - `sponsors`: sponsor section.
  - `deadlines`: important dates of deadlines, pass-due date will be automatically printed with del line.
  - `social_media`: social media on the navbar. (current support facebook and twitter.)
- `news.yml`: news section
- `organization.yml`: committees
  - `programm_chair`: program chair
  - `organizing_committees`: organizing committees
  - `steering_committees`: steering committees
  - `technical_program_committees`: technical program committees
- `venue.yml`: information about venue
  - `address`: full address
  - `accommodation`: accommodation details
  - `direction`: path to image containing directions
- `submission.yml`: submission instructions
- `registration.yml`: registration information

- Google Analytics: in `_config.yml`

## Deployment

### Manual

* Setup Ruby, RVM, Jeykyll, Bundler.
  - Check installation instructions at [INSTALL.md](INSTALL.md).
* Remove `.github/workflows/`
* Change target of the symbolic `Gemfile` to `Gemfile.local`
  ```
  rm Gemfile
  ln -s Gemfile.local Gemfile
  ```
* Adjust release path in `Makefile`
* Test locally, `make serve`
* Build and copy to publish location, `make publish`
* Commit changes to the publish location

### GitHub Pages

* Ensure that the repository is public and GitHub Pages are enabled and set to use GitHub Actions.
* Create `.github/workflows`
* Copy `workflows/release.yml` to `.github/workflows/release.yml`
* Change target of the symbolic `Gemfile` to `Gemfile.github`
  ```
  rm Gemfile
  ln -s Gemfile.github Gemfile
  ```
Report a correction

Explore similar templates

Compare previews and descriptions within the same stack and category.