[Radiant] Developing Radiant site

[Joe Van Dyk]

On Tue, Jul 15, 2008 at 9:07 PM, Chris Parrish
<chris.parrish-forummail at swankinnovations.com> wrote:
> Joe Van Dyk wrote:
>>
>> Hi,
>>
>> I'm new to Radiant, but not Rails.
>>
>> So, I'm seeing that stuff like the layout and CSS is entered through
>> forms and saved to the database, and aren't contained in version
>> controlled files.
>>
>> So, how does that work?  I mean, how do you deploy changes?  Just by
>> copy/pasting the updated snippets and css stuff to the live site and
>> enter it into the form?  How do you version control it?
>>
>> Seems a little weird to me, perhaps I'm missing something?

<snip>

>   * And finally there's version tracking.  Part of the problem here is
>     are you just handling drafts while another live "version" is
>     actively published, or are you trying to track every save that was
>     ever made.  The other issue is working it into Radiant's elegant
>     UI.  All the other approaches are more admin tools.  This one
>     would involve the user and versioning can really affect usability
>     and workflow.
>
> To my knowledge, there isn't anything existing to tackle the third item yet
> (though it's mentioned as being on the development timeline).  There'd be
> some happy campers if you want to roll out a first-class solution here (all
> the free beer and pizza you want at the big Radiant gatherings).
>
> Hope this helps (though I kind of wrote all this to document everything for
> me too).  And if I've missed anyone's great extensions, please chime in.

Well, here's what I'm doing:

I've got some non-technical users that need to add content.  They are
just going to be editing the text, creating new pages, using the
pages/behaviors/snippets that we set up for them.

We are going to be doing the work on the layouts, behaviors, snippets,
etc.  There will be some extensions written as well.

I don't necessarily have to version control the work we're doing
(would be nice though), but just curious about the deploying/updating
process.  Could do hourly backups of the database, that would probably
be good enough.

Would another CMS work better for us?

Thanks,
Joe