Luceedocs.com

I really don’t mean to be a naysayer, but in the spirit of being
community-driven and making the docs accessible to use and re-use, plus
allowing them to be consumable by other products (ie- IDE’s etc) shouldn’t
we (as a community) aim toward documentation and references that are
consumable on a variety of fronts? As far as I can see Readme.IO is a
closed system with no external methods to consume resources. Pete
Frietag’s CFDocs project (GitHub - foundeo/cfdocs: Repository for the cfdocs.org site. ) was a good
start to this by using JSON for the documentation markup, but it’s
incomplete and cumbersome to edit. At the very least, though, it’s MIT
licensed and cloneable/forkable.

I disagree with the idea that multiple documentation repositories, may the
best one win, is a good idea. There’s no need for duplication of effort
when we could all be working on one repo of documentation to make it better
and submitting pull requests with updates. Whether that would be on
Bitbucket or GitHub, it doesn’t matter (other than that GitHub receives
better search visibility), but having closed systems to serve documentation
for open source projects seems like a plan destined to have low
participation.

I would much rather see a cloneable GitHub repository, with a single
community leader hosting and handling pull requests to the master, which
serves structured file-based documentation (e.g. - markdown files). It
would also be easier to contribute to in small pieces without having
another system to authenticate in to and another web form to paste content
in to. I just wanted to put this out there before we get too far down the
road with multiple projects.On Friday, February 20, 2015 at 4:25:18 AM UTC-5, Michael van Leest wrote:

Hi everyone,

I made a start of setting up a docs website for Lucee with the help from
readme.io.
They supported by giving me a free license and are looking into cfml code
colouring support so we can show cfml code examples.

Over the coming days I’ll be adding docs for tags and functions and was
hoping 1 or 2 list members could help me with writing examples.

You can find it on luceedocs.com

