luceedocs.com

[Michael van Leest]

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

[Nando Breiter]

Michael,

Seems like a good start to me, especially in that it is a platform designed for documentation. The only thing I'm concerned about is that we don't duplicate the effort.

An interesting bit I see in the FAQ: if you document your API right in your code, you can import it from GitHub! We'll create stubs from the code, and you can edit the rest on the site.

And 

ReadMe was built almost entirely on Open Source projects, so we want to give back. If you're an open source project, shoot us an email and we'll upgrade you to the Developer Hub tier for free. It's the least we can do to give back.

Aria Media Sagl
Via Rompada 40
6987 Caslano
Switzerland

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

--
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+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAMaJE6tpcvh4atS8yL4hhQy37pmUj5EDztqjBk0KjNGrkAtwEA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Michael van Leest]

Hi Nando,

Yes, I have the Open Source discount from them, so no worries there. I'm actively in contact with them for functionality enhancements and UX enhancements, so along the way we help them shape the product as a thank you.

I'll add a TO-DO document later today/this weekend. So if someone wants to start on a document, they can add their name to the document so everyone knows who is working on it.

The import option is currently not working, so that is not an option at this time. I'm setting up all the files myself the coming days and provide a base template for a tag, function and object so people can copy that if they want to start adding stuff to a new page.

I'll update on my progress here and let you know when we can start writing!

Thanks! 

 

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAGHrs%3D_ADJpcfBFB6ajDNsf-RqOTxa-8yF7yfozUmNLV1B_A1w%40mail.gmail.com.

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

--

Michael van Leest

[Nando Breiter]

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. 

Aria Media Sagl
Via Rompada 40
6987 Caslano
Switzerland

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

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAMaJE6sh76kdNZjMFenErAPBso6Z%2BVP6aKqXRR5bA8gDg4KeSQ%40mail.gmail.com.

