384712 results for ""a""

  • I'm working on a months-long project to produce an icalendar feed, and the ical module is pretty restrictive about field names. I'm already a bit stuck. So I'm just spitballing at the microformats water cooler to see if I can avoid any future pain. ;-)
    btrem at 2025-12-19 22:23
  • i sync a todo list on my email host's calDAV and i'm pretty the tasks are just weird events there
    ulhar4409 at 2025-12-19 22:22
  • i'd focus on the design for humans. if, along the way, i found a reason to make it machine-readable, for a specific consuming case, circle back around.
    [schmarty] at 2025-12-19 22:21
  • without a consumer in mind, my usual advice is to not worry about microformats. ๐Ÿ˜„
    [schmarty] at 2025-12-19 22:20
  • part of me wants to ask if there's a particular reason you want it microformatted, since that is probably relevant to how it can be consumed and why to consume it
    ulhar4409 at 2025-12-19 22:19
  • So I'm not trying to establish the `task` mf. I'm just thinking about how I might create content types that would lend themselves to future (a)comprehension, and perhaps (b) extension.
    btrem at 2025-12-19 22:19
  • btrem: i think typically the advice when a new microformat is proposed (or in this case, unfinished) is to think first about the consuming case. what tool or service will be parsing these, and for what user purpose?
    [schmarty] at 2025-12-19 22:16
  • I'm asking because I am trying to create todo/reminder content type in a Drupal site. And trying to come up with field names that would match existing practice, so the next person who comes along will have some idea of what's what.
    btrem at 2025-12-19 22:15
  • sounds appropriate for a `task` ๐Ÿ˜‚
    [schmarty] at 2025-12-19 22:15
  • There's a proposed `task` micoformat, but it looks like it was forgotten/abandoned. Is that correct?
    btrem at 2025-12-19 22:14
Sort by:

Filter results by:

Tag

Query took 0.03s.


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