Displaying 4 results from an estimated 4 matches for "asciidoctor".
2018 Oct 15
0
Introducing the new docs site
...generates the UI bundle in docs-web which
determines how the site looks), and I'll also write READMEs for each
repo so you'll be able to see what each one is for without having to
refer to this mail - this is just a quick explanation of how the system
works.
Cheers,
Petr
[0] https://asciidoctor.org/docs/user-manual/
[1] https://antora.org/
[2] https://github.com/CentOS/docs
[3] https://github.com/CentOS/docs-installation-guide
[4] https://github.com/CentOS/docs-web
2015 Mar 12
6
Docs strategy and tactics [RFC]
...t formats. This
includes converting to an upstream project's preferred format.
Without getting too far ahead here, there are clearly a handful of
solutions that will work well.
For example, we could author using whatever preferred editor in a
markup such as AsciiDoc or MarkDown, then use e.g. AsciiDoctor to do
the conversions (to Mallard, XML, HTML, PDF, ePub, etc.), all with
sources stored in Git.
That would allow for us to mirror content to github.com/CentOS and
people could use Prose.io for editing and pull requests to submit
content. We would sync all that back to git.centos.org.
That sort of...
2015 Mar 16
0
Docs strategy and tactics [RFC]
...verting to an upstream project's preferred format.
>
> Without getting too far ahead here, there are clearly a handful of
> solutions that will work well.
>
> For example, we could author using whatever preferred editor in a
> markup such as AsciiDoc or MarkDown, then use e.g. AsciiDoctor to do
> the conversions (to Mallard, XML, HTML, PDF, ePub, etc.), all with
> sources stored in Git.
>
> That would allow for us to mirror content to github.com/CentOS and
> people could use Prose.io for editing and pull requests to submit
> content. We would sync all that back to...
2015 Mar 16
0
Docs strategy and tactics [RFC]
...rting to an upstream project's preferred format.
>
> Without getting too far ahead here, there are clearly a handful of
> solutions that will work well.
>
> For example, we could author using whatever preferred editor in a
> markup such as AsciiDoc or MarkDown, then use e.g. AsciiDoctor to do
> the conversions (to Mallard, XML, HTML, PDF, ePub, etc.), all with
> sources stored in Git.
>
> That would allow for us to mirror content to github.com/CentOS and
> people could use Prose.io for editing and pull requests to submit
> content. We would sync all that back to...