Explicit content Sectioning & basic Schema.org usage for HTML version

[fititnt]

See #7

---

This is the actual schema generated by the the README.md. It's not bad considering it's the github default output

If we generate a new version with HTML, lets use some extra logic for structured data. For now I'm not sure the best types to use for our type of content, but at least use something generic to start.

[fititnt]

(The link to preview the last image is https://search.google.com/structured-data/testing-tool/u/0/#url=https%3A%2F%2Ftags.etica.ai%2Fpoc.html.)

And this is our outline, direct link https://validator.w3.org/nu/?doc=https%3A%2F%2Ftags.etica.ai%2Fpoc.html&showoutline=yes.

The default does not use tags like <section>, <article>, <aside>, etc. So heading level is implicit. Let's make it more explicit.

Both images can be used later as reference

[fititnt]

Raw HTML is so flexible for fine tuning. Some heading levels where used just to make easier for automatic ToC with one VSCode extra extension where not ideal ones. But raw HTML for this specific project is better for sure. So lovely.

[fititnt]

Version in production now:

Outline

• https://validator.w3.org/nu/?doc=https%3A%2F%2Ftags.etica.ai%2F&showsource=yes&showoutline=yes

Schema (on Google Rich Snippets tool)

• https://search.google.com/structured-data/testing-tool/u/0/?hl=pt-BR#url=https%3A%2F%2Ftags.etica.ai%2F