Alpha to beta release plan

Problem/Motivation

Need to outline a project plan going from an alpha release to a beta release on the 7.x-2.x branch. Thorough testing is still needed in case there are unknown bugs.

The API is not complete and currently considered unstable. Documentation is also incomplete and will need added and/or revised. Not suitable for production sites. Target audience is developers who wants to participate in testing, debugging and development of the project.

Getting to beta provides a much more stable release and will allow for testing on production sites for those who are comfortable enough to contribute back to the project.

Proposed resolution

The API and documentation needs to be completed and follow Drupal coding and documentation standards. We also need to provide theme implementations of all UIkit components for the user interface so sub-themes have more control over HTML output with less code.

The base theme needs to utilize these theme implementations as well, as many components are currently implementing core components.

I will be committing to the 7.x-2.x-dev branch heavily over the next few months. There will be many changes to the API, so use of this theme on production sites is highly discouraged. I will link back to this plan on any issues regarding changes in the API that "breaks" users' sites. As much as I would love to get a stable release out there soon, I also want to make sure the first stable release is done right.

Remaining tasks

#2788889: How are non-core js/css components loaded?
#2796059: Create Documentation
#2859919: Update to v2.27.2 of library
#2859925: Adding component assets
#2860806: Port theme to Drupal 8

User interface changes

#2859466-4: Off-canvas menu not expanding
Use the UIkit Components module to enable navbar dropdown support mentioned in above issue.

API changes

#2854101-6: Support "Show as expanded" in uk-navbar
#2859925-2: Adding component assets

Original report by Richard Buchanan