[clean1] restructure tiddler markup

[FND]

[this is a bit sweeping, but hard to split into separate issues]

the core of the friendly tiddler representation currently looks like this:

• article
  • header
  • h1
    • span#title
  • section
  • div.meta
    • p [modifier]
    • p [modified]
    • ul.tags
    • li.tag {n}
      • a [/search?q=...]
  • div.tiddlertext

Here are my thoughts:

• [ ] IDs should generally be avoided (e.g. aggregating multiple articles on one page would result in invalid IDs)
• [ ] that header seems unnecessary, as it only contains a single h1 (cf. http://html5doctor.com/avoiding-common-html5-mistakes/#header-hgroup)
• [ ] div.tiddlertext should probably be something else - perhaps http://html5doctor.com/designing-a-blog-with-html5/ (or a more recent variant thereof?) could provide some pointers
• [ ] div.meta should probably be a footer (despite the name)
• [ ] the "blog" link above might also provide some pointers on how best to structure the metadata within .meta
• [ ] ul.tags and li.tag are redundant - IMO ul.tags li should suffice
• [ ] that section should wrap only the tiddler body - this should avoid outline confusion if there are any H1s in that body, and would also simplify the hierarchy in general
• [ ] custom fields should also be included somewhere

[colmjude]

IDs are a tricky one. On the whole I like to avoid them but I can see why cdent likes the title id in this case.

Agree that in this setup the header is unnecessary. An argument could be made (particularly after mentioning the html5doctor) that the header is useful if you include the author/modifier and date/modified in it.

div.tiddlertext is another tricky one. I'd be reluctant to put it in anything else just for the sake of not using a div but maybe a section would be ok. I don't think removing it and having the tiddler.text output unwrapped would be a sensible option either given what could be outputted.

Hmmmm not sure about it being a footer but I understand the point being made.

I'd be tempted with something like:

• article
  • h1.tiddlertitle
  • span
  • div.meta
  • p [modifier]
  • p [modified]
  • ul.tags
    • li {n}
    • a [/search?q=...]
  • section.tiddlertext

[FND]

• I like the idea of moving metadata (author, timestamp, tags) into the header - that would render div.meta obsolete and thus circumvent the footer awkwardness
• the reason section is necessary is because it establishes an independent outline context
• tiddlertitle seems a bit awkward - see below for my preferred alternative
• what I hadn't mentioned above (now amended): I don't like dropping custom fields entirely

So I'd suggest this:

• article.tiddler
  • header
  • h1.title
    • a (optional)
  • metadata: author & timestamp (still not sure about the state of the art there)
  • ul.tags
    • li {n}
    • a [/search?q=...]
  • section containing tiddler body
  • footer (possibly display: none; by default)
  • dl.fields
    • dt + dd {n}
• footer ("Brought to you by TiddlySpace.")

[colmjude]

I'm liking this more now.

I would definitely have a .metadata wrap for the author and timestamp. As you say not sure on the best element for this but can be tweaked.

Agree with the classes for article and h1

This structure does open up the option for a footer with the fields in but there is a discussion to be had able whether this is something we want on the friendly tiddler representation. So I propose we make the changes we've discussed minus the footer which we can continue discussing.

I'll make these changes now.

[colmjude]

This has been merged now so closing.