|
|
|
|
194
|
should be a pretty straightforward subclass of CONTENT with the
|
194
|
should be a pretty straightforward subclass of CONTENT with the
|
195
|
necessary methods: `render`, `page-url` and `publish`. It could have a
|
195
|
necessary methods: `render`, `page-url` and `publish`. It could have a
|
196
|
`url` slot with `page-url` as a reader to allow arbitrary layout on
|
196
|
`url` slot with `page-url` as a reader to allow arbitrary layout on
|
197
|
-the site. The big question is how to handle templating and how
|
|
|
198
|
-indexes or other content should link to it.
|
|
|
|
|
197
|
+the site. For now, we can be sloppy and reuse the post template and
|
|
|
198
|
+limit static-pages to being written in markdown. If we want to support
|
|
|
199
|
+other formats, consider moving the format slot from POST to CONTENT.
|
|
|
200
|
+This has been implemented on the branch `static-pages`.
|
199
|
|
201
|
|
200
|
### New Content Type: Shouts!
|
202
|
### New Content Type: Shouts!
|
201
|
|
203
|
|