Hello; hope all's good.
I looked back across our docs, and I can see much of the language is unchanged from the original,
produced around six years ago. I'm sure my speaking and manner of expression has changed much since,
and so should the composition of our code's guides.
I am going through and re-describing our code, as a means of reminding my preoccupied brain.
Once done on our docs / guides, I am hoping I can begin proposing an agenda of changes to be included in 0.19.0 and 0.20.0;
I am hoping these couple releases can be used as a gauge of 1.0-readiness,
and in some places break up old logic so more concise phrasings can be used.
Alongside a 1.0 (or any planned upcoming) release, I'd like to begin discussing a possible change of this library's name.
"Administrate" is nonsense based on the phrase "Administration", and has been a solid choice for many years.
Regardless, there is a chance to more clearly describe our engine.
I am hoping a change in name can spur some more clear direction in deciding on our engine's use cases.
In such direction, I booked the rubygems enroll and enrolled as possible options.
These names recommend an impression of a leader of a group or class, checking names and addresses on a clipboard.
I imagine a similar scene upon seeing any one of our dashboards, laid up in precise lines summarizing a user's records.
The purpose of a user's dashboard code is the "enrolling" of models, so our engine can handle displays and actions.