Integrate Photologue into a sitemap.xml

[GoogleCodeExporter]

New feature.
The attached file is a sitemaps.py to add to Photologue. It's only a couple
of lines long, and makes it trivial to integrate Photologue into a
project's sitemap.xml.

Original issue reported on code.google.com by richardb...@gmail.com on 11 Oct 2008 at 7:52

Attachments:

• sitemaps.py

[GoogleCodeExporter]

This is a great idea but I wonder if it should be defined on a site-by-site 
basis. 
Does anyone else have any thoughts?

Original comment by justin.d...@gmail.com on 17 Oct 2008 at 5:18

• Changed state: DecisionNeeded
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Hi,
I'm not sure that I'm following you - are you suggesting that we use Django's 
sites
framework?

Original comment by richardb...@gmail.com on 29 Oct 2008 at 10:22

[GoogleCodeExporter]

Sorry I wasn't very clear. I'm just thinking this subject would make for a 
great 
tutorial/doc page rather than a included file. I may be alone in this thinking 
however.

Original comment by justin.d...@gmail.com on 29 Oct 2008 at 12:31

[GoogleCodeExporter]

Ok, I think that I understand better now.
You're suggesting not including sitemap.py - instead, we would have a tutorial
listing the code snippets to add to the project's urls.py in order to enable a
photologue sitemap?
That approach would work equally well. What I see as the advantages of each 
method:
- as a tutorial: less code in photologue.
- as a file: more obvious to someone who installs the app that it easily handles
sitemaps.
I don't have a strong preference - both solutions work equally well.

Original comment by richardb...@gmail.com on 30 Oct 2008 at 10:17

[GoogleCodeExporter]

Issue 4 on Github.

Original comment by richardb...@gmail.com on 12 Aug 2012 at 10:35

• Changed state: Duplicate