What your describing sounds exactly like a "lightweight" (i.e. only the features you want) version of what's already out there. (At least now that you've ditched the "no file generation" requirement.)
Unless you have some requirements that are really important to the success of the project/documentation that existing solutions don't satisfy, I would strongly recommend against building your own tool. I think it'll be harder than you expect. J On Tue, Jun 23, 2009 at 4:17 PM, Aaron Boodman <a...@chromium.org> wrote: > > One important piece of feedback I got was that this system wouldn't > spider well. I've modified the proposal so that instead of generating > the final views at runtime, we generate them at check-in time using > something like Django: > > > http://sites.google.com/a/chromium.org/dev/developers/design-documents/extensions/doc-viewer-design-doc > > I don't think this is a very major blow to ease of use (and we can add > a presubmit hook to make sure people run the script), but it makes it > so that the docs are static files that are easy for search engines to > spider. It also has the advantage of allowing us to pick one of the > many mature templating languages available for Python. > > - a > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
