Closed redeagletwo closed 2 years ago
I started to do this, but the structure of the json files cause problems when reading the information. This results in the page being unfunctional.
I should be able to write a simple js script to do one-time conversion to separate markdown files
Done for the seminars https://github.com/HirodaiSoken/website/tree/oldcontents
What to do for events and others? What kind of format are we going to use for the md file?
Thank you for doing that. The events and others have a loser format with maybe something similar to the award event. This is my suggestion,
event/other title.
date of the event description of the person/people involved
summary of the event in a short paragraph external links and pictures if allowed
If there is no information about the date or links/pictures. Then maybe we have leave them blank. Also, we received some feedback about the seminar and event sections with the details in #25
Some notes to remember for later;
@Cendikiaabdi There is a bug with the resulting markdown files from the .js. All the files are set to a month backwards. Meaning, I think the script started with 00 and iterated up to 11 for the months. So all the months need a +1.
Currently, the old information for events and schedules are inside json files.
/data/schedule_2018.json
/data/schedule_2019.json
/data/schedule_2020.json
/data/schedule_2021.json
I think it is too diffcult to create individual pages for each event. As such I think it is best to create a single page that summerizes the events. That page could be located under
/content/events/<year>/
. This should be possible using the markdown or Hugo, but I have not investigated the details on how.