MDN/Archives/Kuma/Scripting

Overview

The mission of the Kuma wiki is to replace MindTouch. One of the advanced features of MindTouch is DekiScript, a Lua-based scripting environment for wiki authors.

We'd like to replace this feature with something secure, capable, modern, and convenient. We'd also like it if we could carry over the existing body of DekiScript with minimal manual changes. Let's see what's feasible.

DekiScript highlights

• Lua-based dynamic scripting language
• XML/HTML literals for easier construction of well-formed markup
• Inline { { script expressions } } in wiki page content
• Long-form Template: scripts callable with parameters from inline expressions
• Local API with access to Wiki data queries (eg. custom tables of contents, etc)
• Network API with access to external web services (eg. RSS feeds, bugzilla, etc)
• Safe for use by wiki content authors
  • (Not entirely sure what makes it safe, need more research)
    • Seems like long-form Template: scripts are editable only by elevated-permission users?
    • Normal content editors can make calls to Template: scripts, but not employ all scripting features?

Proposed high-level infrastructure

Considering this from a high-level view of off-the-shelf parts that could be glued together:

• Kuma wiki CMS (Django/Python)
• Sandboxed server-side JavaScript filter service (node.js)
• Plentiful and intelligent HTTP-based caching

DekiScript samples

Here's some inline script excerpted from en/Firefox_9_for_developers:

    <li>The <code>value</code> attribute of {{HTMLElement("li")}} now can be
    negative as specified in HTML5. Previously negative values were converted
    to 0.</li>

Here's the source of Template:HTMLElement, a commonly used script:

    /* accepts as input one required parameter: HTML element to create a xref to */
    var uri = uri.parts(Page.uri);
    var lang = string.tolower(uri.path[0]);
    if (string.contains(lang, "project") || string.contains(lang, "Project")) {
      let lang = string.substr(lang, 8);
    }
    /* fall back to page.language on a user page */
    else if (string.StartsWith(lang, "user:")) {
      let lang = page.language;
    }
    var name = $0;
    var sectionname = "Element";

    if (!string.compare("es", string.tolower(lang))) {
      let sectionname = "Elemento";
    }

    if (args.title) {
      let name = args.title;
    }
    var dest = lang .. '/' .. 'HTML/' .. sectionname .. '/' .. name;
    var destEng = 'en/HTML/Element/' .. name;
    if (wiki.pageExists(dest)) { /* the page exists */
      <code>(web.link(wiki.uri(dest), '<' .. name .. '>'))</code>;
    } else if (lang == 'zh_tw' && wiki.pageExists(destEng)){
      /* the MozTW community consider links to English pages better than red ones. 
         I'll write about this to mozilla.dev.mdc later */   
      <code>(web.link(wiki.uri(destEng), '<' .. name .. '>'))</code>;
    } else { /* the page doesn't exist */
      var targeturi = "https://developer.mozilla.org/Article_not_found?uri=" .. dest;
      <code><a rel=('internal') href=(targeturi) class=('new')>web.text('<' .. name .. '>')</a></code>
    }

Miscellaneous notes

• Might js-xml-literals come in handy?
• Could we port DekiScript directly? (It's open source, right?)
• Should we get a compiler / language expert in on this for opinions?