search

getnikola / nikola

A static website and blog generator
https://getnikola.com/
MIT License
2.62k stars 450 forks source link

A semantic theme – all-in or separate? #867

Closed da2x closed 11 years ago

da2x commented 11 years ago

I have some technical goodness to my theme. I want to contribute it back to Nikola. However, I am unsure where it should go.

Option one is to create a new semantic theme featuring h-entry (microformats2) and Schema.org/Blog structured microdata.

Option two would be to do, as requested by @Kwpolska on Twitter, to merge this into base base.

Option three is to take it out of the themes altogether. By introducing new semantic theme helpers, the theme users/hackers would get a parsable semantic blob of data returned instead of individual strings like title or dates.

h-entry is just a set of class names with semantic meanings. Schema.org/Blog uses the new HTML5 microdata attributes.

I fear this could be too technical and new users would hack their themes and partially remove the bits they do not understand. This is the primary reason why it maybe should not go into the base theme.

I have started tinkering on a microformats2 and microdata validator plugin. The idea is for it to halt if the output appears incomplete or unparseable.

Kwpolska commented 11 years ago

IMO, because it’s just class names, it makes no sense to create a new theme, just merge it into base and bootstrap{,3} and possibly themes in the Index.

da2x commented 11 years ago

Reducing the scope of this to microformats2. All consumers of microdata does such a bad job at it, that I am not going to push this on anyone just yet.

This will make it significantly easier to implement also. Will start working on it this weekend.

da2x commented 11 years ago

Issue #877 takes care of h-entry. I think I found a way to salvage microdata as well. I will will need more time to test if microdata consumers can parse my solution properly.

Leaving this issue open a bit longer.

da2x commented 11 years ago

Resolved by fcce3c6. Not an ideal solution (should have been WebPage:Blog:BlogPosting, but microdata consumers are dumb. Using something that will work with consuming services today (G+, Kindle, Bing).

samatjain commented 11 years ago

Isn't HTML5 microdata dead?

See Did You Just Hear That? Microdata Specification Just Died | The Search Agents, and The Downward Spiral of Microdata | The Beautiful, Tormented Machine.

da2x commented 11 years ago

@samatjain, I am aware of that. Personally, I prefer microformats2. But seeing how Google+ still prefers microdata, we should leave it in.