Fixes for issues #93 #94 #95
I would propose s/blog/feed/ as it not always have to be a blog ...and maybe we should make the "..." postfix an option, too?
@tcurdt Good idea on feed, I'll make the change. About making an options of ..., I am not sure, all the Awestruct sites I have checked end up with ...... at the end of the <summarize> element.
Also, I am having some issues with my feed on Google Reader, I want that to settle down to be sure my change in #93 is not causing it.
Ah, the summarize function probably adds those "..." then. +1 to just remove them then.
Let me know how Google Reader likes the new feed.
issue #93 - add published element in atom feed
issue #94 - Remove ... as summarize already produce them
hey @tcurdt , I am reworking #95 to rename blog_url and blog_title to use the feed prefix. I realize that feed_url would be a very confusing name. I can think of:
I think 2. is good. Any other suggestion?
I put my vote in for 2 as well.
issue #95 - Make feed title and content url customizable in atom feed
It was hardcoded to the full website url and title
I have rebased my branch with a new version of these commits:
It's good to go
@emmanuelbernard good point about the naming. But don't you you think a common prefix would be clearer?
Definitely not site_ulr, site_title as you can have more than one feed per site.
We could use content_title instead of feed_title but I don't think that conveys the truth. It's not a title for the content, it's a title for the feed. And it's not a url to the feed but a url to the content used to generate the feed.
To me it's better as it is. What do others think?
Hm. Again true. I think feed_title is just the right name. Still not convinced about the content_url though. Anyway ... merging for now.