384046 results for ""a""

  • I see it now with your daylists. But for my content, since it's a poem, the title and content are both important. And it looks like, at least the pin13 parser, picks up your content as name, but I'm manually setting it with p-name
    itskalvaxus at 2025-12-06 01:51
  • for typical h-entry consuming implementations, a p-name ought to be "enough" to provide a "good enough" UX
    [tantek] at 2025-12-06 01:47
  • correct aaronpk. however the absence of a content property MUST NOT pose a problem for consuming implementations
    [tantek] at 2025-12-06 01:43
  • i thought the "content" property could not be implied, so you'll never end up with a "content" property unless you explicitly have an e-content class
    aaronpk at 2025-12-06 01:35
  • thus <span class="e-content h-entry"> = e-content on ancestor object that has a value of an embedded h-entry itself
    [tantek] at 2025-12-06 01:29
  • e.g. <span class="p-author h-card"> = an author property on ancestor object that has a value of an embedded h-card
    [tantek] at 2025-12-06 01:28
  • Is this not valid MF2? `<article class="h-entry e-content">`. Do I need to move the .e-content to a lower div?
    itskalvaxus at 2025-12-06 01:26
  • or maybe that makes a year look "cooler" than a previous year by showing growth in the number of cities/timezones year over year?
    [tantek] at 2025-12-05 23:53
  • ok that's enough of a nudge to try to prototype using a previous year (to not disturb the current year)
    [tantek] at 2025-12-05 23:51
  • in general, time series displays, charts, nav etc. work well with a horizontal view of time the x-axis being the time axis. left is the past, right to the future
    [tantek] at 2025-12-05 23:49
Sort by:

Filter results by:

Tag

Query took 0.02s.


Search tips

Exclusion
+foo -bar
Logical OR
foo OR bar
Exact phrase
"foo bar"
Partial words
foo*
Particular fields only
title:foo
domain:example.org
nick:somebody
after:2016-11-23
before:2016-11-23
date:2016-11-23