*Amateur Time 
*
I am wondering if there is a smart way to organize different versions of one’s website, when working with Kirby and how to handle these versions and the license.
So how I’m doing it at the moment is:
-
I start building a kirby project live on a server (with Atom and the FTP-Remote-Edit plugin), usually in a subfolder, like example.com/dev
-
At some point i clone the whole kirby folder and rename it (and make some changes to .htaccess, config, etc. accordingly) to create example.com/v1
-
To release version 1 I create an index.php or .htaccess that redirects from example.com to example.com/v1 on the highest folder level.
-
I then keep working on the example.com/dev version until I release a new clone under example.com/v2, replace the content folder, change the redirect, etc, etc
So at some point I have many autonomously coexisting, publicly available Kirby folders on my server like this:
example.com/dev
example.com/v1
example.com/v2
example.com/v3
…
On the upside this feels very neat, I can keep the old versions as backups, also this way I can easily compare them among each other.
But then again there must be a smarter way. Maybe with a shared content folder? And would all versions need an individual license?
How is this normally done? Do other people develop their website locally and only have the latest version online?
Are there some best practices? I don’t even know what to google 
For context: I’m talking about rather small websites with 1-2 developers and 1-2 editors using the panel.