An accessiblity concern - the HTML title of each page generated by Pelican is "Varia", not the actual title of each page, e.g. "PrePostPrint Local Meetup". Proposal to add the actual title of the page in the Jinja template, essentially to have this a variable, please and thank you
An accessiblity concern - the HTML title of each page generated by Pelican is "Varia", not the actual title of each page, e.g. "PrePostPrint Local Meetup". Proposal to add the actual title of the page in the Jinja template, essentially to have this a variable, please and thank you
Yes, we should comply to accessiblity standards with our website.
Last time I checked with online validators there were 30-40 accessiblity issues with the html of the Varia website.
So I am a bit unsure whether we can fix this pelican website or we should make something new, and then in the meanwhile address many other issues with the Varia website. Such as it's event centric lay out, no possibility to properly display ongoing events.
Make/Build/Find something that works for the collective as a whole. (Toolshed)
But if we need a quick fix in the meantime, I can always have a look. :)
Yes, we should comply to accessiblity standards with our website.
Last time I checked with online validators there were 30-40 accessiblity issues with the html of the Varia website.
So I am a bit unsure whether we can fix this pelican website or we should make something new, and then in the meanwhile address many other issues with the Varia website. Such as it's event centric lay out, no possibility to properly display ongoing events.
Make/Build/Find something that works for the collective as a whole. (Toolshed)
But if we need a quick fix in the meantime, I can always have a look. :)
An accessiblity concern - the HTML title of each page generated by Pelican is "Varia", not the actual title of each page, e.g. "PrePostPrint Local Meetup". Proposal to add the actual title of the page in the Jinja template, essentially to have this a variable, please and thank you
Yes, we should comply to accessiblity standards with our website.
Last time I checked with online validators there were 30-40 accessiblity issues with the html of the Varia website.
So I am a bit unsure whether we can fix this pelican website or we should make something new, and then in the meanwhile address many other issues with the Varia website. Such as it's event centric lay out, no possibility to properly display ongoing events.
Make/Build/Find something that works for the collective as a whole. (Toolshed)
But if we need a quick fix in the meantime, I can always have a look. :)