Difference between revisions of "SoC template engine"
(Added further reading (links to relevant feature requests)) |
(Added cordiste as co-mentor, added "bonus" to objective) |
||
Line 6: | Line 6: | ||
== Objective == | == Objective == | ||
The biggest concern replacing Geeklog's existing template engine is backwards compatibility. Existing templates should still be usable (or a conversion system created) and code modification to support the new template library should be kept to a minimum so plugins can be easily updated to use the new template library. | The biggest concern replacing Geeklog's existing template engine is backwards compatibility. Existing templates should still be usable (or a conversion system created) and code modification to support the new template library should be kept to a minimum so plugins can be easily updated to use the new template library. | ||
+ | |||
+ | Geeklog currently uses a large number of (relatively) small template files. A big bonus would be a design that can reduce the number of template files to ease template development without sacrificing backwards compatibility. | ||
== Level of Difficulty == | == Level of Difficulty == | ||
Line 11: | Line 13: | ||
'''Mentor:''' Vinny Furia | '''Mentor:''' Vinny Furia | ||
+ | |||
+ | '''Co-Mentor:''' Ben aka "Cordiste" | ||
== Further Reading == | == Further Reading == |
Revision as of 22:21, 8 March 2012
Overview
Geeklog currently uses an antique template system that does not compile templates, nor does it support modern template library features such as loops or compilation. The student selecting this project should research modern template libraries, choosing one to integrate into Geeklog.
Objective
The biggest concern replacing Geeklog's existing template engine is backwards compatibility. Existing templates should still be usable (or a conversion system created) and code modification to support the new template library should be kept to a minimum so plugins can be easily updated to use the new template library.
Geeklog currently uses a large number of (relatively) small template files. A big bonus would be a design that can reduce the number of template files to ease template development without sacrificing backwards compatibility.
Level of Difficulty
high
Mentor: Vinny Furia
Co-Mentor: Ben aka "Cordiste"
Further Reading
Some existing template libraries:
Some relevant feature requests: