Maëva Brunelles

Hello @HeavyThumper, Thanks for your PR! About the failure check, it's on `black` side, it's fixed with this [PR](https://github.com/pelican-plugins/seo/pull/53/files#diff-63a9c44a44acf85fea213a857769990937107cf072831e1a26808cfde9d096b9R21). By the way, did you launch tests in local? Because [this...

Hello @buanzo, Feel free to open a PR with the patch and tests that ensure the canonical URL is well generated :)

Hi @Sogolumbo, thanks for raising this. To fix this, I would go for this [here](https://github.com/pelican-plugins/seo/blob/b1aadb6ab21e6fbc2bbaa08a5a5cdfff35c2d726/pelican/plugins/seo/seo_enhancer/html_enhancer/article_schema_creator.py#L64): ``` if self._author: schema_article["author"] = {"@type": "Person", "name": self._author.name} ``` Same issue for `category`. Feel...

Indeed. I suppose that the fix you propose couldn't work on Unix with `"file:///"`. I need some time to do some tests.

Hi @ysard and thanks for your report. From a SEO point of view, template creators should never encapsulate title in a h1 tag. Website creators should be able to customize...

Ok, got it, you're right. Moreover, on the template you link, even without considering the structure of article content on Markdown/Rest, there is already two `h1` tags: https://github.com/Pelican-Elegant/elegant/blob/2a689472e42e159b3de2ff5b7bfd5434a9cc63d4/templates/article.html#L35 and https://github.com/Pelican-Elegant/elegant/blob/2a689472e42e159b3de2ff5b7bfd5434a9cc63d4/templates/article.html#L35....