[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?

https://github.com/cybersonic/luceedocs

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?

[Michael Offner]

That's great! 

Let me know when I can help out with data or information.

Micha

--
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+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/35e38379-1153-4af6-8b55-56e6a7570e19%40googlegroups.com.

[Daniel Jansen]

Hi Michael,

Signed up and submitted a test "suggestion".

Nice work.

Regards,

Dan

[Nando Breiter]

@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: ariamedia

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAG%2BEEByF-v53HDo--W0H573stpjyiTGity5sbrSDZGtZpq9imQ%40mail.gmail.com.

[Jean Moniatte]

On Fri, Feb 20, 2015 at 12:33 PM, Mark Drew <mark...@gmail.com> 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.

Also, do we really need versions?

[Matt Quackenbush]

On Feb 20, 2015 7:13 AM, "Jean Moniatte" <je...@ugal.com> wrote:
>
>
> On Fri, Feb 20, 2015 at 12:33 PM, Mark Drew <mark...@gmail.com> 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.

+infinity

> Also, do we really need versions?

In my opinion, yes. It's often not an option to upgrade to the latest and greatest, and it's very frustrating to be unable to find docs for the version you're stuck on.

[Nando Breiter]

On Fri, Feb 20, 2015 at 12:33 PM, Mark Drew <mark...@gmail.com> 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+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAG-7QUuLkuWTB9j6fP%3DeU%2BoV1oumQPZevua1oA4NMRViypDdqQ%40mail.gmail.com.

[Andrew Penhorwood]

Better to have some documentation then none at all.  If someone wants to create a Lucee documentation site / page / etc, then more power to them.  The best doc site will win in the end.  If people rally around one that is great but don't discourage someone else from creating something else.

Andrew Penhorwood

[Jean Moniatte]

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,

Jean

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAGHrs%3D8mqzZGaaYc9ogWXsE%2BmDajtTuTqyjeWGH5PK2tkHExCQ%40mail.gmail.com.

[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

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAGHrs%3D8mqzZGaaYc9ogWXsE%2BmDajtTuTqyjeWGH5PK2tkHExCQ%40mail.gmail.com.

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

--

Michael van Leest

[Michael van Leest]

@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.

--

Michael van Leest

[Mark Drew]

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

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. 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. 

[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? 

MD 

[Jon Clausen]

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 (https://github.com/foundeo/cfdocs/ )  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.

[Mark Drew]

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

I have already done the json files for lucee: 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

--
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.

To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/b2552b60-c134-48c0-9ee8-f4d8c2f7909d%40googlegroups.com.

[Michael van Leest]

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

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

--
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+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/16B81CA3-A49C-4D9A-A98D-677AEE815FD3%40gmail.com.

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

--

Michael van Leest

[Jon Clausen]

Yikes.  Sorry, Mark. JSON is a very good start, in addition to the markdown files. I should have re-read this full thread. What you’re doing is *exactly* what I was hoping for. I appreciate all of your past and future work on IDE dictionaries.  Sublime does have very cumbersome configuration, snippets, and dictionary files, but it’s a great IDE.  

Thanks for your work on this.

Jon

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+un...@googlegroups.com.

To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/180A21F4-B746-4C7C-9F05-39A4015941F2%40gmail.com.

[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. 

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. 

Mark Drew

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

[Michael van Leest]

@Jon: I agree that a wide useable core project for the docs would be preferable and I would support that. The biggest threshold for me is time. The reason why I started this on readme.io is ease of use. It has most required functionalities and therefor I wanted to make a start instead of waiting for a official decision about documentation.

If someone (Lucee? you?) would like to start a project as you mentioned, I'm happy to help and use that, but for now I'm going to try and get the docs as complete as possible with this solution. Export options for 3rd party services/software is not my biggest concern ATM. There is a export option in readme.io, but will discuss the option for specific exports such as JSON, DashDocs etc).

About the part using a github project vs a closed system, they are the same.

They are both free to browse without any login. And you need an account for both services if you want to provide updates. So that is the same and comes down to preference.

I've asked them to add a license option so that the docs can be licensed under whatever opensource license is needed (instead of manually adding it per page).

Michael

--

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+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/b2552b60-c134-48c0-9ee8-f4d8c2f7909d%40googlegroups.com.

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

--

Michael van Leest

[Michael van Leest]

Between the lines.

2015-02-20 15:52 GMT+01:00 Mark Drew <mark...@gmail.com>:

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

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

On 20 Feb 2015, at 14:45, Michael van Leest <mvan...@gmail.com> 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...@gmail.com>:

@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+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/4BB6419D-375B-42D0-91CC-CB39F756F3CB%40gmail.com.

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

--

Michael van Leest

[Michael van Leest]

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

[block:html]

{

  "html": "<ul class=\"list-inline\">\n  <li><a href=\"#summary\">Summary</a></li>\n  <li>&middot</li>\n  <li><a href=\"#attributes\">Attributes</a></li>\n  <li>&middot</li>\n  <li><a href=\"#tag-examples\">Tag examples</a></li>\n  <li>&middot</li>\n  <li><a href=\"#script-examples\">Script examples</a></li>\n  <li>&middot</li>\n  <li><a href=\"#external-examples\">External examples</a></li>\n</ul>\n<hr>"

}

[/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<cfabort>\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<cfscript>\n\tabort;\n</cfscript>\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. 

--

Michael van Leest

[Risto]

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

[Mark Drew]

I think it should be there at the moment as someone will try it out and it won’t work… 

Mark Drew


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

On 20 Feb 2015, at 15:01, Risto <ck.web...@gmail.com> wrote:

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

--
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.

To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/67645f16-8c69-4c8a-a706-5cfeff017e9d%40googlegroups.com.

[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

Between the lines.

Mark Drew

<cmd.png>

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

On 20 Feb 2015, at 14:45, Michael van Leest <mvan...@gmail.com> 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...@gmail.com>:

@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+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/4BB6419D-375B-42D0-91CC-CB39F756F3CB%40gmail.com.
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+un...@googlegroups.com.

To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAMaJE6u%3D0vn1sDrdgkfohSDeEeLLe0Mmcx5qvYL642xs52kN_A%40mail.gmail.com.

[Michael van Leest]

+1 keeping cfscript in the example.

--

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+un...@googlegroups.com.

To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/9867809B-1B9E-4B9B-BB7E-C2DFB3714546%40gmail.com.

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

--

Michael van Leest

[Michael van Leest]

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/9C11EE3B-DA91-4BC4-B8FE-D2B0F44DD076%40gmail.com.

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

--

Michael van Leest

[Mark Drew]

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 :) 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 <mvan...@gmail.com> 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...@gmail.com>:

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

--

Michael van Leest

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAMaJE6sRG0LAqNud4L0%3Dqx56L4fAPDWUPAaMcXwKkGsSL4SiHw%40mail.gmail.com.

[Michael van Leest]

Cool. I'll add you as admin in a bit.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/57792C39-4D26-4BAB-AAFD-91276BEC63E9%40gmail.com.

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

--
Sent from Gmail Mobile

[Nando Breiter]

I've submitted a few minor edits to cfabort, cleaning up the english a bit, just to try it out. 

Aria Media Sagl
Via Rompada 40
6987 Caslano
Switzerland

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

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAMaJE6sZtD46fDNAWBBNG5q7x-bh%2B-D7epMV0Rm70ViP-bEC%2Bw%40mail.gmail.com.

[Igal @ Lucee.org]

I actually prefer that it won't be there, but instead each example should be in a styled div with a header that says if it's in cfml or cfscript (or other dialects in the future).

then there can be a footnote saying that all cfscript example should be surrounded by the <cfscript> tag.

Igal Sapir
Lucee Core Developer
Lucee.org

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAMaJE6v%3D_DYF7c5cqixG20CAQCano%3DyJgCiS67TEzR%3Dk13a-5Q%40mail.gmail.com.

[Mark Drew]

I have merged your changes and worked on an exporter, which I now need to add ejs template files to generate the output

You can see the app running on: http://luceedocs.herokuapp.com/

(in a while http://www.luceedocs.org should point there) 

[Sean Corfield]

Cool! Love that the search brings up all the member functions too!

The "Download >>" link on the home page goes to http://www.downloads.html 

Disqus isn’t loading on the individual function / tag pages - known issue?

[Mark Drew]

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

Mark Drew

--
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.
To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/52C66E4E-E3CE-4ABA-A104-F1D2CD260EAE%40corfield.org.

[Risto]

Lucee supports all script cfc's correct? If that's true then no need for <cfscript>

Enough critics out there. If they look at Lucee script examples and see <tags> they will say that's not a real script language because you need <tags> which isn't necessarily true.
I guess in a .cfm it is

[Sean Corfield]

On Feb 20, 2015, at 10:46 AM, Mark Drew <mark...@gmail.com> wrote:
> Add a ticket pls. Probably need to create a new Disqus for Luceedocs.

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)

[Mark Drew]

Here you go sah!

https://github.com/cybersonic/luceedocs

Mark Drew

> --
> 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.
> To post to this group, send email to lu...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/46F16EFC-A9B1-4AC6-AFB4-22A3B395D437%40corfield.org.

[Andrew Penhorwood]

@Mark - looks great.  Will there be more examples on the script side of things?

Andrew Penhorwood

[Sean Corfield]

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

Sean

[Adam Cameron]

On 21 February 2015 at 03:26, Jon Clausen <jon_c...@silowebworks.com> wrote:

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.

Agreed. I thought we were waiting on the Lucee bods to make a call on the approach? There seems to just be a lot of railroading going on (r about to go on ~) here. 

"more haste less speed" (which is something ppl say, and I understand the intent, but never the wording)

-- 

Adam

[Adam Cameron]

I personally omit 'em in my blog examples as it focuses purely on the code, and people will "get" that sometimes script blocks need delimiting. I see <cfscript> tags as a parser concern really, rather than being part of the code, per se.

Still: I do not - for once - have a strong opinion either way.

-- 

Adam

On 21 February 2015 at 04:01, Risto <ck.web...@gmail.com> wrote:

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

--

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+un...@googlegroups.com.

To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/67645f16-8c69-4c8a-a706-5cfeff017e9d%40googlegroups.com.

[Mark Drew]

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

Mark Drew

> --
> 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.
> To post to this group, send email to lu...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/82BD30FC-E25E-4236-8C6E-418286550FE8%40corfield.org.

[Nando Breiter]

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

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+un...@googlegroups.com.

To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/507D0B9F-2B95-41CA-AEFA-C2BF250A16E8%40gmail.com.

[Mark Drew]

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) 

https://github.com/cybersonic/luceedocs/blob/luceedocs/jsongen.cfm

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

https://github.com/cybersonic/luceedocs/tree/luceedocs/export/4.5.0.042/json

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

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAGHrs%3D_r1Z__oSwo0VSF4kLRXbs0sGKF-ZddLQeYcwSgjn4KoQ%40mail.gmail.com.

[Igal @ Lucee.org]

Nando,

the tag and function reference text comes from

https://bitbucket.org/lucee/lucee/src/master/lucee-java/lucee-core/src/resource/tld/web-cfmtaglibrary_1_0
    and
https://bitbucket.org/lucee/lucee/src/master/lucee-java/lucee-core/src/resource/fld/web-cfmfunctionlibrary_1_0

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

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/163C0286-8330-4B7D-ACF8-D2168E8E29BD%40gmail.com.

[Mark Drew]

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. 

Mark Drew


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

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

Nando,

the tag and function reference text comes from

https://bitbucket.org/lucee/lucee/src/master/lucee-java/lucee-core/src/resource/tld/web-cfmtaglibrary_1_0
    and
https://bitbucket.org/lucee/lucee/src/master/lucee-java/lucee-core/src/resource/fld/web-cfmfunctionlibrary_1_0

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) 

https://github.com/cybersonic/luceedocs/blob/luceedocs/jsongen.cfm

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

https://github.com/cybersonic/luceedocs/tree/luceedocs/export/4.5.0.042/json

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

<Mail Attachment.png>

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/54E7B0B2.2020407%40lucee.org.

[Jonas Hauß]

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?

[Mark Drew]

No need (I think) 

I have just committed a bunch of changes,:

1) default version is now 4.5.1.000 

2) removed old version as the export was iffy

3) Updated the jsongen.cfm file so that version information is correct

