The old way of renaming the script while editing it works, but is cumbersome. Better to have a -dev directory, check out there, maybe even a branch, commit as work progresses, and merge or at least pull to the real site when done.
The blue background is a good reminder, keep that for the -dev
The -dev could have its own data files, copied over when starting to work on a feature, so as not to pollute real data when working
Would be nice if the -dev version had a warning on the top of every page that it is the -dev version, maybe branch name, and timestamp of the script. Maybe also a warning if the production script is newer than the -dev
The old way of renaming the script while editing it works, but is cumbersome. Better to have a -dev directory, check out there, maybe even a branch, commit as work progresses, and merge or at least pull to the real site when done.
The blue background is a good reminder, keep that for the -dev
The -dev could have its own data files, copied over when starting to work on a feature, so as not to pollute real data when working
Would be nice if the -dev version had a warning on the top of every page that it is the -dev version, maybe branch name, and timestamp of the script. Maybe also a warning if the production script is newer than the -dev