Hi everybody,
I''m planning to add full blog support to webgen, RSS/atom feed
generation already works. I want to take a modular approach to this
which means that you can either use all of the ''blog'' features
or only
some of them. For example, if you just like having tags and a listing of
all pages with a certain tag, you don''t need full blog support.
My plan for blog support:
* blog pages:
Nothing special here. Blog pages are just normal pages and created as
such. So you have to style them correctly if they should look like a
blog entry (author name, creation date, tags, ...).
* Automatic feed generation:
Already published in 0.5.3
/blog/blog.feed -> [/blog/blog.rss, /blog/blog.atom]
* Archive style names:
Already implemented but not published. Can be used to modify the output
path of a source path to contain the creation year/month/day.
/blog/content1.page -> /blog/2008/09/content1.html
* Tags support
Just specify the meta information tags which should be an array of tag
names.
* tag source handler:
This source handler uses files with the extension .tag and creates
a page for each tag that is found on specified pages/paths and
optionally a feed for a tag.
Should this handler optionally support nested tags, ie. something
like category trees:
- Computer
- Ruby
- webgen
- ramaze
- Python
- Live
- Picture
- Friends
Or is a separate source handler for this better? What do you think?
/blog/blog.tag -> [/blog/tag1.page, /blog/tag2.page, /blog/tag1.feed, ...]
* archive source handler:
Uses the specified pages/path and generates yearly, monthly or daily
archives. Default monthly.
/blog/blog.archive -> [/blog/2008/index.page, /blog/2008/09/index.page,
/blog/2008/09/10/index.page, ...]
* blog source handler
Automatically creates input files for the tag source handler, the feed
source handler and the archive source handler. This can be used to
specify everything related to a blog in one file and let webgen do the
rest.
/blog/blog.blog -> [/blog/blog.tag, /blog/blog.feed, /blog/blog.archive]
I think that this is everything that should be automatically be
generated for a blog. Are there any other files that need to be
generated for good blog support???
As for using the information provided by the tag/archive/blog handler:
I''m thinking about adding methods like
`blog(''unique-blog-name'')`,
`tags(''unique-tags-name`)`, ... to the context object to retrieve all
information about a blog, tags, ... The question is: what should be
provided by the returned objects? Any recommendations?
Also: should there be any webgen tags that help including blog/tags
content in a page? The only tag I can think of currently is tag-cloud
which generates a tag cloud for a unique-tags-name. Any others???
I would appreciate any input you have on this topic! Or think of it
like this: it''s now or never :P
Regarding a time line: If I find enough spare time (and you guys don''t
want too much extra features ;) I think I can ship blogging support at
the end of September.
-- Thomas
Thomas, My comments are inline below.> I''m planning to add full blog support to webgen, RSS/atom feed > generation already works. I want to take a modular approach to this > which means that you can either use all of the ''blog'' features or only > some of them. For example, if you just like having tags and a listing of > all pages with a certain tag, you don''t need full blog support.- I think the modular approach is a great idea, It allows you to keep Webgen flexible.> > My plan for blog support: > > * blog pages: > ? Nothing special here. Blog pages are just normal pages and created as > ? such. So you have to style them correctly if they should look like a > ? blog entry (author name, creation date, tags, ...).- Using the KISS rule is great one less complication when trying to use this new feature!> * Automatic feed generation: > ? Already published in 0.5.3 > > ? /blog/blog.feed -> [/blog/blog.rss, /blog/blog.atom]- I would like to play around with this, but haven''t had time because of school and work.> * Archive style names: > ? Already implemented but not published. Can be used to modify the output > ? path of a source path to contain the creation year/month/day. > > ? /blog/content1.page -> /blog/2008/09/content1.html- This a useful feature that could be used in some of my other projects!> * Tags support > ? Just specify the meta information tags which should be an array of tag > ? names.> * tag source handler: > ? This source handler uses files with the extension .tag and creates > ? a page for each tag that is found on specified pages/paths and > ? optionally a feed for a tag. > ? Should this handler optionally support nested tags, ie. something > ? like category trees: > ? ? - Computer > ? ? ? - Ruby > ? ? ? ? - webgen > ? ? ? ? - ramaze > ? ? ? - Python > ? ? - Live > ? ? ? - Picture > ? ? ? - Friends > ? Or is a separate source handler for this better? What do you think? > > ? /blog/blog.tag -> [/blog/tag1.page, /blog/tag2.page, /blog/tag1.feed, ...]- I think the nested tags would be a good idea because down the road someone may want something like that and the work has already been done. Another source handler may be the better route to go allowing Webgen to stay modular.> * archive source handler: > ? Uses the specified pages/path and generates yearly, monthly or daily > ? archives. Default monthly. > > ? /blog/blog.archive -> [/blog/2008/index.page, /blog/2008/09/index.page, > ? ? ? ? ? ? ? ? ? ? ? ? ?/blog/2008/09/10/index.page, ...]- I like the idea of an archive source handler, it would be cool to use the feature to archive pages of a website that gets updated allowing a user to easily access old content.> * blog source handler > ? Automatically creates input files for the tag source handler, the feed > ? source handler and the archive source handler. This can be used to > ? specify everything related to a blog in one file and let webgen do the > ? rest. > > ? /blog/blog.blog -> [/blog/blog.tag, /blog/blog.feed, /blog/blog.archive] > > I think that this is everything that should be automatically be > generated for a blog. Are there any other files that need to be > generated for good blog support??? >- I don''t know much about blogging, but it seems you have the direction figured out. It would be fun to test and play around with the blog feature.> As for using the information provided by the tag/archive/blog handler: > I''m thinking about adding methods like `blog(''unique-blog-name'')`, > `tags(''unique-tags-name`)`, ... to the context object to retrieve all > information about a blog, tags, ... The question is: what should be > provided by the returned objects? Any recommendations?- A results page listing the results and all the pages that have the content searched for.> Also: should there be any webgen tags that help including blog/tags > content in a page? The only tag I can think of currently is tag-cloud > which generates a tag cloud for a unique-tags-name. Any others???- I am not sure, I am still trying to learn and understand all the tags that Webgen currently uses. Every week I learn more about this software from this group and the questions / answers posted.> I would appreciate any input you have on this topic! Or think of it > like this: it''s now or never :P > > Regarding a time line: If I find enough spare time (and you guys don''t > want too much extra features ;) I think I can ship blogging support at > the end of September. > > -- Thomas > _______________________________________________ > webgen-users mailing list > webgen-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/webgen-users
FYI: yesterday i ported my small blogging system from 0.4.x to 0.5.4. It consists of the tags/extensions for "blog_index:" for index, "rss_blog" for feed, a helper archive script and a template file. The website has still a small "virtual" problem (bug reported) so it is not online. This forum does not allow attachments ... On 5 Sep., 18:04, Thomas Leitner <t_leit... at gmx.at> wrote:> Hi everybody, > > I''m planning to add full blog support to webgen, RSS/atom feed > generation already works. I want to take a modular approach to this > which means that you can either use all of the ''blog'' features or only > some of them. For example, if you just like having tags and a listing of > all pages with a certain tag, you don''t need full blog support. > > My plan for blog support: > > * blog pages: > ? Nothing special here. Blog pages are just normal pages and created as > ? such. So you have to style them correctly if they should look like a > ? blog entry (author name, creation date, tags, ...). > > * Automatic feed generation: > ? Already published in 0.5.3 > > ? /blog/blog.feed -> [/blog/blog.rss, /blog/blog.atom] > > * Archive style names: > ? Already implemented but not published. Can be used to modify the output > ? path of a source path to contain the creation year/month/day. > > ? /blog/content1.page -> /blog/2008/09/content1.html > > * Tags support > ? Just specify the meta information tags which should be an array of tag > ? names. > > * tag source handler: > ? This source handler uses files with the extension .tag and creates > ? a page for each tag that is found on specified pages/paths and > ? optionally a feed for a tag. > ? Should this handler optionally support nested tags, ie. something > ? like category trees: > ? ? - Computer > ? ? ? - Ruby > ? ? ? ? - webgen > ? ? ? ? - ramaze > ? ? ? - Python > ? ? - Live > ? ? ? - Picture > ? ? ? - Friends > ? Or is a separate source handler for this better? What do you think? > > ? /blog/blog.tag -> [/blog/tag1.page, /blog/tag2.page, /blog/tag1.feed, ...] > > * archive source handler: > ? Uses the specified pages/path and generates yearly, monthly or daily > ? archives. Default monthly. > > ? /blog/blog.archive -> [/blog/2008/index.page, /blog/2008/09/index.page, > ? ? ? ? ? ? ? ? ? ? ? ? ?/blog/2008/09/10/index.page, ...] > > * blog source handler > ? Automatically creates input files for the tag source handler, the feed > ? source handler and the archive source handler. This can be used to > ? specify everything related to a blog in one file and let webgen do the > ? rest. > > ? /blog/blog.blog -> [/blog/blog.tag, /blog/blog.feed, /blog/blog.archive] > > I think that this is everything that should be automatically be > generated for a blog. Are there any other files that need to be > generated for good blog support??? > > As for using the information provided by the tag/archive/blog handler: > I''m thinking about adding methods like `blog(''unique-blog-name'')`, > `tags(''unique-tags-name`)`, ... to the context object to retrieve all > information about a blog, tags, ... The question is: what should be > provided by the returned objects? Any recommendations? > > Also: should there be any webgen tags that help including blog/tags > content in a page? The only tag I can think of currently is tag-cloud > which generates a tag cloud for a unique-tags-name. Any others??? > > I would appreciate any input you have on this topic! Or think of it > like this: it''s now or never :P > > Regarding a time line: If I find enough spare time (and you guys don''t > want too much extra features ;) I think I can ship blogging support at > the end of September. > > -- Thomas > _______________________________________________ > webgen-users mailing list > webgen-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/webgen-users