Add StaticContentModule

[craigh]

Q	A
Bug fix?	no
New feature?	yes!
BC breaks?	no
Deprecations?	no
Fixed tickets	-
Refs tickets	-
License	MIT
Changelog updated	yes

Description

Added template display controller for quick generation and display of static template-based content.

To do

- [x] docs
- [x] also add template-based block
- [x] address question of required /p/* in route
- [ ] add permission scheme somewhere

• move content-blocks to new StaticContentModule
• update docs
• update maker (make:zikula-extension) to discourage use of Zikula as vendor
  - [ ] update BlocksModuleInstaller to shift new block creation on install to StaticContentModule and update existing classes.

[Guite]

Any idea where to provide the permission scheme (component ZikulaCoreBundle::, instance static::)? Maybe in the ExtensionsModule?

[Guite]

maybe we should reconsider this information collection for a later release.

agreed; it could also be populated programmatically ($someService->populatePermissionScheme())

[Guite]

I think this would be a use case for adding a custom route (Routes module) to let calendar point to the same controller as p/calendar (additionally).
Centrally adding /{name} would certainly lead to conflicts.

[craigh]

@Guite I am having second thoughts about removing the contents blocks from Blocks module at 3.1.0. I am thinking full removal should wait until 4.0. In the meantime, I think we should add StaticContent module and deprecate the old blocks with plans to remove at 4.0. In the meantime, we can post an alert to the blocks admin that encourages user to move blocks to StaticContent. Then we don't do anything in the upgrade, etc. thoughts?

[Guite]

That would indeed be cleaner. Good idea.

[Guite]

terrific 😃