I want to use the multi-site function to develop sites for client review from one installatin of wordpress on a development-only domain that I own. Once a client is satisfied with the site, I would have it transferred to the client’s domain.
My questions are:
· Is this a feasible and desirable method to develop sites?
· Are there additional apps or plugins necessary to make this work?
· Where can I find training or tutorials on how to make this work?
· I intend to use Elementor as the development platform for my sites.
· I already have WordPress installed on https://jdcdemo.com for this specific purpose.
· My knowledge of WordPress is adequate, I think, to do what I am proposing, but it can stand improvement.
If this is not the appropriate forum for these questions, please accept my apology and steer me to the correct site.
Thanks to those who know more than me,
Joe
[ad_2]
This is not the best use case for multisite. Multisite is best in situations, where you want the different WordPress websites to share some common functionality, that you would manage as the super-admin.
If these are all going to be bespoke unrelated websites, imho you are better off with separate WordPress installations on subdomains. So you can have website1.jdcdemo.com, website2.jdcdemo.com etc, each having its own WordPress installation.
to piggyback off this. Can you have [site1.com](https://site1.com) and [site1.com/blog](https://site1.com/blog) as a non-multisite? Or are subdirectories always multisite?
No need for multi site or plugins at all. It’s quite easy. You can configure this via the DNS settings on your domain management screen.
E.g. If your dev env. server is on IP [1.1.1.1](http://1.1.1.1), for [*jdcdemo.com*](http://jdcdemo.com) you can set an extra A record:
Type: A Record
Host: client_name, let’s say is acme
Value: [1.1.1.1](http://1.1.1.1)
TTL: I leave that set to automatic
That will result in: [*acme.jdcdemo.com*](http://acme.jdcdemo.com) and you can dev your site there
On your hosting you should set that domain as the primary address of that specific WordPress install where you will dev the website. You can also install SSL for that domain
But usually you do this for the staging environment.
Active development is usually easier on your local machine. Then staging is just used to show to the client the website, let them try it when necessary, get approval/feedback, etc.
You can configure your local environment to update the staging env. automatically with GitHub Actions, for example. So there’s no need to manually move files with SFTP
Development on your local machine is usually easier because you can access tools via NPM that usually can’t be used on your staging env. However, if this project right here is really simple, setting a local dev. environment could be overkill