It appears that WordPress is designed to have websites constructed and maintained online – in the live website. I see some posts here that indicate some people are doing such development offline – in Localhost. But the effort to move a website online – especially for updates – appears to be complex, somewhat manual, and not at all automated. In fact, it’s not clear of just the changes can be moved, or if the entire website would have to be reloaded. This seems complicated by visitor changes to the live website while updates are being created. And backups or version control of content – well I haven’t gone far on that yet.
So what works? Is it just best to make changes to the live website? What would be the best approach for doing development offline?
4 Answers
It totally depends on the types of changes being made. If you’re modifying a theme or a plugin, depending on what the changes are, you can likely build them locally or on a remote dev server, then push them to production with ease.
That works for a user or two, with more users you need version control – something like Git or SVN – to track and merge changes.
See this: https://stackoverflow.com/questions/9705849/how-to-set-up-a-stageing-enviorment-for-wordpress-wordpress-mu/10837071
I usually prefer to have a remote dev server because it’s easier to replicate the production environment, and it’s easier to access from multiple machines. The way I set it up is no slower than local development… possibly even faster.