Quellcode durchsuchen

Move Page content type to "Areas for Improvement", arrange by rough difficulty.

Brit Butler vor 11 Jahren
Ursprung
Commit
7620b7a87d
1 geänderte Dateien mit 19 neuen und 17 gelöschten Zeilen
  1. 19 17
      docs/hacking.md

+ 19 - 17
docs/hacking.md

@@ -92,13 +92,6 @@ grouping content by tags, publishing date, and reverse chronological
92 92
 order. Feeds exist to special case RSS and ATOM generation.
93 93
 Currently, there is only 1 content type: POST, for blog entries.
94 94
 
95
-I'm planning to add a content type PAGE, for static pages. It should
96
-be a pretty straightforward subclass of CONTENT with the necessary
97
-methods: `render`, `page-url` and `publish`. It could have a `url`
98
-slot with `page-url` as a reader to allow arbitrary layout on the site.
99
-The big question is how to handle templating and how indexes or other
100
-content should link to it.
101
-
102 95
 ### Templates and Theming
103 96
 
104 97
 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
177 170
 probably `pushnew` a plist onto the config key in their `enable` function.
178 171
 This has been implemented on the branch `user-defined-routing`.
179 172
 
173
+### New Content Type: Pages!
174
+
175
+Many users have requested a content type PAGE, for static pages. It
176
+should be a pretty straightforward subclass of CONTENT with the
177
+necessary methods: `render`, `page-url` and `publish`. It could have a
178
+`url` slot with `page-url` as a reader to allow arbitrary layout on
179
+the site.  The big question is how to handle templating and how
180
+indexes or other content should link to it.
181
+
182
+### New Content Type: Shouts!
183
+
184
+I've also toyed with the idea of a content type called a SHOUT, which
185
+would be used primarily to reference or embed other content, sort of a
186
+mix between a retweet and a del.icio.us bookmark. We encounter plenty
187
+of great things on the web. Most of mine winds up forgotten in browser
188
+tabs or stored on twitter's servers. It would be cool to see SHOUTs as
189
+a plugin, probably with a dedicated SHOUT-INDEX, and some sort of
190
+oEmbed/embed.ly/noembed support.
191
+
180 192
 ### Better Content Types
181 193
 
182 194
 Creating a new content type is both straightforward and doable as a
@@ -197,16 +209,6 @@ Unfortunately, this does not solve:
197 209
    Content Types it includes or the CONTENT which indexes it appears
198 210
    on is not yet clear.
199 211
 
200
-### New Content Type: Shouts!
201
-
202
-I've also toyed with the idea of a content type called a SHOUT, which
203
-would be used primarily to reference or embed other content, sort of a
204
-mix between a retweet and a del.icio.us bookmark. We encounter plenty
205
-of great things on the web. Most of mine winds up forgotten in browser
206
-tabs or stored on twitter's servers. It would be cool to see SHOUTs as
207
-a plugin, probably with a dedicated SHOUT-INDEX, and some sort of
208
-oEmbed/embed.ly/noembed support.
209
-
210 212
 ### Incremental Compilation
211 213
 
212 214
 Incremental compilation is doable, even straightforward if you ignore