Talk:Web template
From Wikipedia, the free encyclopedia
Contents |
[edit] Relationships and dependencies with another articles
Web template is not a isolated article, it is very correlated and "depends on" the article Web template system, and we can adopt:
- the web template system article as "umbrella article".
- Web template and Template engine are complementar articles.
- Specific complements: Web template hook styles and Web template system (formalism).
- Other very correlated articles: preprocessor (referential to not-web template engines), XSLT (main article about XML specific templates), Template (word processing) and Style sheet as referential to template original concepts (from Desktop publishing).
[edit] To Do List
... please update here ...
- All of these sections (to me anyway) have good content and comprise essential sections of the article series. The only one that seems a little shaky to me (in general) is the Template reuse and repositories, only because that seems to have been a source of spam-magnet in the historical legacy of this article. One big issue (for me anyway) is still the question how do we organize material, participation and workflow on these articles? I think this is important because some aspects are still quite difficult. I will send you some proposals soon for you to review to see what you think. dr.ef.tymac 16:59, 30 November 2006 (UTC)
[edit] Template languages section
See Web_template#Template_languages.
It will bigger... To decide: copy/paste to a complementar article.
[edit] History section
See Web_template#History. Need review.
[edit] Sub-template use strategies section
See Web_template#Sub-template_use_strategies. Need review.
[edit] Template reuse and repositories
See Web_template#Template_reuse_and_repositories. Need review for site examples -- many spans was here (!), but we need cite them for exemplify... or find articles about them on wikipedia.
[edit] Terms need change (not very used in english)
- "outputted" is ok?
- I think this is generally considered "grammatically correct", but not "favored usage" ... more favorable examples might include: (as a noun) "X does Y by sending output to Z"; "X sends generated output to Y"; "X produces Y, which is then output to Z"; "X succeeds only if it obtained the output from Y"; (as a verb) "the signal was output to the measuring unit" "the signal is output continuously at a rate of" ... probably the reason that "outputted" is disfavored is because the combining form "putted", when used by itself, is not grammatically correct [citation needed] . dr.ef.tymac 17:15, 30 November 2006 (UTC)
UPDATE: (example) "Nancy putted the box on the shelf." (not grammatically correct, therefore [my speculation is] native english speakers subconciously avoid this kind of usage). dr.ef.tymac 17:18, 30 November 2006 (UTC)
- diagramation and "page arranging" (page structure?)
- For others, User:CmdrObot/robot do a lot to work for us: Condictions→Conditions, Controlable→Controllable, a informal→an informal, a input→an input, aplications→applications, complementar→complementary, condiction→condition, formated→formatted, growed→grew.
[edit] Termonology and style
[edit] Terms with optional ortography
- Programable or Programmable? Used PrograMMable, more used (Google say) on wikipedia, and like on Programmable logic device.
- Parametrized or Parameterized? for "Parametr. reference" and "Parametr. declaration". Used "parametErized" like on Parameterized macro.
[edit] Jargon options
- General programming language jargon: sugestion to use functional programming jargon and concepts, instead Imperative (or procedural) programming ones. But need to use (and contrast) also macro and preprocessor jargon...
- Transformations model and concepts: sugestion to adaptate text to the "informal part" (and not XML dependent) of the XQuery/XSLT/XPath concepts and vocabulary.
- NOT USE commercial synonymous concepts like Database Publishing.
- NOT use the term data model to substitute the terms Content and Content resource:
- It is Web, and W3C and others prefer to use the term Content, about "content on documents" (not "data on documents").
- A data model need Structure. Integrity, Manipulation, Querying... is more simple say that a set of variables are Content than Data model.
- This article was here since October 2005 with the term Content: it is stable and many other linkted articles use the term.
- Is better say "input data" (for process) than say "input model" (it is like to say "input model information")... Example: a "vCard DTD" have the data model information, a "vCard data" have the specific vCard information.
[edit] Big Review/Revert/Adapt = please comment
- Adapted Intro to changes. -- Krauss 24 November 2006
- Reverted picture: the new was only a copy (spam?) from Template processor, not adapted to: 1) The basic concepts fixed here; 2) Another illustrations (see architectures), they are compatible. 3) The picture have 2 outputs to show what it does, for didactic -- Krauss 24 November 2006
[edit] References
Theres is very little references on this page, especially when it comes to the separation into different types of template languages. More references would really help. The singel reference there is seems referenced when it comes to the template languager hierarchy, but it doesn't seem to mention the types of templates in that hierarchy. In fact, it all smells like original research... --Regebro 22:59, 4 December 2006 (UTC)