Closed Bug 715253 Opened 13 years ago Closed 13 years ago

templates/scripting: define architecture

Categories

(developer.mozilla.org Graveyard :: Wiki pages, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: groovecoder, Assigned: lorchard)

References

Details

(Whiteboard: u=user c=wiki p=3)

Sheppy: describe the data requirements for the templates Then we'll design the overall architecture of the template/scripting system.
Sheppy, can you make a list here of the wiki resources that the scripts need to access? E.g., * Documents/Pages (read, update) * Authors (read) * Revision * etc. Then we'll draw a diagram of the system architecture.
Whiteboard: u=user c=wiki p= → u=user c=wiki p=3
A look at the template usage count will help, here. I've got some ideas about how to build a server-side JS template service, but want to make sure it supports the kinds of data access our current templates need at a minimum. Whether or not it will require rewriting DekiScript by hand or support some kind of recompile/emulation will be an advanced goal. It'll also depend on how complex our existing templates are, or whether the bulk of them are simple code
Assignee: nobody → lorchard
Depends on: 714804
Blocks: 710728
Target Milestone: 2.1 → 2.2
Don't have a diagram yet, but starting to do a brain dump here: https://wiki.mozilla.org/MDN/Kuma/Scripting
There's a diagram now. Going to call this one resolved as a first draft, file follow-up for additional work. https://wiki.mozilla.org/MDN/Kuma/Scripting#Proposed_solution_.231
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Version: Kuma → unspecified
Component: Website → Landing pages
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.