@@ -119,24 +118,10 @@ This node is optional. If it is not defined, the block or page will be applied t
will also be applied to stores, which will be created in the future after re-running `setup:upgrade` command.
You can also use the 'wildcard' `*` in order to define that the content should be applied to all stores.
## Planed features / Road map
| Status | Feature/Change | Version |
|---|---|---|
| planned | Refactoring: Needs to find a pretty solution in order avoid some duplicate code... | 1.1.x |
| planned | CLI command to apply dedicated configured content entries to database | 1.2.x |
| planned | Integration tests | 1.2.x |
| idea | Add a button to page or block edit page in Magento backend, if there is content defined for this page in code. (Like: "Use default content") | ? |
| idea | Persist version hash every time the content is applied to database and track whether is was changes by editor. (Auto `maintained` mode) | ? |
Further ideas are welcome :)
## Major changes
| Feature/Change | Version |
|---|---|
| Configuration for pages | 0.1.0 |
| Configuration for blocks | 0.1.0 |
| Recurring setup installer for pages | 0.1.0 |
| Recurring setup installer for blocks | 0.1.0 |
| Notification in Magento backend (admin), for editors - if the content entry is maintained by code | 1.0.0 |
| Introduce `key` attribute for configured entries, in order to improve merging of all configurations | 1.0.0 |
| Refactoring: Improve query for fetching existing cms entities by configured entries | 1.0.0 |
## Issues and planned features
See issues to see what's planed next: https://github.com/magento-hackathon/m2-content-provisioning/issues
