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.
On 20 Feb 2015, at 15:01, Michael van Leest <@Michael_van_Leest mailto: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 ·\n <a href="#attributes">Attributes\n ·\n <a href="#tag-examples">Tag examples\n ·\n <a href="#script-examples">Script examples\n ·\n <a href="#external-examples">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 mailto:Michael_van_Leest>:
Between the lines.
2015-02-20 15:52 GMT+01:00 Mark Drew <@Mark_Drew mailto: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/ 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 mailto: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 http://www.luceedocs.com/v4.5/docs/cfabort
2015-02-20 15:15 GMT+01:00 Mark Drew <@Mark_Drew mailto: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 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 http://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 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/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 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 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/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 https://groups.google.com/d/optout.
Trust me,