Indicate a site is not production

[gwendolyngoetz]

We need to provide a way to better indicate to users if a deployment of CiviForm is production or not production.

We can split this into separate issues later, I'm just throwing out some random ideas.

The official government website banner

There have been past discussions before about when to show the banner. I suggest we make the following changes:

• Only show the banner on .gov websites
• Only show the banner on the production version of the website
• On non-.gov / non-production websites:
  • Show an expanded banner that explains this is not prod
  • Include an link to the production site if one is configured
  • Make it sticky so it follow when you scroll
  • Include appropriate translations and accessibility

Basically, it should be annoying. Here's an example.

Allow setting a time to make a program change program visibility

On the program edit page we allow setting the visibility of a program. An option to make it disabled is currently being worked on. Allow the date and time to be set along with what to change the visibility to. You could then set a date when you want a program inaccessible, but it would also allow for when you want any visibility change to go live. That means a program would be set to go live at 2 am without someone have to be awake.

Show a modal when attempting to apply

Not my favorite one, but adding it out there one might get annoying. We'd need to be able to have this disabled in both development and production for automated testing purposes unless we retrofit all tests.

Expire TI access

When adding someone as a TI an (optional?) end date that can be set which will remove access as a TI when that date is reached. This will help prevent a TI from creating applications in the wrong place.

Extra publish screen for first time published programs

When publishing a program for the first time we could include a message to the person publishing with recommendations of things to do if they have the same program in a test environment. Such as removing TI access in test, disabling a program in test, etc.

[avaleske]

Could we also put a basic password prompt before accessing the site? (Maybe at the AWS level, not even part of civiform)

[elisekalstad]

To consider as a good first issue.

[elisekalstad]

@avaleske -- That's a good idea, perhaps for a more advanced solution. There's benefit right now to having test applications easy to access for sharing testing responsibilities across staff. For a first step, just slathering "TEST SITE" in really obvious ways is (hopefully) effective.

[gwendolyngoetz]

With the addition of some new programs in production I am finding this to be a growing issue.

I am adding the banner in the first example. It's fully opt in. It won't show on prod and you must enabled it from the settings page. Optionally if they supply a new setting that has a url to the prod server a link to that site will be shown. See #7705.

It may not be perfect, but further refinement can come later.

FYI @sijiayam, @isabelcshaw, @shreyachatterjee00