Difference between revisions of "GlTheme"
(Created page with "== Introduction == A '''theme''' is the look and feel and '''''outline''''' of a geeklog website. It should never be the case that the usage of a specific theme requires code ...") |
(→Components) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
| − | A '''theme''' is the look and feel and '''''outline''''' of a geeklog website. It should never be the case that the usage of a specific theme requires code changes. A theme is configurable (as is language too). | + | [[File:technologies.png|right]] |
| + | ]A '''theme''' is the look and feel and '''''outline''''' of a geeklog website. It should never be the case that the usage of a specific theme requires code changes. A theme is configurable (as is language too). | ||
A '''theme''' uses templates to render content. | A '''theme''' uses templates to render content. | ||
| Line 17: | Line 18: | ||
A '''templet''' is the workhorse of the template. As opposed to a template that accepts a tRoot (template root directory) and loads the macro text from files, the templet accepts a inline parameter as macros text. Obviously templets process short macro's, also called snippets. A templet is not cache-able. | A '''templet''' is the workhorse of the template. As opposed to a template that accepts a tRoot (template root directory) and loads the macro text from files, the templet accepts a inline parameter as macros text. Obviously templets process short macro's, also called snippets. A templet is not cache-able. | ||
| + | |||
| + | [[Image:jquery.png|frame|right|jQuery]] | ||
| + | |||
| + | A '''library''' is a '''''resource''''' and is declared to resolve dependencies amongst other resources. In general a library contains javascript. Some libraries are loaded on top (head), other require the bottom residence (footer). | ||
A '''resource''' is anything that is needed to render a page in the local client (the browser). Resources of a page may vary depending on characteristics of the connection, on the (type of) browser and even on the device that runs the local browser: think of a page that is loaded by a browser script; since we think of pages as a central concept, the script that loads the page is a resource of the very page. | A '''resource''' is anything that is needed to render a page in the local client (the browser). Resources of a page may vary depending on characteristics of the connection, on the (type of) browser and even on the device that runs the local browser: think of a page that is loaded by a browser script; since we think of pages as a central concept, the script that loads the page is a resource of the very page. | ||
Current resources are limited to style sheets (css) and javascript (js). Resources can show mutual dependency; style sheets cascade and javascripts might depend on a library. | Current resources are limited to style sheets (css) and javascript (js). Resources can show mutual dependency; style sheets cascade and javascripts might depend on a library. | ||
| − | + | [[File:frameworks.png|frame|right|uiKit, Responsive, Bootstrap]] | |
| − | A '''framework''' is a ''''library'''' and is declared to rule the application of css in a dynamic way. In general a framework is based on css and intends to give geek log a responsive character. | + | A '''framework''' is a '''''library''''' and is declared to rule the application of css in a dynamic way. In general a framework is based on css and intends to give the geek log website a responsive character. |
A '''skin''' is a look and feel concept that can be applied to pages or their components. It contains a set of browser instructions. Therefor it bundles css, icons, a color-scheme. It should never be the case that the usage of a specific skin requires code changes other than invoking them. | A '''skin''' is a look and feel concept that can be applied to pages or their components. It contains a set of browser instructions. Therefor it bundles css, icons, a color-scheme. It should never be the case that the usage of a specific skin requires code changes other than invoking them. | ||
| − | A '''layout''' is the frame in which the content is assembled and displayed. A layout can be designed using wireframes ([http://wiki.geeklog.net/index.php?title=Wireframes what is a wireframe?]). It contains css, div-id's, javascript and templates. A layout is referenced in the code. | + | A '''layout''' is the frame in which the content is assembled and displayed. A layout can be designed using wireframes ([http://wiki.geeklog.net/index.php?title=Wireframes what is a wireframe?]). It contains css, div-id's, classnames, javascript and templates. A layout is referenced in the code. |
Latest revision as of 13:19, 30 September 2014
Introduction
]A theme is the look and feel and outline of a geeklog website. It should never be the case that the usage of a specific theme requires code changes. A theme is configurable (as is language too).
A theme uses templates to render content.
A theme could deliver different content for the admin, the logged-in user and the anonymous user.
A theme uses css, javascript, icons, images and other media. A theme renders components commonly known as widgets.
A theme could deliver different look-and-feel's for the admin, the logged-in user and the anonymous user.
A theme can be responsive.
Components
A template is a general purpose macro text body that reflects the blueprint for a page or page component. Templates are used for layouts (and refererence by design the (wire)frames). And complex themes may embed their skins in them too. It consist of content (text) with replaceable parameters (variables), they get parsed and may be recursive, either in itself, either by code.
A templet is the workhorse of the template. As opposed to a template that accepts a tRoot (template root directory) and loads the macro text from files, the templet accepts a inline parameter as macros text. Obviously templets process short macro's, also called snippets. A templet is not cache-able.
A library is a resource and is declared to resolve dependencies amongst other resources. In general a library contains javascript. Some libraries are loaded on top (head), other require the bottom residence (footer).
A resource is anything that is needed to render a page in the local client (the browser). Resources of a page may vary depending on characteristics of the connection, on the (type of) browser and even on the device that runs the local browser: think of a page that is loaded by a browser script; since we think of pages as a central concept, the script that loads the page is a resource of the very page. Current resources are limited to style sheets (css) and javascript (js). Resources can show mutual dependency; style sheets cascade and javascripts might depend on a library.
A framework is a library and is declared to rule the application of css in a dynamic way. In general a framework is based on css and intends to give the geek log website a responsive character.
A skin is a look and feel concept that can be applied to pages or their components. It contains a set of browser instructions. Therefor it bundles css, icons, a color-scheme. It should never be the case that the usage of a specific skin requires code changes other than invoking them.
A layout is the frame in which the content is assembled and displayed. A layout can be designed using wireframes (what is a wireframe?). It contains css, div-id's, classnames, javascript and templates. A layout is referenced in the code.
