Organising C5 Projects

Permalink 2 users found helpful
I posted on another thread about how I have been organising my C5 projects, then concluded it was a useful enough topic to see what other developers are doing. It may help some newcomers to get started (and it may give me some ideas for my own workflow)

==================
I have been working with 3 or 4 installations for each project:

Development - play with ideas, make my mistakes, leave lots of unused versions.

Offline Stage and/or Online Stage - Install successful ideas, write content. No playing about because this will be moved or copied to the final site.

Final Site - what it says, no playing, no risks, just finished content copied or moved from the stage(s) when I am ready to go live.

At various points I copy the stage(s) back to the development, but I never copy development forward. When I am ready to go live, the online stage gets cleaned up and copied or moved forward to the live domain.

JohntheFish
 
codingpenguins replied on at Permalink Reply
I agree i with JohntheFish above way above (for the cleanest way), but in other situations where you have to customize things on that site or can not keep things as clean (no development/testing/production sites).

The way I do it (which I have yet to have complaints) is go through all pages/files and only keep the latest version. Then go to the CollectionVersions in the database and change the cvID to 1 and change the cvcomments to "Initial Version", check cvIsApproved, and verify cvAuthorUID, cvApproverUID is 1. This prevents them from looking at my past versions. (same idea for FileVersions)

I also delete all the rows in PageStatistics, the private messages/users tables (except for the admin - If I added Users to test), and the Logs table.

- I did this all from memory, so not 100%, but I think that is all I do. Only take 15-30 minutes at the most.