4) removed the uservoice banner since you can add tickets with…

5) ...the Fork me on Github banner and also make comments with...

6) … the Disquss module

7) added a link to tags (soon to add to functions etc) that you can suggest an edit and it points to the right JSON file as well as the right XML file (I think it’s the right file.. need to check since it’s doing some version madness)

HTH 

Mark Drew


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

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

Nando,

the tag and function reference text comes from

https://bitbucket.org/lucee/lucee/src/master/lucee-java/lucee-core/src/resource/tld/web-cfmtaglibrary_1_0
    and
https://bitbucket.org/lucee/lucee/src/master/lucee-java/lucee-core/src/resource/fld/web-cfmfunctionlibrary_1_0

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) 

https://github.com/cybersonic/luceedocs/blob/luceedocs/jsongen.cfm

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

https://github.com/cybersonic/luceedocs/tree/luceedocs/export/4.5.0.042/json

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

<Mail Attachment.png>

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/54E7B0B2.2020407%40lucee.org.

[Jon Clausen]

Mark,

Not quite, though it doesn’t mess up the display jumbotron container display as much.  That imageFilter description is also markdown formatted so it’s a big unformatted blob of text when displayed.  

I just submitted a pull request which adds markdown rendering of the descriptions and a conditional “Full Description” section when the description in the JSON is over 300 chars.

