I want to publish bookmarks. Not so much individually, but more in collections, and tagged, to accompany blog posts, eg as bibliography.
- Data model: URL (etc), commentary (rich text), tags, timestamp(s), draft flag.
- Scalability (from a UX perspective, so probably a client side issue just as well).
- Import (and export?) from Firefox, Konqueror, Chromium.
- Search (full text, including URL)
Use WP’s blogroll, CPTs, or what?
- Blogroll (aka links) additions don’t show up in the loop, like custom post types (CPTs). And then there’s also a “link” post format? Anyway, a dedicated shortcode would give me flexibility.
- And the blogroll’s DB schema (table wp_links) seems more appropriate. Though I could replicate it as custom field(s). Serialized PHP objects versus SQL? I hate SQL (obsolete paradigm, as old as I am), prefer dynamic (duck) typing. But, a separate table/entity feels cleaner…
- Or Delicious?!
- Konqueror’s kept in ~/.kde/share/apps/konqueror/bookmarks.xml; simple enough structure; favicons in separate PNG files.
- Firefox’s maybe in an SQLite DB; addon bookmarksbackups converts them to JSON; includes description, but not favicons. Can manually save as HTML?
- Chromium’s are in ~/.config/chromium/Default/Bookmarks, in JSON; simple; no favicons.
- How to import each of these into WP?
- Separate from posts’ tagging?
- Hierarchical? Tagging, as in folksonomy (Web 2.0), is far superior to (strictly hierarchical, tree) categorizing, but, eg, how to distinguish between “WP › performance” and “JS › performance”? Do I want to? Yes.