Voting starts in March for the Drupal Association Board election.
Mission statement is a setting in Drupal at least in the past half decade. It is configurable on a plain textarea on the site settings page (no input format selection) and is hardwired in themes to show on the front page of the site. Or not at all if the theme customization options have it unchecked.
If we go a bit farther, we see we have a way to put text into a region of the website on one specific page here. Except that it is not defined as a "region", so we cannot put different mission statements on different sections. We cannot place any other thing into the mission region (eg. a map) because there is no way to set the input format and the XSS filtering might not allow things we'd want to do (eg. styling of elements). Also, this whole mission setting and its visibility is hidden in the site settings and theme settings, while other blocks we put on the page are editable and their visibility can be set on the blocks admin.
All-in-all if you think this through, making the mission a region and letting people put arbitrary custom blocks in there can have several advantages:
- I can have a mission statement displayed on more then the front page (e.g also on the company team page).
- I can have the mission statement only displayed somewhere else, but not on the front page (eg. only on the company team page).
- I can set whatever input format I want so I can even display complex maps.
- I can put more then one block into that region, so dynamic data can be output there via module defined blocks.
There are two disadvantages:
- Setting up visibility rules for blocks is slightly more complex compared to the theme setting checkbox for the mission statement (but allows for a multitude more options - eg. I can have different missions for different roles).
- The mission statement was used in the sitewide node RSS feed as a description. I am not convinced that the site mission is an adequate description for that feed, so I don't consider this a considerable loss.
An update path should obviously be implemented if the concept is approved. That update path would see if there is a mission statement already and create a custom block for that region if there is one. Otherwise it would not do anything.
The attached patch *removes 26 lines* and *only adds 1* to implement my suggestion. (Yes, I have completely similar plans for the footer message, except it only has a region defined, so it would not have any new lines added except the update path :).
This is how a custom block is set in the region (no surprises):
This is how it is displayed on the same blocks admin page (no visibility is set yet for this block on my site):
Ps. some people said in similar issues that I should consider that blocks module is not required anymore for replacements like Panels to be able to do the whole page display. Well, Panels already exposes blocks, so getting rid of a special case for the site mission would help Panels as well, since it would just treat this as a regular block again.
|#42||site-mission-with-fixed-upgrade.patch||17.03 KB||Gábor Hojtsy|
|#39||site-mission-with-fixed-upgrade.patch||16.85 KB||Gábor Hojtsy|
Failed: 11228 passes, 0 fails, 5 exceptions View
|#37||remove-mission.patch||15.23 KB||Gábor Hojtsy|
|#28||mission-with-site-description.patch||15.19 KB||Gábor Hojtsy|
|#26||remove-mission-reroll.patch||11.6 KB||Gábor Hojtsy|
Failed: 11164 passes, 0 fails, 8 exceptions View