Jon

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/8C674A2C-187E-4565-BCBB-FC08BB450A28%40gmail.com.

[Nando Breiter]

On Fri, Feb 20, 2015 at 11:16 PM, Mark Drew <mark...@gmail.com> 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?

 

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/754DA546-5CDE-426B-8689-E1AC70DDC8C3%40gmail.com.

[Mark Drew]

Awesome work sir! Great idea to use md for descriptions. Check out the work I started on "random docs" in the feature/docs branch. 

Will merge tomorrow!

Mark Drew

On 20 Feb 2015, at 23:21, Jon Clausen <jon_c...@silowebworks.com> wrote:

Mark,

Not quite, though it doesn’t mess up the display jumbotron container display as much.  That imageFilter description is also markdown formatted so it’s a big unformatted blob of text when displayed.  

I just submitted a pull request which adds markdown rendering of the descriptions and a conditional “Full Description” section when the description in the JSON is over 300 chars.

Jon

On February 20, 2015 at 5:28:46 PM, Mark Drew (mark...@gmail.com) wrote:

No need (I think) 

I have just committed a bunch of changes,:

1) default version is now 4.5.1.000 

2) removed old version as the export was iffy

3) Updated the jsongen.cfm file so that version information is correct

4) removed the uservoice banner since you can add tickets with…

