This is just a short prospect to the future product bundle development.
The Roadmap
General
All of the following objectives need to be configurable. At least as a config variable, but better as setting in sulu backoffice.
Routing #339
Every product needs to have a definable route.
SEO Tab #342
A SEO tab needs to be added to define seo information, as it's already done in SuluArticleBundle.
Preview #344
Products need a preview in backoffice to preview the products page.
Therefore, first, a default preview template needs to be created. Later, of course, the selected template is shown.
Excerpt #345
An excerpt tab is needed for administer excerpt information. This is especially needed for smart content.
Smart content #346
A smart content data provider needs to be implemented to be able to add products dynamically to content pages.
Content templating #347
Content templates structure should be definable as xml, template views as twig. Again, an example can be found in SuluArticleBundle.
Prospectively the data is stored in relational databases by json-decoding the content data. An alternative would be storing the content as xml, which has the advantage of the ability to perform
mysql xpath queries.
Attributes #348
Attributes should be moved to their own bundle: SuluAttributeBundle.
More attribute types should be implemented: selects, bool-values,..
This is just a short prospect to the future product bundle development.
The Roadmap
General
All of the following objectives need to be configurable. At least as a config variable, but better as setting in sulu backoffice.
Routing #339
Every product needs to have a definable route.
SEO Tab #342
A SEO tab needs to be added to define seo information, as it's already done in SuluArticleBundle.
Preview #344
Products need a preview in backoffice to preview the products page. Therefore, first, a default preview template needs to be created. Later, of course, the selected template is shown.
Excerpt #345
An excerpt tab is needed for administer excerpt information. This is especially needed for smart content.
Smart content #346
A smart content data provider needs to be implemented to be able to add products dynamically to content pages.
Content templating #347
Content templates structure should be definable as xml, template views as twig. Again, an example can be found in SuluArticleBundle. Prospectively the data is stored in relational databases by json-decoding the content data. An alternative would be storing the content as xml, which has the advantage of the ability to perform mysql xpath queries.
Attributes #348
Attributes should be moved to their own bundle:
SuluAttributeBundle. More attribute types should be implemented: selects, bool-values,..