Steven Garrity
unread,Apr 9, 2013, 10:32:33 AM4/9/13You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Dan Poirier, dev-moz...@lists.mozilla.org
It seems like support for l10n would have to be a hard requirement for
this. Some type of review process would be ideal as well.
Worth investigating though.
Steven
On 04/02/2013 02:00 PM, Dan Poirier wrote:
> I was browsing some bugs and saw some discussion about how just changing
> some text on the web site requires a full branch/edit/pull request/code
> review/test/deploy cycle, which seems like overkill in many cases. The
> solution people seem to be using is to move entire pages of content to the
> wiki.
>
> I think Bedrock could benefit from a light CMS feature, where people with
> the right privileges could edit some sections of text on existing pages
> without requiring code changes. That would let Mozilla retain more control
> of those pages than a wiki would have, while bypassing the laborious code
> update process.
>
> This would only let authorized people edit page sections that have been
> marked as editable in their templates. Editors couldn't change anything
> else on the page, create new pages, delete pages, or anything else. That
> level of change would still require a code change.
>
> There are a number of Django packages that let you do this kind of thing.
>
> Caktus has developed one that I think is pretty good, django-scribbler,
> thought it might be a bit too light-weight for our use case.
>
> django-scribbler gives real-time preview of what the page looks like as
> it's edited, and even autocompletion of HTML markup and within template
> tags, so I think it's pretty friendly to people who might lack confidence
> when editing HTML, though it's not for people who don't know anything at
> all about HTML.
>
> On the other hand, there's no review process or other workflow, and no
> history kept. There's also no support for translation.
>
> If this sounds worth pursuing, we might work out just what features we'd
> need to have, and could then look for a package that has those features, or
> add them to an existing package, maybe even django-scribbler :-)
>