DekiScript Sitemap

    Table of contents
    1. 1. Tutorial Outline
    2. 2. Sitemap

    The tutorial section needs to be reworked to provide a more gentle progression from casual DekiScript use to templates to extensions to mashups.

    Tutorial Outline

    1. Getting Started
      1. What is DekiScript
      2. Language overview (values, control flow, ...)
    2. Dynamic Page Content
      1. the various wiki.* functions
      2. using HTML attributes to generate content
      3. using XML literals to generate content
    3. Reusable Templates
      1. How templates work
      2. Using parameters in templates
    4. DekiScript Extensions
      1. How extensions work
      2. Limitations of extensions
      3. Benefits of extensions
    5. Working with web-services
      1. Working with XML data
        1. reading in an XML document
        2. reading a value from an XML document
        3. reading a list of values
        4. iterating over an XML document
        5. using xpath
      2. working with JSON data

    Sitemap

    Tag page
    Viewing 3 of 3 comments: view all
    The current structure has too many individual pages (imo). Instead of having 1 page per function (string.compare, string.contains, ...), all functions with the same prefix should be on one page. That will make it much easier for developers to get a quick overview of all the functionality. The same is even truer for objects (page, site, tag, ...) which currently are hyper fragmented.
    Posted 08:56, 27 Jan 2009
    From the technical articles side, we need to differentiate between "how to...", applications, and technical articles. The latter would be a bit like what is found on the CodeProject website.
    Posted 09:01, 27 Jan 2009
    For applications, we need to figure out a packaging structure so that they can be more easily incorporated into other Deki sites. This is a technical work item.
    Posted 09:02, 27 Jan 2009
    Viewing 3 of 3 comments: view all
    You must login to post a comment.

    Copyright © 2011 MindTouch, Inc. Powered by