Timeline for How do I add version control to my workflow?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2020 at 8:21 | history | edited | CommunityBot |
Commonmark migration
|
|
| Aug 27, 2012 at 17:43 | vote | accept | cfree | ||
| Feb 9, 2012 at 23:09 | comment | added | Wyck |
I don't know of a term, but many modern frameworks have a better abstraction layer when it comes to storing content in the database or have a "migration" type of API, wordpress is a bit of a can of worms in that regard and is also a reason why is does not support PHP Data Objects.
|
|
| Feb 9, 2012 at 21:34 | comment | added | cfree | @Wyck Alright, thank you. Is there a term for this kind of wonky development process? | |
| Feb 9, 2012 at 19:34 | comment | added | Wyck | There is not yet, is it really a thorn in the side of WordPress but not specifically a WordPress issue as many CMS's have this problem, you can read about it here wordpress.stackexchange.com/questions/119/… more in depth, some scripts do exist out there but most of them are in house because they are specific to a certain environment. | |
| Feb 9, 2012 at 19:11 | comment | added | cfree | @EAMann I do it more often than I care to (Find/Replace...). I really just wanted to see if there was a better way (industry standard) of building websites using Wordpress as a CMS, which increasingly seems like it's more trouble than its worth. | |
| Feb 9, 2012 at 19:01 | comment | added | EAMann | It's not usually a matter of syncing database changes. What I meant to say is that you take a dump of your production database and replace your local development database with it. True, you can automate it with a script ... but you likely won't be doing it very often. | |
| Feb 9, 2012 at 18:59 | comment | added | cfree | @Wyck Rather than dropping content alongside the theming, it makes sense to separate the two processes. I like the idea of a dev area for theming and a staging area for content dropping independent of each other. The only issue I see is that clients like to see both the theme and the content (the site in its entirety; static pages) prior to launching it live. | |
| Feb 9, 2012 at 18:41 | comment | added | cfree | @EAMann Great response, thank you! The only thing I would add to the workflow you described would be to write code, commit changes, push to development site, get comments back from client, ... I hadn't considered two separate workflows because regularly we will have to change the content ourselves for the clients. Occasionally we'll have to put HTML in the content to accommodate for special requests within the content (special styles, etc). Sometimes they require client approval before going live, which is why the databases would need to sync. Are there best practices for this kind of setup? | |
| Feb 9, 2012 at 18:40 | comment | added | Wyck | You can't really sync the databases easily unless you have a special script that manages how the content data is stored in the database. That is why you seperate code from content in your workflow, the alternative is to use a staging server or try and use one of the db syncing scripts or write your own. | |
| Feb 9, 2012 at 17:57 | history | answered | EAMann | CC BY-SA 3.0 |