Difference between revisions of "SoC template engine"

From GeeklogWiki
Jump to: navigation, search
(Added cordiste as co-mentor, added "bonus" to objective)
m (Further Reading)
(One intermediate revision by the same user not shown)
Line 26: Line 26:
* [http://project.geeklog.net/tracking/view.php?id=1423 Allow a Topic to have it's own Theme]
* [http://project.geeklog.net/tracking/view.php?id=1423 Allow a Topic to have it's own Theme]
* [http://project.geeklog.net/tracking/view.php?id=1424 Allow a Theme to have a Base Theme]
* [http://project.geeklog.net/tracking/view.php?id=1424 Allow a Theme to have a Base Theme]
* [http://project.geeklog.net/tracking/view.php?id=1358 Rework COM_siteHeader and COM_siteFooter]
* [http://project.geeklog.net/tracking/view.php?id=1316 Issue with Blocks in Footer]

Latest revision as of 12:42, 16 March 2012

(Return to the main idea page for the Google Summer of Code)


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.


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


Mentor: Vinny Furia

Co-Mentor: Ben aka "Cordiste"

Further Reading

Some existing template libraries:

Some relevant feature requests: