The problem with this question and finding the answer is that there really isn’t an easy way/automated way to convert content from webflow to a CMS. But understanding what you’re doing can help.
Webflow creates extremely easy to read semantic code. Any CMS you use whether it’s Wordpress, CraftCMS or Processwire will require this type of code. So Webflow is doing the first step automatically. So when you export your code and begin assembling the CMS of choice it’s very easy to connect the custom fields to the code created.
You’re asking about after doing that, if the client needs items changed or pages customized or the design updated what do you do and are there any tips?
Well, my question back would be in any scenario whether or not Webflow was used to enforce / help the design how would you do this?
The design changes, you get comps or changes from client, you update the design & pages and add those changes to the CMS. Whether you’re making those changes in Webflow or directly in the css files of the CMS’s theme, it’s essentially the same thing.
But there are tools you can use to make it easier. The ones I use are:
- GitHub / bitbucket & Sourcetree - to keep track of changes, collab with other Dev’s on a project, and be able to revert
Kaleidoscope - for comparing the new and old css or js files
Buddy.app - to automate pushing to live server & compiling
Hopefully this helps. I understand trying to find something to automate this, but a lot of time those automation tools put you in a box that isn’t really necessary to begin with and creates a bloated theme with classes you never needed to begin with. And besides that, you don’t really learn the CMS and how it works to solve problems and make informed decisions down the line for other clients.
@webdev really looking forward to testing out processwire looks radddddd