TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
We switched from Confluence to GitLab/Hugo in the past year. It was an interesting process with a lot of trial and error, and we had to figure out how to re-format a lot of our documentation.
We used internal UI developers to make the templates, etc.
I personally like the change. I spent too much time killing <span> tags in the HTML editor that Confluence put in every time you pasted something in the WYSIWYG editor.
(In fact, it inspired the fake band name <span> tag killaz for me lol.)
We use Atom to edit the code and GitLab to push changes and manage the documentation branches.
If youâd like to see our changes and what our Hugo docs look like, visit docs.cpanel.net. We still keep our developer (API) documentation in Confluence, which you can access from documentation.cpanel.net.
Our internal documentation will remain on Confluence. Weâre still developing the plan to move the API documentation to Hugo later this year.
Rosie Arcelay
Technical Writer II
cPanel, LLC
rosie -at- cpanel -dot- net
> On Feb 5, 2020, at 9:38 PM, Helen OBoyle <hoboyle -at- gmail -dot- com> wrote:
>
> Hi Ed,
>
> On Thu, Feb 6, 2020 at 9:31 AM Marsh, Ed <Ed -dot- Marsh -at- gs -dot- com> wrote:
>> We built our own DITA-to-Confluence workflow. I do not recommend it. It
> worked great for our needs but it was not easy to implement, and future
> versions of Confluence are removing WebDAV connectivity, which breaks our
> process.
>
> Regarding this, do you have firm information on the removal of WebDAV?
> Specifically which versions (server/cloud/etc) of Confluence, and which
> releases (and expected dates) will be affected?
>
> Our writing/publishing team doesn't require this, as we upload and retrieve
> content via the REST API after converting DocBook->Confluence format XML
> via a stylesheet. But other teams (end power users who like to do global
> changes, and another team who integrates our content elsewhere) do use
> WebDAV, so your comment is of interest to me.
>
> Kind regards,
>
> Helen.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as rosie -at- cpanel -dot- net -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and info.
>
> Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com
