Update project page in preparation for 1.0.0 stable release

Created on 22 February 2023, over 1 year ago
Updated 24 February 2023, over 1 year ago

Problem/Motivation

The project page has a few things that are pretty outdated or no longer relevant that should be updated for the upcoming 1.0.0 stable release.

Steps to reproduce

πŸ‘€

Proposed resolution

Config Enforce ensures that select configuration cannot be changed in production environments.

Change this and other instances of "select" to something less ambiguous; select could be mistaken as referring to <select> elements which is not completely out of the realm of possibility given that this module deals heavily with forms.

NOTE: If you are upgrading from a version of this module prior to version 1.0.0-beta13, please read the 1.0.0-beta13 Release Notes β†’ for details on the proper upgrade process.

Is this worth keeping? Looks like the linked release was over two years ago, and given the nearly non-existent install base of the module right now, it likely won't be relevant to anyone anymore. At the very least, we should move it to a footnote or something.

This project is in active development, and an ALPHA release if forthcoming. Contributions of all sort are welcome, from documentation and reporting bugs through code and security reviews, unit tests, etc.

Let's remove the mention of "ALPHA release" since that's even more out of date.

Remaining tasks

Make the above changes.

User interface changes

None.

API changes

None.

Data model changes

Nope.

πŸ“Œ Task
Status

Fixed

Version

1.0

Component

Documentation

Created by

πŸ‡¨πŸ‡¦Canada Ambient.Impact Toronto

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Ambient.Impact
  • πŸ‡¨πŸ‡¦Canada ergonlogic MontrΓ©al, QuΓ©bec πŸ‡¨πŸ‡¦

    Change this and other instances of "select" to something less ambiguous; select could be mistaken as referring to
    elements which is not completely out of the realm of possibility given that this module deals heavily with forms.

    Maybe "managed":

    Config Enforce ensures that managed configuration cannot be changed in production environments.

    ... or "specified":

    Config Enforce ensures that specified configuration cannot be changed in production environments.

    I think I prefer "managed".

    +1 to all the rest.

  • πŸ‡¨πŸ‡¦Canada Ambient.Impact Toronto

    I'm normally pretty good at naming stuff but I'm having trouble deciding on one or another because I can see pros and cons to both, and the thesaurus isn't yielding anything useful. I think I like "specified" because it speaks about the action the user in charge of enforced config does to make said config enforced, while "managed" is a bit more vague about what's happening. I could very well be overthinking this. πŸ˜‚

  • Issue was unassigned.
  • Status changed to Needs review over 1 year ago
  • πŸ‡¨πŸ‡¦Canada Ambient.Impact Toronto

    Edits have been made, along with a few more not listed above. Everything is in the revision history for the page.

  • Status changed to Fixed over 1 year ago
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.69.0 2024