5) ...the Fork me on Github banner and also make comments with...

6) … the Disquss module

7) added a link to tags (soon to add to functions etc) that you can suggest an edit and it points to the right JSON file as well as the right XML file (I think it’s the right file.. need to check since it’s doing some version madness)

HTH 

Mark Drew

<4E4D7F71-BA2B-4509-8A23-566E02A542DD@home>

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/etPan.54e7c179.2e4327b0.15e12%40jonclausen-mbp.local.

[Mark Drew]

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

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAGHrs%3D8_2129yW00kbLHBTgLa9vDKmXQm6k%2Bw_7OVTSXnZmdvg%40mail.gmail.com.

[Robert Munn]

This is a super-cool effort by all involved and makes me feel good about the direction Lucee is headed.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/334231FC-3A3D-4424-942A-966047053F8B%40gmail.com.

[Kenneth Redler]

On Friday, February 20, 2015 at 10:01:54 AM UTC-5, Risto wrote:

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

I vote for no surrounding <cfscript> 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.

 

[Dominic Watson]

I've just posted this project on GitHub: https://github.com/DominicWatson/luceedocsbuilder

To be clear, I'm not aiming to create yet another docs site - just demonstrate how I think we can enhance the current import system to better support editorial changes.

Would appreciate any feedback (please see the README for full details).

--

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+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/b7e04c3b-f1a2-4c92-9ffd-84f2864c5a00%40googlegroups.com.

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

--

Pixl8 Interactive, 3 Tun Yard, Peardon Street, London SW8 3HT, United Kingdom T: +44 [0] 845 260 0726• W: www.pixl8.co.uk• E: in...@pixl8.co.uk

Follow us on: Facebook Twitter LinkedIn

CONFIDENTIAL AND PRIVILEGED - This e-mail and any attachment is intended solely for the addressee, is strictly confidential and may also be subject to legal, professional or other privilege or may be protected by work product immunity or other legal rules. If you are not the addressee please do not read, print, re-transmit, store or act in reliance on it or any attachments. Instead, please email it back to the sender and then immediately permanently delete it. Pixl8 Interactive Ltd Registered in England. Registered number: 04336501. Registered office: 8 Spur Road, Cosham, Portsmouth, Hampshire, PO6 3EB

[Andrew Penhorwood]

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

[Jon Clausen]

Mark's current master branch is here:

http://luceedocs.herokuapp.com

On Feb 26, 2015, at 1:27 PM, Andrew Penhorwood <penho...@gmail.com> 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 the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/747ff437-b147-42c5-b844-bb5c24bee953%40googlegroups.com.

[Michael van Leest]

I will work on the bootstrap styling this week and submit a pull request.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/4123B007-A33D-4F14-B342-DC72F2C8AE9A%40silowebworks.com.

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

--

Michael van Leest

[Nando Breiter]

On Thu, Feb 26, 2015 at 7:35 PM, Jon Clausen <jon_c...@silowebworks.com> wrote:

Mark's current master branch is here:

http://luceedocs.herokuapp.com

Or at http://www.luceedocs.org/ (at least I believe they are the same ...) 

[Mark Drew]

Yep. Luceedocs.org points to the master branch that is deployed on heroku. 

Mark Drew

- Sent by typing with my thumbs. 

--
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.

To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAGHrs%3D_eGFxR9xtF-Dfbitf5LPFEg3_F5D3nCpQWigUat-ptUA%40mail.gmail.com.

[Mark Drew]

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> 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.

To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/747ff437-b147-42c5-b844-bb5c24bee953%40googlegroups.com.

[Andrew Penhorwood]

http://luceedocs.org/   -  no www

Give:    This webpage is not available

Andrew Penhorwood

[Mark Drew]

Add the www for the moment. Route 53 is an idiot at apex domains. Will fix tomorrow. 

Mark Drew