Let me know what you guys think and if you have any pointers, let me know
(or provide enhancements on the luceedocs.com site.

Regards,


Michael van Leest

I’ve always asked myself how the description to the imageFilter function
could be changed. It’s very large and breaks every normal presentation…

Should I open a lucee ticket for that?

Don’t worry about duplicating effort with regards to documentation, better
have more than less.

No. Better have one excellent documentation that everybody uses than two
incomplete ones.

Also, do we really need versions?On Fri, Feb 20, 2015 at 12:33 PM, Mark Drew <@Mark_Drew> wrote:

@Nando: I’ve approved the edit just as example.

I need to create some sort of basic template so it’s easier to add new
stuff and keep the same layout. I will begin with tags and create the full
documentation of cfabort as an example.2015-02-20 14:51 GMT+01:00 Michael van Leest <@Michael_van_Leest>:

@Mark: If you have a script to export JSON data, that would help a lot!

@Nando: I will transfer the project to Lucee if they would want to
maintain it, sure.

@Michael Offner: Sure! Will let you know.

About versions:
There is already version support in readme.io. You select the cersion you
would like to duplicate and edit the documents that need edits, add new
documents and voila… new version docs (selectable in the main menu).
There is even a “beta” option for a version, so when Lucee 5 Alpha/Beta
comes out, we can already work on v5 specific docs without too much hassle.

Adding a dialect to v5 docs will be something like adding a new group to
the docs “Lucee script” or whatever. Just like tags, functions, objects are
now groups.

Michael

2015-02-20 14:37 GMT+01:00 Nando Breiter <@Nando_Breiter>:

On Fri, Feb 20, 2015 at 12:33 PM, Mark Drew <@Mark_Drew> wrote:

Don’t worry about duplicating effort with regards to documentation,
better have more than less.

No. Better have one excellent documentation that everybody uses than two
incomplete ones.

Agreed.

Also, do we really need versions?

I think so, yes. If the plans to add a new dialect to the language come
to fruition, that release will be very different from previous releases. It
won’t be simply a few incremental improvements that can be documented in
the few tags and functions that have changed. I would hope that creating a
new version of the docset in readme.io is a simple administrative
process that imports the previous version to work from as a base.


You received this message because you are subscribed to the Google
Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/CAG-7QUuLkuWTB9j6fP%3DeU%2BoV1oumQPZevua1oA4NMRViypDdqQ%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAG-7QUuLkuWTB9j6fP%3DeU%2BoV1oumQPZevua1oA4NMRViypDdqQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups
“Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/CAGHrs%3D8mqzZGaaYc9ogWXsE%2BmDajtTuTqyjeWGH5PK2tkHExCQ%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAGHrs%3D8mqzZGaaYc9ogWXsE%2BmDajtTuTqyjeWGH5PK2tkHExCQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.


Michael van Leest


Michael van Leest

Cool. I’ll add you as admin in a bit.On Friday, February 20, 2015, Mark Drew <@Mark_Drew> wrote:

Doesn’t it say they can import it from a github account?

I just emailed them to find out how we could just import this. They have
an API for publishing stuff, but copy and pasting… you will die of old age
:slight_smile: Trust me,

I shall wait to hear what they say.

Mark Drew

develop • deploy • deliver
http://charliemikedelta.com

On 20 Feb 2015, at 15:10, Michael van Leest <@Michael_van_Leest <javascript:_e(%7B%7D,‘cvml’,‘@Michael_van_Leest’);>> wrote:

If you can export it in that way for every tag, that would save huge
amounts of time!
I have to do it for each tag, but that is fine. So 1 file per tag would be
ideal and I’ll update each page with a simple copy/paste.

2015-02-20 16:04 GMT+01:00 Mark Drew <@Mark_Drew
<javascript:_e(%7B%7D,‘cvml’,‘@Mark_Drew’);>>:

I can probably do something that exports the JSON this format, apart
from the block:html maybe? If we do this as a file somewhere would that
help? So that you don’t have to manually do this for every tag/function?

Mark Drew

<cmd.png>
develop • deploy • deliver
http://charliemikedelta.com

On 20 Feb 2015, at 15:01, Michael van Leest <@Michael_van_Leest <javascript:_e(%7B%7D,‘cvml’,‘@Michael_van_Leest’);>> wrote:

@Mark: This is what the raw data of cfabort looks like:

[block:html]
{
“html”: "<ul class="list-inline">\n

  • <a
    href="#summary">Summary
  • \n
  • &middot
  • \n
  • <a
    href="#attributes">Attributes
  • \n
  • &middot
  • \n
  • <a
    href="#tag-examples">Tag examples
  • \n
  • &middot
  • \n
  • <a
    href="#script-examples">Script examples
  • \n
  • &middot
  • \n

  • External examples
  • \n\n
    " } [/block]

    [block:api-header]
    {
    “type”: “basic”,
    “title”: “Summary”
    }
    [/block]
    Stops processing of a page at the tag location. Lucee returns everything
    that was processed before the cfabort tag. The cfabort tag is often used
    with conditional logic to stop processing a page when a condition occurs.
    [block:api-header]
    {
    “type”: “basic”,
    “title”: “Attributes”
    }
    [/block]

    [block:parameters]
    {
    “data”: {
    “h-0”: “Name”,
    “h-1”: “Type”,
    “h-2”: “Required”,
    “h-3”: “Description”,
    “0-0”: “type”,
    “0-3”: “Define if only current page execution will aborted or the
    hole request.\nValues are "page" for the current page or "request" for
    all.”,
    “1-0”: “showerror”,
    “0-1”: “string”,
    “1-1”: “string”,
    “0-2”: “No”,
    “1-2”: “No”,
    “1-3”: “The error to display when cfabort executes.\nThe error
    message displays in the standard CFML error page.”
    },
    “cols”: 4,
    “rows”: 2
    }
    [/block]

    [block:api-header]
    {
    “title”: “Tag examples”,
    “type”: “basic”
    }
    [/block]

    [block:code]
    {
    “codes”: [
    {
    “code”: “This will be output\n\nThis will not”,
    “language”: “text”,
    “name”: “cfabort.cfm”
    }
    ]
    }
    [/block]

    [block:api-header]
    {
    “type”: “basic”,
    “title”: “Script examples”
    }
    [/block]

    [block:code]
    {
    “codes”: [
    {
    “code”: “This will be
    output\n\n\tabort;\n\nThis will not”,
    “language”: “text”,
    “name”: “cfabort.cfm”
    }
    ]
    }
    [/block]

    [block:api-header]
    {
    “type”: “basic”,
    “title”: “External examples”
    }
    [/block]
    There are currently no external examples available for cfabort. Please
    submit any good resources (blog posts, mailing list messages, etc) about
    this specific tag.

    2015-02-20 15:58 GMT+01:00 Michael van Leest <@Michael_van_Leest
    <javascript:_e(%7B%7D,‘cvml’,‘@Michael_van_Leest’);>>:

    Between the lines.

    2015-02-20 15:52 GMT+01:00 Mark Drew <@Mark_Drew
    <javascript:_e(%7B%7D,‘cvml’,‘@Mark_Drew’);>>:

    That is looking pretty good. Is there a way to now generate everything
    and then we can edit it? Is the content stored in gihub? Sorry for the dumb
    questions, the https://readme.io/ site doesn’t answer much about this.

    It’s a git project, but I as far as I’ve seen, it’s a private git system
    they use.

    We can convert the JSON → Markdown of course and just create a repo
    with each version being a tag or branch (can’t remember how readthedocs did
    it) and that should help

    One thing that will be annoying is the left hand navigation. Now it’s
    pretty long and all that there is are tags, wait till you get to the 500 or
    so functions!!! And then Member Methods… each page is going to be mighty
    long.

    I’ve filed a enhancement request for that to make groups collapsable
    (and collapsed as default). It’s automatically generated from the files
    that are created, so no custom stuff in the side menu for now.

    Mark Drew

    <cmd.png>
    develop • deploy • deliver
    http://charliemikedelta.com

    On 20 Feb 2015, at 14:45, Michael van Leest <@Michael_van_Leest <javascript:_e(%7B%7D,‘cvml’,‘@Michael_van_Leest’);>> wrote:

    @Mark: I was already looking at railodocs. I’ve used a similar approach.

    http://www.luceedocs.com/v4.5/docs/cfabort

    2015-02-20 15:15 GMT+01:00 Mark Drew <@Mark_Drew
    <javascript:_e(%7B%7D,‘cvml’,‘@Mark_Drew’);>>:

    @Nando: I’ve approved the edit just as example.

    I need to create some sort of basic template so it’s easier to add new
    stuff and keep the same layout. I will begin with tags and create the full
    documentation of cfabort as an example.

    Like the ones from Railodocs?

    http://www.railodocs.org/tag/cfcache

    I have the ejb templates for functions and tags too.

    It says it can take stuff from a repo and show it. Sounds like
    readthedocs.org?


    You received this message because you are subscribed to the Google
    Groups “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send
    an email to lucee+unsubscribe@googlegroups.com
    <javascript:_e(%7B%7D,‘cvml’,‘lucee%2Bunsubscribe@googlegroups.com’);>.
    To post to this group, send email to lucee@googlegroups.com
    <javascript:_e(%7B%7D,‘cvml’,‘lucee@googlegroups.com’);>.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/4BB6419D-375B-42D0-91CC-CB39F756F3CB%40gmail.com
    https://groups.google.com/d/msgid/lucee/4BB6419D-375B-42D0-91CC-CB39F756F3CB%40gmail.com?utm_medium=email&utm_source=footer
    .
    For more options, visit https://groups.google.com/d/optout.


    Michael van Leest


    Michael van Leest


    You received this message because you are subscribed to a topic in the
    Google Groups “Lucee” group.
    To unsubscribe from this topic, visit
    https://groups.google.com/d/topic/lucee/wsuvmNOxnz0/unsubscribe.
    To unsubscribe from this group and all its topics, send an email to
    lucee+unsubscribe@googlegroups.com
    <javascript:_e(%7B%7D,‘cvml’,‘lucee%2Bunsubscribe@googlegroups.com’);>.
    To post to this group, send email to lucee@googlegroups.com
    <javascript:_e(%7B%7D,‘cvml’,‘lucee@googlegroups.com’);>.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/CAMaJE6u%3D0vn1sDrdgkfohSDeEeLLe0Mmcx5qvYL642xs52kN_A%40mail.gmail.com
    https://groups.google.com/d/msgid/lucee/CAMaJE6u%3D0vn1sDrdgkfohSDeEeLLe0Mmcx5qvYL642xs52kN_A%40mail.gmail.com?utm_medium=email&utm_source=footer
    .
    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to the Google Groups
    “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to lucee+unsubscribe@googlegroups.com
    <javascript:_e(%7B%7D,‘cvml’,‘lucee%2Bunsubscribe@googlegroups.com’);>.
    To post to this group, send email to lucee@googlegroups.com
    <javascript:_e(%7B%7D,‘cvml’,‘lucee@googlegroups.com’);>.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/9C11EE3B-DA91-4BC4-B8FE-D2B0F44DD076%40gmail.com
    https://groups.google.com/d/msgid/lucee/9C11EE3B-DA91-4BC4-B8FE-D2B0F44DD076%40gmail.com?utm_medium=email&utm_source=footer
    .

    For more options, visit https://groups.google.com/d/optout.


    Michael van Leest


    You received this message because you are subscribed to a topic in the
    Google Groups “Lucee” group.
    To unsubscribe from this topic, visit
    https://groups.google.com/d/topic/lucee/wsuvmNOxnz0/unsubscribe.
    To unsubscribe from this group and all its topics, send an email to
    lucee+unsubscribe@googlegroups.com
    <javascript:_e(%7B%7D,‘cvml’,‘lucee%2Bunsubscribe@googlegroups.com’);>.
    To post to this group, send email to lucee@googlegroups.com
    <javascript:_e(%7B%7D,‘cvml’,‘lucee@googlegroups.com’);>.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/CAMaJE6sRG0LAqNud4L0%3Dqx56L4fAPDWUPAaMcXwKkGsSL4SiHw%40mail.gmail.com
    https://groups.google.com/d/msgid/lucee/CAMaJE6sRG0LAqNud4L0%3Dqx56L4fAPDWUPAaMcXwKkGsSL4SiHw%40mail.gmail.com?utm_medium=email&utm_source=footer
    .
    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to the Google Groups
    “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to lucee+unsubscribe@googlegroups.com
    <javascript:_e(%7B%7D,‘cvml’,‘lucee%2Bunsubscribe@googlegroups.com’);>.
    To post to this group, send email to lucee@googlegroups.com
    <javascript:_e(%7B%7D,‘cvml’,‘lucee@googlegroups.com’);>.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/57792C39-4D26-4BAB-AAFD-91276BEC63E9%40gmail.com
    https://groups.google.com/d/msgid/lucee/57792C39-4D26-4BAB-AAFD-91276BEC63E9%40gmail.com?utm_medium=email&utm_source=footer
    .
    For more options, visit https://groups.google.com/d/optout.


    Sent from Gmail Mobile

    I don’t see a link to the repo for creating tickets…?

    Sean Corfield – (904) 302-SEAN
    An Architect’s View – http://corfield.org/

    “Perfection is the enemy of the good.”
    – Gustave Flaubert, French realist novelist (1821-1880)On Feb 20, 2015, at 10:46 AM, Mark Drew <@Mark_Drew> wrote:

    Add a ticket pls. Probably need to create a new Disqus for Luceedocs.

    If you can export it in that way for every tag, that would save huge
    amounts of time!
    I have to do it for each tag, but that is fine. So 1 file per tag would be
    ideal and I’ll update each page with a simple copy/paste.2015-02-20 16:04 GMT+01:00 Mark Drew <@Mark_Drew>:

    I can probably do something that exports the JSON this format, apart from
    the block:html maybe? If we do this as a file somewhere would that help?
    So that you don’t have to manually do this for every tag/function?

    Mark Drew

    develop • deploy • deliver
    http://charliemikedelta.com

    On 20 Feb 2015, at 15:01, Michael van Leest <@Michael_van_Leest> wrote:

    @Mark: This is what the raw data of cfabort looks like:

    [block:html]
    {
    “html”: "<ul class="list-inline">\n

  • <a
    href="#summary">Summary
  • \n
  • &middot
  • \n
  • <a
    href="#attributes">Attributes
  • \n
  • &middot
  • \n
  • <a
    href="#tag-examples">Tag examples
  • \n
  • &middot
  • \n
  • <a
    href="#script-examples">Script examples
  • \n
  • &middot
  • \n

  • External examples
  • \n\n
    " } [/block]

    [block:api-header]
    {
    “type”: “basic”,
    “title”: “Summary”
    }
    [/block]
    Stops processing of a page at the tag location. Lucee returns everything
    that was processed before the cfabort tag. The cfabort tag is often used
    with conditional logic to stop processing a page when a condition occurs.
    [block:api-header]
    {
    “type”: “basic”,
    “title”: “Attributes”
    }
    [/block]

    [block:parameters]
    {
    “data”: {
    “h-0”: “Name”,
    “h-1”: “Type”,
    “h-2”: “Required”,
    “h-3”: “Description”,
    “0-0”: “type”,
    “0-3”: “Define if only current page execution will aborted or the hole
    request.\nValues are "page" for the current page or "request" for all.”,
    “1-0”: “showerror”,
    “0-1”: “string”,
    “1-1”: “string”,
    “0-2”: “No”,
    “1-2”: “No”,
    “1-3”: “The error to display when cfabort executes.\nThe error message
    displays in the standard CFML error page.”
    },
    “cols”: 4,
    “rows”: 2
    }
    [/block]

    [block:api-header]
    {
    “title”: “Tag examples”,
    “type”: “basic”
    }
    [/block]

    [block:code]
    {
    “codes”: [
    {
    “code”: “This will be output\n\nThis will not”,
    “language”: “text”,
    “name”: “cfabort.cfm”
    }
    ]
    }
    [/block]

    [block:api-header]
    {
    “type”: “basic”,
    “title”: “Script examples”
    }
    [/block]

    [block:code]
    {
    “codes”: [
    {
    “code”: “This will be
    output\n\n\tabort;\n\nThis will not”,
    “language”: “text”,
    “name”: “cfabort.cfm”
    }
    ]
    }
    [/block]

    [block:api-header]
    {
    “type”: “basic”,
    “title”: “External examples”
    }
    [/block]
    There are currently no external examples available for cfabort. Please
    submit any good resources (blog posts, mailing list messages, etc) about
    this specific tag.

    2015-02-20 15:58 GMT+01:00 Michael van Leest <@Michael_van_Leest>:

    Between the lines.

    2015-02-20 15:52 GMT+01:00 Mark Drew <@Mark_Drew>:

    That is looking pretty good. Is there a way to now generate everything
    and then we can edit it? Is the content stored in gihub? Sorry for the dumb
    questions, the https://readme.io/ site doesn’t answer much about this.

    It’s a git project, but I as far as I’ve seen, it’s a private git system
    they use.

    We can convert the JSON → Markdown of course and just create a repo
    with each version being a tag or branch (can’t remember how readthedocs did
    it) and that should help

    One thing that will be annoying is the left hand navigation. Now it’s
    pretty long and all that there is are tags, wait till you get to the 500 or
    so functions!!! And then Member Methods… each page is going to be mighty
    long.

    I’ve filed a enhancement request for that to make groups collapsable (and
    collapsed as default). It’s automatically generated from the files that are
    created, so no custom stuff in the side menu for now.

    Mark Drew

    <cmd.png>
    develop • deploy • deliver
    http://charliemikedelta.com

    On 20 Feb 2015, at 14:45, Michael van Leest <@Michael_van_Leest> wrote:

    @Mark: I was already looking at railodocs. I’ve used a similar approach.

    http://www.luceedocs.com/v4.5/docs/cfabort

    2015-02-20 15:15 GMT+01:00 Mark Drew <@Mark_Drew>:

    @Nando: I’ve approved the edit just as example.

    I need to create some sort of basic template so it’s easier to add new
    stuff and keep the same layout. I will begin with tags and create the full
    documentation of cfabort as an example.

    Like the ones from Railodocs?

    http://www.railodocs.org/tag/cfcache

    I have the ejb templates for functions and tags too.

    It says it can take stuff from a repo and show it. Sounds like
    readthedocs.org?


    You received this message because you are subscribed to the Google Groups
    “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/4BB6419D-375B-42D0-91CC-CB39F756F3CB%40gmail.com
    https://groups.google.com/d/msgid/lucee/4BB6419D-375B-42D0-91CC-CB39F756F3CB%40gmail.com?utm_medium=email&utm_source=footer
    .
    For more options, visit https://groups.google.com/d/optout.


    Michael van Leest


    Michael van Leest


    You received this message because you are subscribed to a topic in the
    Google Groups “Lucee” group.
    To unsubscribe from this topic, visit
    https://groups.google.com/d/topic/lucee/wsuvmNOxnz0/unsubscribe.
    To unsubscribe from this group and all its topics, send an email to
    lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/CAMaJE6u%3D0vn1sDrdgkfohSDeEeLLe0Mmcx5qvYL642xs52kN_A%40mail.gmail.com
    https://groups.google.com/d/msgid/lucee/CAMaJE6u%3D0vn1sDrdgkfohSDeEeLLe0Mmcx5qvYL642xs52kN_A%40mail.gmail.com?utm_medium=email&utm_source=footer
    .
    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to the Google Groups
    “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/9C11EE3B-DA91-4BC4-B8FE-D2B0F44DD076%40gmail.com
    https://groups.google.com/d/msgid/lucee/9C11EE3B-DA91-4BC4-B8FE-D2B0F44DD076%40gmail.com?utm_medium=email&utm_source=footer
    .

    For more options, visit https://groups.google.com/d/optout.


    Michael van Leest

    Don’t worry about duplicating effort with regards to documentation,
    better have more than less.

    No. Better have one excellent documentation that everybody uses than two
    incomplete ones.

    Agreed.

    Also, do we really need versions?

    I think so, yes. If the plans to add a new dialect to the language come to
    fruition, that release will be very different from previous releases. It
    won’t be simply a few incremental improvements that can be documented in
    the few tags and functions that have changed. I would hope that creating a
    new version of the docset in readme.io is a simple administrative process
    that imports the previous version to work from as a base.> On Fri, Feb 20, 2015 at 12:33 PM, Mark Drew <@Mark_Drew> wrote:


    You received this message because you are subscribed to the Google Groups
    “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/CAG-7QUuLkuWTB9j6fP%3DeU%2BoV1oumQPZevua1oA4NMRViypDdqQ%40mail.gmail.com
    https://groups.google.com/d/msgid/lucee/CAG-7QUuLkuWTB9j6fP%3DeU%2BoV1oumQPZevua1oA4NMRViypDdqQ%40mail.gmail.com?utm_medium=email&utm_source=footer
    .

    For more options, visit https://groups.google.com/d/optout.

    Cheers for that! I shall get to them next week (house painting this weekend!)
    Having said that, there are already pull requests!

    Mark Drew> On 20 Feb 2015, at 19:15, Sean Corfield <@Sean_Corfield> wrote:

    Thank you! I created a bunch of issues for minor bugs / suggestions.

    Sean

    On Feb 20, 2015, at 10:58 AM, Mark Drew <@Mark_Drew> wrote:
    Here you go sah!

    GitHub - cybersonic/luceedocs: Documentation website and generator for Lucee Server


    You received this message because you are subscribed to a topic in the Google Groups “Lucee” group.
    To unsubscribe from this topic, visit https://groups.google.com/d/topic/lucee/wsuvmNOxnz0/unsubscribe.
    To unsubscribe from this group and all its topics, send an email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/82BD30FC-E25E-4236-8C6E-418286550FE8%40corfield.org.
    For more options, visit https://groups.google.com/d/optout.

    @Mark: If you have a script to export JSON data, that would help a lot!

    @Nando: I will transfer the project to Lucee if they would want to maintain
    it, sure.

    @Michael Offner: Sure! Will let you know.

    About versions:
    There is already version support in readme.io. You select the cersion you
    would like to duplicate and edit the documents that need edits, add new
    documents and voila… new version docs (selectable in the main menu).
    There is even a “beta” option for a version, so when Lucee 5 Alpha/Beta
    comes out, we can already work on v5 specific docs without too much hassle.

    Adding a dialect to v5 docs will be something like adding a new group to
    the docs “Lucee script” or whatever. Just like tags, functions, objects are
    now groups.

    Michael2015-02-20 14:37 GMT+01:00 Nando Breiter <@Nando_Breiter>:

    On Fri, Feb 20, 2015 at 12:33 PM, Mark Drew <@Mark_Drew> wrote:

    Don’t worry about duplicating effort with regards to documentation,
    better have more than less.

    No. Better have one excellent documentation that everybody uses than two
    incomplete ones.

    Agreed.

    Also, do we really need versions?

    I think so, yes. If the plans to add a new dialect to the language come to
    fruition, that release will be very different from previous releases. It
    won’t be simply a few incremental improvements that can be documented in
    the few tags and functions that have changed. I would hope that creating a
    new version of the docset in readme.io is a simple administrative process
    that imports the previous version to work from as a base.


    You received this message because you are subscribed to the Google Groups
    “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/CAG-7QUuLkuWTB9j6fP%3DeU%2BoV1oumQPZevua1oA4NMRViypDdqQ%40mail.gmail.com
    https://groups.google.com/d/msgid/lucee/CAG-7QUuLkuWTB9j6fP%3DeU%2BoV1oumQPZevua1oA4NMRViypDdqQ%40mail.gmail.com?utm_medium=email&utm_source=footer
    .

    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to the Google Groups
    “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/CAGHrs%3D8mqzZGaaYc9ogWXsE%2BmDajtTuTqyjeWGH5PK2tkHExCQ%40mail.gmail.com
    https://groups.google.com/d/msgid/lucee/CAGHrs%3D8mqzZGaaYc9ogWXsE%2BmDajtTuTqyjeWGH5PK2tkHExCQ%40mail.gmail.com?utm_medium=email&utm_source=footer
    .

    For more options, visit https://groups.google.com/d/optout.


    Michael van Leest

    @Mark: If you have a script to export JSON data, that would help a lot!
    luceedocs/jsongen.cfm at luceedocs · cybersonic/luceedocs · GitHub https://github.com/cybersonic/luceedocs/blob/luceedocs/jsongen.cfm

    @Nando: I will transfer the project to Lucee if they would want to maintain it, sure.

    @Michael Offner: Sure! Will let you know.

    About versions:
    There is already version support in readme.io http://readme.io/. You select the cersion you would like to duplicate and edit the documents that need edits, add new documents and voila… new version docs (selectable in the main menu). There is even a “beta” option for a version, so when Lucee 5 Alpha/Beta comes out, we can already work on v5 specific docs without too much hassle.
    That is pretty awesome.

    @Michael,

    Do you understand how versions of the docs are created in readme.io? Let’s
    assume we need a new doc version for 5.0. Do we have to start from zero
    again and recreate all the pages? On the readme.io website, I see
    “Maintaining old or testing beta versions of your docs is a breeze!” but I
    can’t find any detail on how this works. I would hope that creating a new
    version of your docs is also “a breeze” (very easy).

    Aria Media Sagl
    Via Rompada 40
    6987 Caslano
    Switzerland

    +41 (0)91 600 9601
    +41 (0)76 303 4477 cell
    skype: ariamediaOn Fri, Feb 20, 2015 at 12:41 PM, Michael Offner <@Michael_Offner> wrote:

    That’s great!
    Let me know when I can help out with data or information.

    Micha

    Am Freitag, 20. Februar 2015 schrieb Mark Drew :

    AH.,I had already registered luceedocs.org and was porting railodocs.org

    to it as I mentioned before. Great effort but there is no content? I can
    pass you the script that generates the JSON for luceedocs.org if that
    helps?

    GitHub - cybersonic/luceedocs: Documentation website and generator for Lucee Server

    Don’t worry about duplicating effort with regards to documentation,
    better have more than less.

    I was going to work on the Dash docs I have done that before, unless
    someone is already doing it?

    On Friday, February 20, 2015 at 11:27:30 AM UTC, Nando Breiter wrote:

    Michael,

    If the community gets behind this documentation effort, would you be
    willing to transfer “ownership” to the Lucee Association?

    I signed up for an account, and I have a Suggest Edits button, which
    indicates that a core team would need to review suggestions and approve
    them. I don’t have the right to add pages. I think this level of control
    over the content while inviting contributions, is a good feature.

    I also really like the interface. You can insert text (as markdown),
    images, code snippets (either by copying and pasting them or linking from a
    Gist), tables (good for explaining attributes of a tag or function when
    necessary), embed YouTube videos, jsFiddle snippets, PDFs, etc, insert
    callouts, Custom HTML / CSS … this is much more comprehensive than
    anything we could build ourselves in a reasonable amount of time. My
    opinion only, but I think we should all get behind this solution and go for
    it.


    You received this message because you are subscribed to the Google Groups
    “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/35e38379-1153-4af6-8b55-56e6a7570e19%40googlegroups.com
    https://groups.google.com/d/msgid/lucee/35e38379-1153-4af6-8b55-56e6a7570e19%40googlegroups.com?utm_medium=email&utm_source=footer
    .
    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to the Google Groups
    “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/CAG%2BEEByF-v53HDo--W0H573stpjyiTGity5sbrSDZGtZpq9imQ%40mail.gmail.com
    https://groups.google.com/d/msgid/lucee/CAG%2BEEByF-v53HDo--W0H573stpjyiTGity5sbrSDZGtZpq9imQ%40mail.gmail.com?utm_medium=email&utm_source=footer
    .

    For more options, visit https://groups.google.com/d/optout.

    Ok, but would it be new docs for major versions only (Lucee 4, Lucee 5) or
    for each release (would seem too much in my opinion)?

    Thanks,
    JeanOn Fri, Feb 20, 2015 at 2:37 PM, Nando Breiter <@Nando_Breiter> wrote:

    On Fri, Feb 20, 2015 at 12:33 PM, Mark Drew <@Mark_Drew> wrote:

    Don’t worry about duplicating effort with regards to documentation,
    better have more than less.

    No. Better have one excellent documentation that everybody uses than two
    incomplete ones.

    Agreed.

    Also, do we really need versions?

    I think so, yes. If the plans to add a new dialect to the language come to
    fruition, that release will be very different from previous releases. It
    won’t be simply a few incremental improvements that can be documented in
    the few tags and functions that have changed. I would hope that creating a
    new version of the docset in readme.io is a simple administrative process
    that imports the previous version to work from as a base.


    You received this message because you are subscribed to the Google Groups
    “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/CAG-7QUuLkuWTB9j6fP%3DeU%2BoV1oumQPZevua1oA4NMRViypDdqQ%40mail.gmail.com
    https://groups.google.com/d/msgid/lucee/CAG-7QUuLkuWTB9j6fP%3DeU%2BoV1oumQPZevua1oA4NMRViypDdqQ%40mail.gmail.com?utm_medium=email&utm_source=footer
    .

    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to the Google Groups
    “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/CAGHrs%3D8mqzZGaaYc9ogWXsE%2BmDajtTuTqyjeWGH5PK2tkHExCQ%40mail.gmail.com
    https://groups.google.com/d/msgid/lucee/CAGHrs%3D8mqzZGaaYc9ogWXsE%2BmDajtTuTqyjeWGH5PK2tkHExCQ%40mail.gmail.com?utm_medium=email&utm_source=footer
    .

    For more options, visit https://groups.google.com/d/optout.

    Hi Michael,

    Signed up and submitted a test “suggestion”.
    Nice work.

    Regards,
    Dan

    You can generate your own JSON file of the docs from here: luceedocs/jsongen.cfm at master · cybersonic/luceedocs · GitHub https://github.com/cybersonic/luceedocs/blob/master/jsongen.cfm

    I have already done the json files for lucee: luceedocs/export at master · cybersonic/luceedocs · GitHub https://github.com/cybersonic/luceedocs/tree/master/export

    I was looking for a way to do exports but I shall have some time maybe next week to be able to do exporters (like for Dashdocs) and then look at automating dictionaries for cfeclipse and, if I can get my head round it, for sublime text (it’s all rather odd and never had the time to look totally into it)

    I guess having the docs as JSON is a good start no?

    Mark Drew

    develop • deploy • deliver
    http://charliemikedelta.com ttp://charliemikedelta.com> On 20 Feb 2015, at 14:26, Jon Clausen <@Jon_Clausen> wrote:

    I really don’t mean to be a naysayer, but in the spirit of being community-driven and making the docs accessible to use and re-use, plus allowing them to be consumable by other products (ie- IDE’s etc) shouldn’t we (as a community) aim toward documentation and references that are consumable on a variety of fronts? As far as I can see Readme.IO is a closed system with no external methods to consume resources. Pete Frietag’s CFDocs project (GitHub - foundeo/cfdocs: Repository for the cfdocs.org site. ) was a good start to this by using JSON for the documentation markup, but it’s incomplete and cumbersome to edit. At the very least, though, it’s MIT licensed and cloneable/forkable.

    I disagree with the idea that multiple documentation repositories, may the best one win, is a good idea. There’s no need for duplication of effort when we could all be working on one repo of documentation to make it better and submitting pull requests with updates. Whether that would be on Bitbucket or GitHub, it doesn’t matter (other than that GitHub receives better search visibility), but having closed systems to serve documentation for open source projects seems like a plan destined to have low participation.

    I would much rather see a cloneable GitHub repository, with a single community leader hosting and handling pull requests to the master, which serves structured file-based documentation (e.g. - markdown files). It would also be easier to contribute to in small pieces without having another system to authenticate in to and another web form to paste content in to. I just wanted to put this out there before we get too far down the road with multiple projects.

    On Friday, February 20, 2015 at 4:25:18 AM UTC-5, Michael van Leest wrote:
    Hi everyone,

    I made a start of setting up a docs website for Lucee with the help from readme.io http://readme.io/.
    They supported by giving me a free license and are looking into cfml code colouring support so we can show cfml code examples.

    Over the coming days I’ll be adding docs for tags and functions and was hoping 1 or 2 list members could help me with writing examples.

    You can find it on luceedocs.com http://luceedocs.com/

    Let me know what you guys think and if you have any pointers, let me know (or provide enhancements on the luceedocs.com http://luceedocs.com/ site.

    Regards,


    Michael van Leest


    You received this message because you are subscribed to a topic in the Google Groups “Lucee” group.
    To unsubscribe from this topic, visit https://groups.google.com/d/topic/lucee/wsuvmNOxnz0/unsubscribe https://groups.google.com/d/topic/lucee/wsuvmNOxnz0/unsubscribe.
    To unsubscribe from this group and all its topics, send an email to lucee+unsubscribe@googlegroups.com mailto:lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com mailto:lucee@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/b2552b60-c134-48c0-9ee8-f4d8c2f7909d%40googlegroups.com https://groups.google.com/d/msgid/lucee/b2552b60-c134-48c0-9ee8-f4d8c2f7909d%40googlegroups.com?utm_medium=email&utm_source=footer.
    For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

    We did this disco a little while back and I added a link to the XML files
    from each of the pages in the docs. If people want to update the docs
    themselves they have to go to the docs an ALSO to the xml files.
    There was some discussion and people decided that just updating the docs
    was fine, hence my comment about how to do it with the current docs.

    To be honest, I might put a feature in that you can update the docs but
    that would lead to a JIRA ticket with the updates for the dev team.

    It seems to me the problem with not updating the origin XML content is that
    the next time the docs are pulled from those XML files, maybe for the next
    (major) version release, any updates we’ve made to “just the docs” (which I
    interpret to mean the JSON generated from the origin XML) will be reverted.
    Do I have that right?

    And the problem with updating the origin XML is that every pull request or
    ticket would take up the dev team’s time. (Plus it’s certainly more
    difficult to edit XML or JSON than it is to use a well-designed interface).

    Is there is a benefit for the dev team, or the project as a whole, to
    maintaining the origin of the documentation within the source code?On Fri, Feb 20, 2015 at 11:16 PM, Mark Drew <@Mark_Drew> wrote:

    On 20 Feb 2015, at 22:09, Igal @ Lucee.org <@Igal> wrote:

    Nando,

    the tag and function reference text comes from

    Bitbucket
    and

    Bitbucket

    If you find errors or typos you can update those files and submit a patch.

    remember that they are xml files so any changes must be xml compliant.

    thanks,

    Igal Sapir
    Lucee Core Developer
    Lucee.org http://lucee.org/
    On 2/20/2015 1:49 PM, Mark Drew wrote:

    What the project does is make a bunch of JSON files that are the data
    files that drive the site (tags, functions, objects) from a lucee server
    using the following script (no black magic)

    luceedocs/jsongen.cfm at luceedocs · cybersonic/luceedocs · GitHub

    It then generates a folder that you can check out here:

    luceedocs/export/4.5.0.042/json at luceedocs · cybersonic/luceedocs · GitHub

    So you can (at the moment) just send pull requests with changes to each
    of these files (for the develop branch) and we can then display them in the
    site when it gets merged into master.

    Following up from my email of a while ago, I need to have a way to show
    content, so I might integrate that into the md files from the wiki or
    something.

    Or just put them in there as there are plenty of markdown → html
    solutions out there. I shall add a ticket

    Mark Drew

    develop • deploy • deliver
    http://charliemikedelta.com

    On 20 Feb 2015, at 21:45, Nando Breiter <@Nando_Breiter> wrote:

    Mark, this looks fantastic. Thanks!

    Do I understand it correctly that the content itself is in the Lucee
    source code? Where should we submit tickets for typo’s and grammatical
    mistakes? Or maybe a better question might be, how do we maintain and
    contribute to the documentation as a community without it needing to all go
    through Micha and Igal (if the content is within the Lucee source).

    Aria Media Sagl
    Via Rompada 40
    6987 Caslano
    Switzerland

    +41 (0)91 600 9601
    +41 (0)76 303 4477 cell
    skype: ariamedia

    On Fri, Feb 20, 2015 at 10:22 PM, Mark Drew <@Mark_Drew> wrote:

    Cheers for that! I shall get to them next week (house painting this
    weekend!)
    Having said that, there are already pull requests!

    Mark Drew

    On 20 Feb 2015, at 19:15, Sean Corfield <@Sean_Corfield> wrote:

    Thank you! I created a bunch of issues for minor bugs / suggestions.

    Sean

    On Feb 20, 2015, at 10:58 AM, Mark Drew <@Mark_Drew> wrote:
    Here you go sah!

    GitHub - cybersonic/luceedocs: Documentation website and generator for Lucee Server


    You received this message because you are subscribed to a topic in the
    Google Groups “Lucee” group.
    To unsubscribe from this topic, visit
    https://groups.google.com/d/topic/lucee/wsuvmNOxnz0/unsubscribe.
    To unsubscribe from this group and all its topics, send an email to
    lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/82BD30FC-E25E-4236-8C6E-418286550FE8%40corfield.org
    .
    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to the Google Groups
    “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/507D0B9F-2B95-41CA-AEFA-C2BF250A16E8%40gmail.com
    .
    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to a topic in the
    Google Groups “Lucee” group.
    To unsubscribe from this topic, visit
    https://groups.google.com/d/topic/lucee/wsuvmNOxnz0/unsubscribe.
    To unsubscribe from this group and all its topics, send an email to
    lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/CAGHrs%3D_r1Z__oSwo0VSF4kLRXbs0sGKF-ZddLQeYcwSgjn4KoQ%40mail.gmail.com
    https://groups.google.com/d/msgid/lucee/CAGHrs%3D_r1Z__oSwo0VSF4kLRXbs0sGKF-ZddLQeYcwSgjn4KoQ%40mail.gmail.com?utm_medium=email&utm_source=footer
    .
    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to the Google Groups
    “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/163C0286-8330-4B7D-ACF8-D2168E8E29BD%40gmail.com
    https://groups.google.com/d/msgid/lucee/163C0286-8330-4B7D-ACF8-D2168E8E29BD%40gmail.com?utm_medium=email&utm_source=footer
    .
    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to the Google Groups
    “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/54E7B0B2.2020407%40lucee.org
    https://groups.google.com/d/msgid/lucee/54E7B0B2.2020407%40lucee.org?utm_medium=email&utm_source=footer
    .
    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to the Google Groups
    “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/754DA546-5CDE-426B-8689-E1AC70DDC8C3%40gmail.com
    https://groups.google.com/d/msgid/lucee/754DA546-5CDE-426B-8689-E1AC70DDC8C3%40gmail.com?utm_medium=email&utm_source=footer
    .

    For more options, visit https://groups.google.com/d/optout.

    This is a super-cool effort by all involved and makes me feel good about the direction Lucee is headed.On Feb 20, 2015, at 3:41 PM, Mark Drew <@Mark_Drew> wrote:

    Actually that is not the whole picture. Most of the tags and function definition come from those xml files. The rest come from
    Cfml files such as ajaxproxy.cfc

    The point of the docs is to be correct despite the underlying mechanism. Since we now have a way to edit these, making them go back to xml and cfm is pretty trivial.

    Mark Drew

    On 20 Feb 2015, at 23:25, Nando Breiter <@Nando_Breiter> wrote:

    On Fri, Feb 20, 2015 at 11:16 PM, Mark Drew <@Mark_Drew> wrote:
    We did this disco a little while back and I added a link to the XML files from each of the pages in the docs. If people want to update the docs themselves they have to go to the docs an ALSO to the xml files.
    There was some discussion and people decided that just updating the docs was fine, hence my comment about how to do it with the current docs.

    To be honest, I might put a feature in that you can update the docs but that would lead to a JIRA ticket with the updates for the dev team.

    It seems to me the problem with not updating the origin XML content is that the next time the docs are pulled from those XML files, maybe for the next (major) version release, any updates we’ve made to “just the docs” (which I interpret to mean the JSON generated from the origin XML) will be reverted. Do I have that right?

    And the problem with updating the origin XML is that every pull request or ticket would take up the dev team’s time. (Plus it’s certainly more difficult to edit XML or JSON than it is to use a well-designed interface).

    Is there is a benefit for the dev team, or the project as a whole, to maintaining the origin of the documentation within the source code?

    On 20 Feb 2015, at 22:09, Igal @ Lucee.org <@Igal> wrote:

    Nando,

    the tag and function reference text comes from

    Bitbucket
    and
    Bitbucket

    If you find errors or typos you can update those files and submit a patch.

    remember that they are xml files so any changes must be xml compliant.

    thanks,

    Igal Sapir
    Lucee Core Developer
    Lucee.org

    On 2/20/2015 1:49 PM, Mark Drew wrote:

    What the project does is make a bunch of JSON files that are the data files that drive the site (tags, functions, objects) from a lucee server using the following script (no black magic)

    luceedocs/jsongen.cfm at luceedocs · cybersonic/luceedocs · GitHub

    It then generates a folder that you can check out here:

    luceedocs/export/4.5.0.042/json at luceedocs · cybersonic/luceedocs · GitHub

    So you can (at the moment) just send pull requests with changes to each of these files (for the develop branch) and we can then display them in the site when it gets merged into master.

    Following up from my email of a while ago, I need to have a way to show content, so I might integrate that into the md files from the wiki or something.

    Or just put them in there as there are plenty of markdown → html solutions out there. I shall add a ticket

    Mark Drew

    develop • deploy • deliver
    http://charliemikedelta.com

    On 20 Feb 2015, at 21:45, Nando Breiter <@Nando_Breiter> wrote:

    Mark, this looks fantastic. Thanks!

    Do I understand it correctly that the content itself is in the Lucee source code? Where should we submit tickets for typo’s and grammatical mistakes? Or maybe a better question might be, how do we maintain and contribute to the documentation as a community without it needing to all go through Micha and Igal (if the content is within the Lucee source).

    Aria Media Sagl
    Via Rompada 40
    6987 Caslano
    Switzerland

    +41 (0)91 600 9601
    +41 (0)76 303 4477 cell
    skype: ariamedia

    On Fri, Feb 20, 2015 at 10:22 PM, Mark Drew <@Mark_Drew> wrote:
    Cheers for that! I shall get to them next week (house painting this weekend!)
    Having said that, there are already pull requests!

    Mark Drew

    On 20 Feb 2015, at 19:15, Sean Corfield <@Sean_Corfield> wrote:

    Thank you! I created a bunch of issues for minor bugs / suggestions.

    Sean

    On Feb 20, 2015, at 10:58 AM, Mark Drew <@Mark_Drew> wrote:
    Here you go sah!

    GitHub - cybersonic/luceedocs: Documentation website and generator for Lucee Server


    You received this message because you are subscribed to a topic in the Google Groups “Lucee” group.
    To unsubscribe from this topic, visit https://groups.google.com/d/topic/lucee/wsuvmNOxnz0/unsubscribe.
    To unsubscribe from this group and all its topics, send an email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/82BD30FC-E25E-4236-8C6E-418286550FE8%40corfield.org.
    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to the Google Groups “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/507D0B9F-2B95-41CA-AEFA-C2BF250A16E8%40gmail.com.
    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to a topic in the Google Groups “Lucee” group.
    To unsubscribe from this topic, visit https://groups.google.com/d/topic/lucee/wsuvmNOxnz0/unsubscribe.
    To unsubscribe from this group and all its topics, send an email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAGHrs%3D_r1Z__oSwo0VSF4kLRXbs0sGKF-ZddLQeYcwSgjn4KoQ%40mail.gmail.com.
    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to the Google Groups “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/163C0286-8330-4B7D-ACF8-D2168E8E29BD%40gmail.com.
    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to the Google Groups “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/54E7B0B2.2020407%40lucee.org.
    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to the Google Groups “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/754DA546-5CDE-426B-8689-E1AC70DDC8C3%40gmail.com.

    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to the Google Groups “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAGHrs%3D8_2129yW00kbLHBTgLa9vDKmXQm6k%2Bw_7OVTSXnZmdvg%40mail.gmail.com.
    For more options, visit https://groups.google.com/d/optout.


    You received this message because you are subscribed to the Google Groups “Lucee” group.
    To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
    To post to this group, send email to lucee@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/334231FC-3A3D-4424-942A-966047053F8B%40gmail.com.
    For more options, visit https://groups.google.com/d/optout.

    I vote for no surrounding tags. I think it’s just visual noise,
    and subtly conflates the script and tag dialects in a way that could
    tacitly confirm preconceived notions of noisy cfml tag soup in the mind of
    a skeptical outsider. And surely at this point most outsiders are skeptical.

    CFML documentation also has an inglorious history of examples that require
    painful mental code parsing and execution to locate the elusive single line
    or two where the feature in question actually appears. And even then, it’s
    rarely illustrative of the concept, its context, range of possible inputs
    and outputs, etc. I vote for – unlike the sentences in this message
    inflated up by years of peeve – minimalism and quality.On Friday, February 20, 2015 at 10:01:54 AM UTC-5, Risto wrote:

    What do people think about showing tags around script examples?
    I personally prefer script examples not to have tags arund them.

    Oh. Are there multiple “competing” documentation projects running?

    I believe the status quo is that people are toying around - an
    experimental phase where stuff can get done wrong, then scrapped, then done
    better. The consensus seems to be to use Mark’s project as a source of
    documentation and to have people build other sets from there.

    Cool.

    Might it be an idea for the experimental stuff not bother with
    Lucee-centric domain names whilst they’re in that state? There’s no reason
    for them to no simply be like - for example - messingabout.adamcameron.me
    if it was something I was working on.

    In the bigger scheme of things it doesn’t matter so much, but it would cut
    down on confusion a bit perhaps?

    And has there been no specific guidance on the topic of “docs” from the
    Lucee Association? It sounds like it’s a bunch of ppl doing their own
    thing?On Thursday, 26 February 2015 21:51:48 UTC, Adam Cameron wrote:
    On 27 February 2015 at 11:19, Dominic Watson <@Dominic_Watson> wrote:


    Adam

    http://luceedocs.org/ - no www

    Give: This webpage is not available

    Andrew PenhorwoodOn Thursday, February 26, 2015 at 2:23:35 PM UTC-5, Mark Drew wrote:

    What do you mean? Luceedocs.org ?

    Mark Drew

    • Sent by typing with my thumbs.

    On 26 Feb 2015, at 18:27, Andrew Penhorwood <penho...@gmail.com <javascript:>> wrote:

    Is there a URL where we can view a working version of documentation
    output? I once had a URL from Mark’s stuff but can’t seem to find it now.

    Andrew Penhorwood


    You received this message because you are subscribed to a topic in the
    Google Groups “Lucee” group.
    To unsubscribe from this topic, visit
    https://groups.google.com/d/topic/lucee/wsuvmNOxnz0/unsubscribe.
    To unsubscribe from this group and all its topics, send an email to
    lucee+un...@googlegroups.com <javascript:>.
    To post to this group, send email to lu...@googlegroups.com <javascript:>.
    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/747ff437-b147-42c5-b844-bb5c24bee953%40googlegroups.com
    https://groups.google.com/d/msgid/lucee/747ff437-b147-42c5-b844-bb5c24bee953%40googlegroups.com?utm_medium=email&utm_source=footer
    .
    For more options, visit https://groups.google.com/d/optout.