I can give you most of a website for satRdays events, ready (almost) out of the box. I have a number of sections to help you out:
- Event description
- Event location
- With map
- Embedded tickets
- Tito
- Ticket Tailor
- Eventbrite
- Call for papers
- Sessionize
- Speaker Bios
- Talk descriptions
- Schedule
- Important Dates
- Links to satRdays Code of Conduct and Diversity materials
-
Open Git Bash.
-
Create a bare clone of the repository.
git clone --bare satRdays/satRday_site_template.git
- Mirror-push to the new repository.
cd satRday_site_template.git
git push --mirror https://github.com/satRdays/[cityYEAR].git
- Remove the temporary local repository you created in step 1.
cd ..
rm -rf satRdays/satRday_site_template.git
The file config.toml gives you access to a number of points on the site, mostly using site params.
A high level overview of these features:
enable
- boolean to render or hide that section
title
/subtitle
/description
/button text
/...- strings to display text in that position
bg
- boolean to toggle lightly shaded backgrounds on or off for that section
eid
/accountevent
/eventviewid
/CfSpage
- strings that are part of a url (that are usually part of an iframe) to link to a service for tickets/Call for papers
- Talks are generated from
Talk0X.yaml
files indata/projects/
- Each talk should have similar structures (some values may be missed or blank) based on the included examples, and be in its own file
- Speaker/organiser bios are generated from
Speaker0X.toml
files indata/speakers/
- Each speaker should have similar structures (some values may be missed or blank) based on the included examples, and be in its own file
In the hopefully rare event that even more specific material is needed you can explore the following. Make use of the hugo inheritance method to override defaults where applicable, rather than modify the defaults in place.
- Copy the base
hugo-satrdays-theme/static/css/style.css
into/static/css/style.css
- This will now be the style sheet for your website, overriding the themes
- Either
- find a partial from
/layouts/partials
in the existing themes you want to base your work on, copy it to the project/layouts/partials
, and modify the copy - write a new
myfile.html
from scratch and include it in the project/layouts/partials
- find a partial from
- then make sure that it is referenced in
index.html
I am a Hugo website, with two themes. Agency provides the base layer of theming, with a custom satRday theme which overides some areas.
As the design is strongly based on the hugo-agency-theme
, naming conventions are not obvious in certain situations
- The
talks
section ofhugo-satrdays-theme
is built from theportfolio
section of thehugo-agency-theme
- The
important dates
section ofhugo-satrdays-theme
is built from theabout
section of thehugo-agency-theme
- The
speakers
section ofhugo-satrdays-theme
is built from theteam
section of thehugo-agency-theme
- The
sponsors
section ofhugo-satrdays-theme
is built from theclients
section of thehugo-agency-theme