-
Improvement
-
Resolution: Won't Do
-
Minor
-
None
-
2.5
-
MOODLE_25_STABLE
In response to a collective recommendation (at Perth Hackfest) that HTML markup, IDs and classnames should be simplified or standardized in order to make theme development faster and more foolproof, I've surveyed activity types and recorded some recommendations here: http://docs.moodle.org/dev/Standardize_classnames_and_layout_to_facilitate_theming
I will create the recommendations as children of this task. Many of these child tasks would require significant time looking into the renderers and markup in order to even determine scope. I will capture them here to the best of my ability and hope that the community contributes with comments, ideas, and hopefully code.
Generally, these tasks are meant to address things in core that theme designers don't have access to using the layout files.
1.
|
Add a paragraph renderer |
|
Closed | Unassigned |
2.
|
In places where container() renderer is used and text should be inside <p> tags, replace container() with newly-created paragraph() renderer |
|
Closed | Unassigned |
3.
|
Change uses of #intro to .intro |
|
Closed | Unassigned |
4.
|
Remove uses of .generalbox as parent of all content in central column |
|
Closed | Unassigned |
5.
|
Revise span#maincontent |
|
Closed | Unassigned |
6.
|
Standardize inheritance for tables |
|
Closed | Unassigned |
7.
|
Make header usage hierarchical within page views |
|
Closed | Unassigned |
8.
|
Establish universal label classes and consolidate existing label applications to use these new classes |
|
Closed | Unassigned |
9.
|
Establish universal alert classes and consolidate existing alert applications to use these new classes |
|
Closed | Unassigned |
10.
|
Establish universal button classes and consolidate existing button applications to use these new classes |
|
Closed | Unassigned |