From 7620b7a87df3cb25dc2e39d5ce832138b715c25f Mon Sep 17 00:00:00 2001 From: Brit Butler Date: Wed, 16 Apr 2014 11:29:16 -0400 Subject: [PATCH] Move Page content type to "Areas for Improvement", arrange by rough difficulty. --- docs/hacking.md | 36 +++++++++++++++++++----------------- 1 file changed, 19 insertions(+), 17 deletions(-) diff --git a/docs/hacking.md b/docs/hacking.md index a0f7869..c9c6d3b 100644 --- a/docs/hacking.md +++ b/docs/hacking.md @@ -92,13 +92,6 @@ grouping content by tags, publishing date, and reverse chronological order. Feeds exist to special case RSS and ATOM generation. Currently, there is only 1 content type: POST, for blog entries. -I'm planning to add a content type PAGE, for static pages. It should -be a pretty straightforward subclass of CONTENT with the necessary -methods: `render`, `page-url` and `publish`. It could have a `url` -slot with `page-url` as a reader to allow arbitrary layout on the site. -The big question is how to handle templating and how indexes or other -content should link to it. - ### Templates and Theming User configs are allowed to specify a theme, otherwise the default is @@ -177,6 +170,25 @@ localizing all the site routing in one place. New Content Types would probably `pushnew` a plist onto the config key in their `enable` function. This has been implemented on the branch `user-defined-routing`. +### New Content Type: Pages! + +Many users have requested a content type PAGE, for static pages. It +should be a pretty straightforward subclass of CONTENT with the +necessary methods: `render`, `page-url` and `publish`. It could have a +`url` slot with `page-url` as a reader to allow arbitrary layout on +the site. The big question is how to handle templating and how +indexes or other content should link to it. + +### New Content Type: Shouts! + +I've also toyed with the idea of a content type called a SHOUT, which +would be used primarily to reference or embed other content, sort of a +mix between a retweet and a del.icio.us bookmark. We encounter plenty +of great things on the web. Most of mine winds up forgotten in browser +tabs or stored on twitter's servers. It would be cool to see SHOUTs as +a plugin, probably with a dedicated SHOUT-INDEX, and some sort of +oEmbed/embed.ly/noembed support. + ### Better Content Types Creating a new content type is both straightforward and doable as a @@ -197,16 +209,6 @@ Unfortunately, this does not solve: Content Types it includes or the CONTENT which indexes it appears on is not yet clear. -### New Content Type: Shouts! - -I've also toyed with the idea of a content type called a SHOUT, which -would be used primarily to reference or embed other content, sort of a -mix between a retweet and a del.icio.us bookmark. We encounter plenty -of great things on the web. Most of mine winds up forgotten in browser -tabs or stored on twitter's servers. It would be cool to see SHOUTs as -a plugin, probably with a dedicated SHOUT-INDEX, and some sort of -oEmbed/embed.ly/noembed support. - ### Incremental Compilation Incremental compilation is doable, even straightforward if you ignore