- Event's title, location, and date
- Welcoming remark section with video
- Speaker with name, title, pop up profile section
- About section with options to navigate to subpages
- Event Sponsors' pictures section
- Contact Us section
- Refer to Formspree on how to setup the contact form.
- Table with time and event title columns
- Speaker's name is hilighted in different color and speaker's position/title is in italic.
Two different design:
- profile picture with name and email
- user profile with picture, title, position, and profile
- Google Map (need to replace it with your own API key)
- Just a typical FAQs page
- Sections to talk about mission, vision, objectives, and history about your event
- A page to redirect to a sign up page
- Google Analytics built in (replace
UA-xxxxxxxx-x
with your personal analytics verification key in_includes/2016_data/head.html
) - SEO (check
_config.yml
) - Customized 404 Page Not Found Page
- Designed to be futureproof as you can create a subpages for each year (eg. YOUR-LINK.github.io/2015, YOUR-LINK.github.io/2016, etc)
- Header with icon logo defined, but removed from source code.
- Website logo in SVG defined, but removed from source code.
- Display PDF from Google Drive
- For first time user, you have to install Ruby and NodeJS. You may follow my installation guide in my Jekyll tutorial or Ruby on Rails Tutorial for Windows, Linux, and MacOS (installation videos are included).
- Install Jekyll by using the command
gem install jekyll
. - Then, install Jekyll Sitemap and Jekyll SEO gems by using the command
gem install jekyll-sitemap
andgem install jekyll-seo-tag
. - Start your localhost server by using the command
jekyll serve
. Make sure that you are at the root directory of your folder before using this command. - Your site should be accessible at
localhost:4000
. - For additional information about Jekyll, refer to the official website.
Note: If you forked it and edited _config.yml
via the online editor on Github, the Github pages may not work. In that case, you will make any changes (add a new line, etc) and push the changes from your local machine via CLI or GUI git.
- The main stylesheet is stored
/css/2016_style
. Both2016
and2017
are sharing the same stylesheet. - In
/css/2016_style/img
you will find where the pictures in/2016
are stored at. You will find the images of speakers in/css/2017_style/img
. This setup is to ensure that we can easily to move from year to year by creating new folders. _2016_pages
and_2017_pages
are the folders that store subpages._2016_data
and_2017_data
are the folders that store each sections in home page. Those sections are can be removed by removing or commenting out theinclude
code in_layout/2016_home.html
or_layout/2017_home.html
._data/twenty_16/
and_data/twenty_17/
containsdata
files for agenda, faqs, home about section data, speakers, and team members information. The data file is in the format of.yml
. The reason why the folders are namedtwenty_16
andtwenty_17
are due to liquid syntax will throw errors if the name contains integer.- In order to view PDF correctly, sharing setting in Google Drive must set to "Public on the web".