- Sent by typing with my thumbs. 

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/7a528da0-1995-4ccb-b1a7-d09ba667c3cb%40googlegroups.com.

[Adam Cameron]

Would it perhaps be an idea to get docs.lucee.org pointed to it too?

On 27 February 2015 at 10:00, Mark Drew <mark...@gmail.com> wrote:

Add the www for the moment. Route 53 is an idiot at apex domains. Will fix tomorrow. 

[Sean Corfield]

And just to avoid confusion due to the subject line, could someone responsible for luceedocs.com pipe up and say where to post issues for that site?

So, reminder:

http://www.luceedocs.org -> https://github.com/cybersonic/luceedocs

(per the "Fork me on GitHub" banner)

http://www.luceedocs.com -> ???

(and it _is_ confusing because that second site only has a list of tags and no content at all!)

Sean

[Adam Cameron]

On 27 February 2015 at 10:49, Sean Corfield <se...@corfield.org> wrote:

(and it _is_ confusing because that second site only has a list of tags and no content at all!)

Oh. Are there multiple "competing" documentation projects running?

-- 

Adam 

[Nando Breiter]

luceedocs.com is powered by readme.io, which seems to be basically a CMS designed for docs, and was a fledgling attempt to get a documentation effort going just before Mark Drew released the auto-generated luceedocs.org site. Since (I think) all content would need to be added manually, luceedocs.org has pretty much blown it out of the water (in my opinion). 

Aria Media Sagl
Via Rompada 40
6987 Caslano
Switzerland

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

--

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+un...@googlegroups.com.

To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/DB91CF10-66D7-46F2-AADC-F0ED3267ECF6%40corfield.org.

[Dominic Watson]

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.

[Adam Cameron]

On Thursday, 26 February 2015 21:51:48 UTC, Adam Cameron wrote:

Oh. Are there multiple "competing" documentation projects running?

On 27 February 2015 at 11:19, Dominic Watson <dominic...@pixl8.co.uk> wrote:

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?

-- 

Adam 

[Sean Corfield]

On Feb 26, 2015, at 2:27 PM, Adam Cameron <dac...@gmail.com> wrote:

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.

Agreed. According to whois, Michael van Leest is the man behind luceedocs.com.

FWIW, searching Google for lucee documentation yields www.luceedocs.org as the 5th and 6th results:

1. Peter Boughton’s Lucee on Jetty wiki

2. FW/1 blog home page (because I posted about the Lucee launch)

3. FW/1 blog post about Lucee compatibility

4. The lucee category on the FW/1 blog

5. www.luceedocs.org

6. The Lucee documentation for cfcomponent

7. Brad Wood’s blog post about Railo and Lucee questions

8. FW/1 on RIAForge (because of Lucee compatibility listed there)

(funnily enough someone who claimed to be a big SEO expert slammed me for moving my blogs to github.io domains saying it would ruin their reputation on Google)

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)

[Mark Drew]

I don't manage the Lucee  domain. Up to Micha I guess. Also luceedocs.org is a fork of railodocs.org. 

Mark Drew

- Sent by typing with my thumbs. 

--
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.
To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAFwR%2BKcJGX7Hi-5wiHRKhHX-kzDdkgYTM08CBdvw3iG6T22r%3Dw%40mail.gmail.com.

[Adam Cameron]

Yes. The suggestion was not directed at you.

But if it's not yet settled which approach the docs will take, that is perhaps a premature suggestion anyhow.

-- 

Adam

On 27 February 2015 at 11:47, Mark Drew <mark...@gmail.com> wrote:

I don't manage the Lucee  domain. Up to Micha I guess. Also luceedocs.org is a fork of railodocs.org. 

[Mark Drew]

Micha and I have had discussions. 

Mark Drew

- Sent by typing with my thumbs. 

--
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.
To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAFwR%2BKce4Ob-rL9uaUgCwG7jtVyPSdYkqCND5vqedtjL4o6SeQ%40mail.gmail.com.

[Michael van Leest]

I'll redirect luceedocs.com to .org later today.

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+un...@googlegroups.com.

To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/28EB2FD3-B929-4607-892E-344A01CDA695%40gmail.com.

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

--
Sent from Gmail Mobile