Changes between Initial Version and Version 1 of Ticket #33161, comment 49
- Timestamp:
- 06/30/2020 03:14:24 PM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #33161, comment 49
initial v1 9 9 No objection per se, but I'd like in the dev notes (and ideally in inline documentation IMO) some explanation of what each is intended to mean. 10 10 11 For example, in Jetpack, we have a "development mode" that is intended for localhost where a site would not be connecting to WordPress.com. The original use case is for theme developers to be able to activate some features of Jetpack that would usually require a connection with a fair mockup of it so they can work on front-end theming. (I realize this mode isn't perfect, so let's not go down the rabbit hole if Jetpack is actually doing all that I'm claiming it does!). Major parts of Jetpack will not work in this mode and isn't foreseen as a new going-into-production-eventually site. 11 For example, in Jetpack, we have a "development mode" that is intended for localhost where a site would not be connecting to WordPress.com. The original use case is for theme developers to be able to activate some features of Jetpack that would usually require a connection with a fair mockup of it so they can work on front-end theming. (I realize this mode isn't perfect, so let's not go down the rabbit hole if Jetpack is actually doing all that I'm claiming it does!). Major parts of Jetpack will not work in this mode and isn't foreseen as a new going-into-production-eventually site. [To note, Jetpack will likely deprecate and rename our "development" mode to be more precise as a "localhost mode".] 12 12 13 13 We have a "Staging Mode" which is meant for sites that may be a copy of a production database (which in our case includes the knowledge that a site is connected to WordPress.com), but isn't production — so don't do anything that would impact that. Don't send out new posts to Twitter, etc.