List of possible chores

[Rotzbua]

I don't know what the current development status of the website is, but here is a list of things that could be done to bring the website up to date. Most todos are less work than they appear.

• [ ] Add missing lang attributes
• [ ] Add alternative text to images
• [ ] Add <meta name="viewport"> tag
• [ ] Remove invalid trailing slashes on void html5 elements
• [ ] Remove historic browser fixes for IE
• [ ] Remove outdated vendor specific code
• [ ] Remove leftovers from outdated services like flattr
• [ ] Fix mixed content (gallery)
• [ ] Fix broken links
• [ ] Fix usage of deprecated js api https://developer.mozilla.org/en-US/docs/Web/API/Navigator/appVersion
• [ ] Fix invalid html e.g. <ul> and <ol> must only directly contain <li>, <script> or <template> elements
• [ ] Move inline CSS to style file
• [ ] Migrate js to ES2015
• [ ] Update dependencies
  • [ ] jquery to latest v1 (eol) or v3
  • [ ] jquery addons
  • [ ] font awesome

If you want me to solve some of them please send me feedback.

[t-paul]

I don't think there was a wider discussion yet, but I'd prefer to move to some framework which removes all the duplication in every HTML page on the source side. But that said, I'm not too fond of deploying or maintaining some content management site like WordPress or so.

Assuming moving to a totally different solution is not on the table, I see 2 main options:

• Leverage more of the features of Jekyll for generating the site
• Using some other framework and deploy via GitHub action (which seems to be the recommended solution now anyway)

Personally I had to spend some time with Svelte kit for a project at work. This seems to be a nice option as it's both providing a good framework for development while also allowing fully rendered/generated pages without the need for a back-end service. I've used that for the GSoC Project Proposal page, generating the page from the issues list (Source Repo) and that worked quite well.

@kintel, what do you think?