...
This is the first project stage. It is primarily a label rather than a deployment target, but will be notable for having an associated announcement. The announcement post will explain this plan and how we intended to roll out each stage and the associated deployment steps.
At the time of writing creation for this document, almost all the requirements here are were already met. So, this stage will be is primarily about organizing, cleaning things up and getting them , and finishing up ongoing work into a release-ready state.
...
- Usable local deployment
- Usable dev deployment
- Support for users as a concept
- Support for sites, categories, and pages as concepts
- UI to view and edit user profile data
- UI to view and edit pages (e.g. adding revisions)
Stage 1 (
...
Foundations)
This project stage is marked by having a more complete set of actions available on users and pages, but which is overall still very non-comprehensive. This will also be the start of basic settings panels, which are expected to be in flux until designs and requirements stabilize. And, the foundations of solid international internationalization support should be ensured.
...
- All UI available so far is properly localized (i.e. no UNTRANSLATED)
- All infrastructure is available through IPv6
- Platform info page
- Page parent / child UI
- Displays page breadcrumbs
- Able to see page’s children
- Page theme exposure
- Support for page locks
- UI for creating or removing page locks
- UI for displaying current and historical locks
- User sessions
- Users are able to log in and log out
- Session information is passed and processed in Framerail and DEEPWELL
- Site actions require session data and perform authentication
- User creation UI
- Temporary support for passcode to limit user creation
- Basic platform settings UI
- Able to set free creation or requiring a passcode
- Basic site settings UI
- Able to set a site’s slug, name, and header information
- Able to set a site’s default home page slug
- Basic user settings UI
- Able to set a user’s preferred language(s)
- Able to modify a user’s email and password
...
- Only developers may create users on the dev deploy
Stage 2 (Early
...
)
This project stage is marked by having a more complete basic feature set. Most core operations on Wikidot are supported, and the project has a sufficient base to enable future changes to be made. This will be a longer stage than the Pre-AlphaStage 1, and marks the transition to larger stages with periodic intermediate releases.
...
Stage 5 (Migration Alpha)
Unlike “alpha” and “beta”, the word “gamma” is not often used in release terminology. Here it will refer to At this point, the platform should be stable and able to host general functions. So starting here, the effort will be on beginning the migration period for the new platform, that . That is, when Wikidot sites start moving over for real to use Wikijump as their new permanent home. It is expected that this will come with a number of operational and logistical difficulties, so it will start with smaller sites and those with fewer requirements. The stage will be marked with dialogue and work with these early platforms to ensure their workflows and needs are accounted for.
...