I was going to overly format this, but this is a list of the kind of things we are thinking about for using Plone. Following this, Paul is going to send out a link to some more specific questions/use cases. I'm comfortable with proceeding and growing as we go, including our taxonomy stuff, but I do want to do some pre-thinking so we can avoid totally st00pid stuff. <BobJensen> Plone addons needed? <quaid> * A workflow with a queue and roles for writer, editor, publisher ... so a writer can submit to the queue from $SOURCE, then it is all WUI after that. <megacoder> WUI? <quaid> * A way to make $SOURCE == Wiki output, either XML -> toolchain -> XHTML -> Plone <quaid> web user interface <BobJensen> existing and undeveloped <quaid> * A way to make $SOURCE == XML in CVS -> toolchain -> XHTML -> Plone <quaid> i.e. <quaid> 'make publish <quaid> or <quaid> 'make publish-web' <quaid> or something <megacoder> Yeah, "make publish-plone", but don't quote me within reach... <-- aalamS has quit (Read error: 104 (Connection reset by peer)) <quaid> * A make publish-web, could it just put things in the beginning of the Plone queue and that is good enough? <stickster> quaid: +1 <BobJensen> +1 <stickster> I think that would be where we would want it to stop, for review, right? <quaid> right <BobJensen> Yup I agree <quaid> so, not even an editor can inject from CVS -> Web live without the workflow in the way <quaid> what else? <quaid> think of use cases <nman64> Once the HTML is built, cadaver can be used with expect to script uploading the pages to Plone. <quaid> let the tools people (who may be some of us) worry about implementation after we define the uses. <quaid> heh <BobJensen> LOL <quaid> nman64: not to squelch ideation on that front, too, just wanted to involve the non-Ploney's :) <Eitch> +1 * BobJensen wonders what team got a GOAL!!! for Eitch's +1 <Eitch> almost! <quaid> ok, here is another one ... <Eitch> Brazil is kicking ass :) <quaid> * Some artistes and designers to help us make our CSS nice <Eitch> what CSS? <quaid> the Plone CSS? <quaid> fedora.css ? <quaid> both? <BobJensen> quaid: I think this is going to be very important for both <Eitch> both <quaid> I mean, we are going to be showing off our docs through this interface, but it will use a diff. CSS than the standard 'make html-nochunks', which is made for stand-alone, right? <Eitch> but fedora.css is really fine <quaid> yep, both <megacoder> quaid, CVS can assign a "state" (using the "-s <state>" switch); we could use that to key the plone update <quaid> sure, but why not review them both, or somesuch <BobJensen> quaid: +1 <Eitch> well, maybe changing some colors to blue <stickster> Eitch: We have that in our CSS methinks <quaid> well, they ain't broke, but we can review :) <stickster> I did some color redesign last year, IIRC... but it's not visible on the f.r.c website <quaid> nope <stickster> Always open to something better <Eitch> stickster: humm <quaid> a general one ... <quaid> * UI designer help for the www.fp.o <stickster> I would like to see some more dfong-style theming throughout, especially title pages and admonition boxes <quaid> tired of getting beat up on that one, too :) <Eitch> stickster: example: http://www.devin.com.br/eitch/fedora/yum-software-management-pt_BR/ <BobJensen> the front page will come from plone eventually am I correct nman64 ? -- Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 ////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Attachment:
signature.asc
Description: This is a digitally signed message part
