Roadmap for Phundament for Yii1

[motin]

The last major updates to Phundament for Yii1 were made in November 2013. Since then, it seems Phundament development has focused entirely on Phundament for Yii2.

Unfortunately, taking the plunge to Yii2 is not an alternative at this moment and we wish to know more about the plans for the development of Phundament for Yii1.

Here is a retrospective of our usage of Phundament:

What do we actively use in Phundament?

• Composer
• Uploading files using P3 Media & jQuery File Upload
• Codeception-based testing (unit, acceptance, functional)
• gii-template-collection to generate our data model of 25+ content types, including file based types such as TextDoc, Video with subtitles

What do we not use in Phundament?

• The translation UI / i18n extensions (translatable & yii-translate) - not flexible enough to accomodate our i18n requirements and lacks translator-friendly UIs
• P3 Pages - the UI for creating widgets was too abstract and hard to understand
• P3 Widgets - the UI for creating widgets was too abstract and hard to understand
• Phundament's approach with environment-specific configuration - instead we use our own method of setting environment-specific configuration

What were we missing in a CMS based on pristine Phundament that we have had to implement ourselves?

• User-contributed content translation into 100+ languages (crowdsourced translation)
• Workflow-based editing / quality assurance workflows
• Progress tracking (items can be X % ready for publishing, or Y % translated into language Z etc)
• Content versioning
• Graph-database-style relations
• Centralized configuration of behaviors and code generation based on project metadata
• Re-usable logic by using traits, and not entirely basing shared features on code generation
• Code-based programming of the RBAC configuration to allow for complex authorization logic
• A REST API (using Wrest)
• A higher quality user management extension (yii-user needed a serious revamp…)
• Generation of frontend vs backend views separately
• Generation of edit-in-place-based administration of related content
• Yiistrap and Bootstrap 3 (in progress)

All of this can potentially be worked back into Phundament, but only with major changes to the architecture and selection of extensions etc. One thing is for certain, we need a boilerplate that is in phase with the requirements mentioned above, and without the extensions that we don’t use and only add overhead. For a foreseeable future, this will be based on Yii1.