CSS Improvements for #CHR2025: flaws e.g., CSS in individual .md files instead of integration of main.css

[MinaAlmasi]

This is an issue for bookkeeping in case, this setup is re-used for CHR2025!

Since I am no web developer, I have been sort of "hacking" the CSS and learning on the go. It is likely that any web developer will spot room for improvement. I have noted down some considerations that might be worth to take into account next year:

Not using main CSS enough

I have had issues with CSS not rendering properly when writing in main.css directly - at least not locally - which makes it difficult to design on the go. I raised this issue with @pbvahlst, and due to time constraints, I have not spent time bug-fixing, and instead just done custom CSS for each .md file sperately. (This could also have something to do with me using NPM instead of HUGO to build the website)

This has resulted in repetitive CSS (e.g., identical code in venue.md and about.md) which could ultimately lead to consistency issues (e.g., if I change something in venue.md but forget to do so in about.md). There is also identical CSS in all paperX.md files for each paper, but they are auto-generated in the repository cohure/website-automatisation.

This is not a big issue, and I have tried to keep it as consistent and coherent as possible, but may be worth improving on in the next iteration.

Check list (for where CSS can be streamlined):

• About.md and venue.md (and frontpage index.md)
• All .md files in /announcements and /venue

Redundant CSS

Some custom CSS may redundant and could be simplified. In general, it might be worth to take a look at the CSS to streamline it.