Bioconductor conference 2023 website

Website: https://bioc2023.bioconductor.org/

This repository contains material for the Bioconductor annual conference. View the corresponding GitHub repo. Created using BioC_template.

Run Hugo to preview the webpage locally.

rm -rf public; hugo --verbose; hugo server --disableFastRender --verbose

Schedule generation

• Prepare the schedule table spreadsheet by copying information from the tentative schedule and the Openreview reviews spreadsheet.

  • Each line describes either single event (Keynote, workshop, etc.) or multiple events (Short talks track).
    • Data for multiple event entries is stored at the end of the spreadsheet (Note: the format may change, Issue 17)
  • For the "time" column, set the format to custom "hh:mm" (IMPORTANT)
  • Avoid using special characters, especially, "/".
  • If quotes need to be used, use single quotes.

• Check 1_create_yaml.R for the correct sheet=XYZ sheet from the schedule table spreadsheet

• Run the following command in the terminal in the base directory:

Rscript --vanilla 1_create_yaml.R; bash 2_create_abstracts.sh; bash 3_create_tracks.sh

Manually adding data for the schedule

• Note: not needed if the schedule was automatically generated from the schedule table spreadsheet using the steps above.

• Data for the abstracts and other elements for the schedule table should be located in data/abstracts/. This folder is populated by 1_create_yaml.R from the "schedule table" spreadsheet.

There are three types of abstracts.

1. papers. Name format: day1_1315_longWorkshop_paper25.yaml.
2. tracks. Name format: day1_0900_shortTalksSysEpi_track.yaml.
3. All other elements that will be added to the schedule.

Abstract file name format: day[1-3]_HHMM_type_paper/track#.yaml. The abstracts should all contain these fields. If any field isn't used, it should remain blank.

day: "" # Day of a conference, 'day1', 'day2' etc. format
title: "" # A string with the full title.
paper: "" # Number of paper or track. Valid options: paper# or track#. For example, paper2, track1, etc. track is only used for the short talks tracks. If 'track#', then the 'talks:' field should list the associated papers, e.g., ["paper34","paper78","paper45","paper37","paper8"]
session_type: "" # String with the session type, e.g., "Short talk", "Short talks track", "Package demo", "Workshop".
authors: "" # String with the authors separated by comma.
presenting_author: "" # Author who will present. The first author by default.
affiliation: "" # String with the affiliation.
abstract: "" # String with the abstract. Sometimes there are quotes in the text which should be escaped.
time: "" # The time in 24h format. Example: 1300 for 1 PM.
talks: "" # This field is only for the short talk tracks. This should list the number of papers under this track. This should be a YAML array. Example: ["paper10", "paper20"]
github: "" # Link to the associated dode repository
presenting_author: "" # Presenting author. If multiple, as for the track sessions, additional 'presenting_author#' fields should be filled.
twitter: "" # A full url to twitter or other social media platform. If multiple, as for the track sessions, additional 'twitter#' fields should be filled.
youtube: "" # Link to youtube video when available. If multiple, as for the track sessions, additional 'youtube#' fields should be filled.
details: "" # Currently not used
level: "" # Valid only for workshops and package demos. Can be 'Beginner', 'Intermediate', 'Advanced'
orchestra: "" # Should be 'yes' for workshops and package demos

• The content/abstracts/ directory contains the individual pages for the abstracts. This directory could be ignored as it will be updated with the 2_create_abstracts.sh and 3_create_tracks.sh bash scripts. These scripts convert the elements in data to content pages.

• Workshops and package demo yaml files will be processed by workshops.md to create the "WORKSHOPS & DEMOS" page.

======

data

YAML files that need to be adjusted for each conference.

abstracts

YAML files for every event. Workshop_paper are processed by content/workshops.md and layouts/shortcodes/workshops.html. All events are processed by layouts/shortcodes/schedule.html.

carousel

YAML files for the carousel panels. Processed by the main theme.

clients

YAML files for sponsors. Processed by the main theme and layouts/shortcodes/sponsors.html

organizers

YAML files for co-chairs and committee. Processed by content/organizers.md, layouts/shortcodes/cochairs.html and layouts/shortcodes/committee.html.

speakers

YAML files for each speaker. Processed by layouts/partials/speakers.html.

Disclaimer

This template was created using the modified hugo-universal-theme. See the demo web site, the original github repository and the exampleSite files. Template by Bootstrapious. Ported to Hugo by DevCows. The theme is added as selected files, not as a submodule, for easier modification.