Need new DITA CMS - Any suggestions?


Elizabeth Gschwind (FICO)
 

HI DITA users – one part of FICO’s business is being divested. A lot of their content is written in DITA and they will no longer have access to FICO’s CMS (Tridion Docs). They will NOT be rolled into the new company’s systems and will manage their own documentation. We are wondering if anyone has a recommendation for a light-weight and user-friendly CMS or similar tool for managing their content? They are currently leaning toward using SVN or GIT but will need an XML editor and help with setting up style sheets etc.

 

Does anyone have experience with spinning out content from an existing system, and recommendations?

 

Thank you in advance!

 

Elizabeth Gschwind

Localization Manager | FICO | Tel: +1 415.299.0896 | ElizabethGschwind@...

 

This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.


Sarah O'Keefe
 

Hi Elizabeth,

We have lots of experience with CCMS transitions.

In addition to the issues you've already mentioned, they will need to strip out the proprietary CCMS bits (such as variables, libraries, and conditionals) and map them to standard DITA constructs.

We would be happy to help if consulting support is in the plan.

Regards,

Sarah O'Keefe


May 11, 2021 at 12:38 PM

HI DITA users – one part of FICO’s business is being divested. A lot of their content is written in DITA and they will no longer have access to FICO’s CMS (Tridion Docs). They will NOT be rolled into the new company’s systems and will manage their own documentation. We are wondering if anyone has a recommendation for a light-weight and user-friendly CMS or similar tool for managing their content? They are currently leaning toward using SVN or GIT but will need an XML editor and help with setting up style sheets etc.

 

Does anyone have experience with spinning out content from an existing system, and recommendations?

 

Thank you in advance!

 

Elizabeth Gschwind

Localization Manager | FICO | Tel: +1 415.299.0896 | ElizabethGschwind@...

 

This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.

--
Sarah O’Keefe
CEO, Scriptorium
Schedule a meeting: calendly.com/sarahokeefe


Thomas Rathkamp
 

On Tuesday, May 11, 2021, 11:39:08 AM CDT, Elizabeth Gschwind (FICO) via groups.io <elizabethgschwind@...> wrote:


HI DITA users – one part of FICO’s business is being divested. A lot of their content is written in DITA and they will no longer have access to FICO’s CMS (Tridion Docs). They will NOT be rolled into the new company’s systems and will manage their own documentation. We are wondering if anyone has a recommendation for a light-weight and user-friendly CMS or similar tool for managing their content? They are currently leaning toward using SVN or GIT but will need an XML editor and help with setting up style sheets etc.

 

Does anyone have experience with spinning out content from an existing system, and recommendations?

 

Thank you in advance!

 

Elizabeth Gschwind

Localization Manager | FICO | Tel: +1 415.299.0896 | ElizabethGschwind@...

 

This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.


Mica Semrick
 

Hi Elizabeth,

I think that git + oxygen + oxygen's git plugin works pretty well. It'll be difficult to find a usable solution much cheaper than that. Even better if someone on the team understands git well, as that seems to be a rub on many tech pubs teams.

As far as getting content out of tridion docs, it depends on how much dependency the content has on ishconditions-- if the content's conditions are relatively straight forward, then someone should be able to write some xslt to transfer the ishconditions over to the standard dita conditional attributes. If the ishconditions use a lot of AND and OR statements, the content will likely need some restructuring to achieve the same publishing ends with dita conditions as with ishcondotions.

As for getting content out of tridion docs, I believe you have two choices: do the publication export out of the web ui (which dumps UTF-16 formatted XML with some processing instructions, then convert that to normal UTF-8 dita) or use the dita-ot's dita normalize output (you'll get standard dita out of that).

Hope that helps.

-m


On May 11, 2021 9:38:58 AM PDT, "Elizabeth Gschwind (FICO) via groups.io" <ElizabethGschwind@...> wrote:

HI DITA users – one part of FICO’s business is being divested. A lot of their content is written in DITA and they will no longer have access to FICO’s CMS (Tridion Docs). They will NOT be rolled into the new company’s systems and will manage their own documentation. We are wondering if anyone has a recommendation for a light-weight and user-friendly CMS or similar tool for managing their content? They are currently leaning toward using SVN or GIT but will need an XML editor and help with setting up style sheets etc.

 

Does anyone have experience with spinning out content from an existing system, and recommendations?

 

Thank you in advance!

 

Elizabeth Gschwind

Localization Manager | FICO | Tel: +1 415.299.0896 | ElizabethGschwind@...

 

This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.


ekimber@contrext.com
 

I second Mica's suggestion: Using Oxygen for authoring is always an excellent choice and you then have a number of content management options, including using git, as Mica points out.

There have been many presentations at the various DITA conferences over the last few years on using git to manage DITA content.

There are a number of easy-to-use hosted git repositories you can choose from, including GitHub, BitBucket, GitLab, and Azure DevOps (which basically integrates GitHub into a Jira-style issue tracker and continuous integration platform--I had never used Azure DevOps before a few days ago but I just went through the exercise of setting up a new DevOps instance as test and was pleasantly easy to set up a git repo and connect it to an existing local repo and set up a custom agile project management workflow--in a couple of hours I was ready go).

Cheers,

Eliot

--
Eliot Kimber
http://contrext.com


On 5/11/21, 11:51 AM, "Mica Semrick" <main@dita-users.groups.io on behalf of mica@silentumbrella.com> wrote:



Hi Elizabeth,

I think that git + oxygen + oxygen's git plugin works pretty well. It'll be difficult to find a usable solution much cheaper than that. Even better if someone on the team understands git well, as that seems to be a rub on many tech pubs teams.

As far as getting content out of tridion docs, it depends on how much dependency the content has on ishconditions-- if the content's conditions are relatively straight forward, then someone should be able to write some xslt to transfer the ishconditions over to the standard dita conditional attributes. If the ishconditions use a lot of AND and OR statements, the content will likely need some restructuring to achieve the same publishing ends with dita conditions as with ishcondotions.

As for getting content out of tridion docs, I believe you have two choices: do the publication export out of the web ui (which dumps UTF-16 formatted XML with some processing instructions, then convert that to normal UTF-8 dita) or use the dita-ot's dita normalize output (you'll get standard dita out of that).

Hope that helps.

-m

On May 11, 2021 9:38:58 AM PDT, "Elizabeth Gschwind (FICO) via groups.io" <ElizabethGschwind=fico.com@groups.io> wrote:
HI DITA users – one part of FICO’s business is being divested. A lot of their content is written in DITA and they will no longer have access to FICO’s CMS (Tridion Docs). They will NOT be
rolled into the new company’s systems and will manage their own documentation. We are wondering if anyone has a recommendation for a light-weight and user-friendly CMS or similar tool for managing their content? They are currently leaning toward using SVN
or GIT but will need an XML editor and help with setting up style sheets etc.

Does anyone have experience with spinning out content from an existing system, and recommendations?

Thank you in advance!


Elizabeth Gschwind
Localization Manager | FICO | Tel: +1 415.299.0896 |
ElizabethGschwind@fico.com


This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.


rikp@...
 

Tom,

 

Thank you for the recommendation but XDocs DITA CCMS is now at version 5.2 see www.bluestream.com.

 

Rik

 

Rik Page
Sales and Marketing Director
+44 (0)79 8013 0260

rikp@...

skype: rik.page

www.bluestream.com

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Thomas Rathkamp via groups.io
Sent: 11 May 2021 17:49
To: main@dita-users.groups.io
Subject: Re: [dita-users] Need new DITA CMS - Any suggestions?

 

Elizabeth,

 

Not sure about the conversion aspect, but as a relatively low-cost CMS, I would recommend XDocs from Bluestream. 

 

 

XDocs 1.0 a Revolutionary DITA Enabled XML Content Management System - B...

Bluestream today announced the general availability of XDocs 1.0, an XML content management system.

 

 

 

 

 

 

 

Tom Rathkamp
Senior Technical Writer

 

 

 

On Tuesday, May 11, 2021, 11:39:08 AM CDT, Elizabeth Gschwind (FICO) via groups.io <elizabethgschwind@...> wrote:

 

 

HI DITA users – one part of FICO’s business is being divested. A lot of their content is written in DITA and they will no longer have access to FICO’s CMS (Tridion Docs). They will NOT be rolled into the new company’s systems and will manage their own documentation. We are wondering if anyone has a recommendation for a light-weight and user-friendly CMS or similar tool for managing their content? They are currently leaning toward using SVN or GIT but will need an XML editor and help with setting up style sheets etc.

 

Does anyone have experience with spinning out content from an existing system, and recommendations?

 

Thank you in advance!

 

Elizabeth Gschwind

Localization Manager | FICO | Tel: +1 415.299.0896 | ElizabethGschwind@...

 

This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.


Thomas Rathkamp
 

Ah, my apologies. I sent the wrong link. ;) 



Tom Rathkamp
Senior Technical Writer




On Tuesday, May 11, 2021, 12:40:57 PM CDT, rikp@... <rikp@...> wrote:


Tom,

 

Thank you for the recommendation but XDocs DITA CCMS is now at version 5.2 see www.bluestream.com.

 

Rik

 

Rik Page
Sales and Marketing Director
+44 (0)79 8013 0260

rikp@...

skype: rik.page

www.bluestream.com

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Thomas Rathkamp via groups.io
Sent: 11 May 2021 17:49
To: main@dita-users.groups.io
Subject: Re: [dita-users] Need new DITA CMS - Any suggestions?

 

Elizabeth,

 

Not sure about the conversion aspect, but as a relatively low-cost CMS, I would recommend XDocs from Bluestream. 

 

 

XDocs 1.0 a Revolutionary DITA Enabled XML Content Management System - B...

Bluestream today announced the general availability of XDocs 1.0, an XML content management system.

 

 

 

 

 

 

 

Tom Rathkamp
Senior Technical Writer

 

 

 

On Tuesday, May 11, 2021, 11:39:08 AM CDT, Elizabeth Gschwind (FICO) via groups.io <elizabethgschwind@...> wrote:

 

 

HI DITA users – one part of FICO’s business is being divested. A lot of their content is written in DITA and they will no longer have access to FICO’s CMS (Tridion Docs). They will NOT be rolled into the new company’s systems and will manage their own documentation. We are wondering if anyone has a recommendation for a light-weight and user-friendly CMS or similar tool for managing their content? They are currently leaning toward using SVN or GIT but will need an XML editor and help with setting up style sheets etc.

 

Does anyone have experience with spinning out content from an existing system, and recommendations?

 

Thank you in advance!

 

Elizabeth Gschwind

Localization Manager | FICO | Tel: +1 415.299.0896 | ElizabethGschwind@...

 

This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.


Kristen James Eberlein
 

Hi, Elizabeth.

Please give the group my contact information. I have expert-level experience both with the SDL CCMS and with transitioning users of that CCMS to alternatives. GitHub and SVN are possible choices (if the group will not be localizing content), and there also are some CCMS that they might want to consider.

Eberlein Consulting could assist with all or any of the following, depending on the company's requirements:

  • Selection of a CCMS or version control system
  • Selection of an XML editor
  • Configuration of the XML editor to make the authoring environment as productive and user-friendly as possible
  • Development of DTDs for their new environment
  • Preparation of DITA source for the new environment
  • Stylesheets for PDF, HTML5, etc.
  • Documentation of processes for the new environment
Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
OASIS Distinguished Contributor
Principal consultant, Eberlein Consulting LLC
+1 919 622-1501; kriseberlein (skype)




rikp@...
 

Not a problem Tom 😊

 

This isn’t the forum for us to push our wares but please have a look at the website – we also have experience of migrating from Tridion to Z=XDocs – all DITA is not always equal.

 

Rik

 

+44 (0)79 8013 0260

rikp@...

skype: rik.page

www.bluestream.com

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Thomas Rathkamp via groups.io
Sent: 11 May 2021 18:43
To: main@dita-users.groups.io
Subject: Re: [dita-users] Need new DITA CMS - Any suggestions?

 

Ah, my apologies. I sent the wrong link. ;) 

 

 

 

Tom Rathkamp
Senior Technical Writer

 

 

 

On Tuesday, May 11, 2021, 12:40:57 PM CDT, rikp@... <rikp@...> wrote:

 

 

Tom,

 

Thank you for the recommendation but XDocs DITA CCMS is now at version 5.2 see www.bluestream.com.

 

Rik

 

Rik Page
Sales and Marketing Director
+44 (0)79 8013 0260

rikp@...

skype: rik.page

www.bluestream.com

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Thomas Rathkamp via groups.io
Sent: 11 May 2021 17:49
To: main@dita-users.groups.io
Subject: Re: [dita-users] Need new DITA CMS - Any suggestions?

 

Elizabeth,

 

Not sure about the conversion aspect, but as a relatively low-cost CMS, I would recommend XDocs from Bluestream. 

 

 

XDocs 1.0 a Revolutionary DITA Enabled XML Content Management System - B...

Bluestream today announced the general availability of XDocs 1.0, an XML content management system.

 

 

 

 

 

 

 

Tom Rathkamp
Senior Technical Writer

 

 

 

On Tuesday, May 11, 2021, 11:39:08 AM CDT, Elizabeth Gschwind (FICO) via groups.io <elizabethgschwind@...> wrote:

 

 

HI DITA users – one part of FICO’s business is being divested. A lot of their content is written in DITA and they will no longer have access to FICO’s CMS (Tridion Docs). They will NOT be rolled into the new company’s systems and will manage their own documentation. We are wondering if anyone has a recommendation for a light-weight and user-friendly CMS or similar tool for managing their content? They are currently leaning toward using SVN or GIT but will need an XML editor and help with setting up style sheets etc.

 

Does anyone have experience with spinning out content from an existing system, and recommendations?

 

Thank you in advance!

 

Elizabeth Gschwind

Localization Manager | FICO | Tel: +1 415.299.0896 | ElizabethGschwind@...

 

This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.


Kendall User
 

Along with those suggestions, if you have condition names that are not one of the attribute names in OOTB DITA, you would need to either add specialized attributes or convert them in some way. For example, if you have a condition named sue, there's no attribute named sue.

Then there variables which would need to get converted to keydefs or you could use conrefs.

And, there are publication objects and baselines, which don't map to standard DITA types. You would need to match publications' conditions with ditaval files. Baselines could be made into git tags if you do the migration so that revisions match up with object versions in the CMS.


Michael McLoughlin
 

I have to agree with Mica - do you really need a CCMS here? We moved 18 months ago from a leading DITA CCMS because it was buggy and too expensive to Git/Github + OxygenXML and haven't looked back. We also took the opportunity to switch from unnecessary topic specialisations and remove some of the extra crud added by the CCMS. This took a little work with some bash scripts and the Oxygen XML refactor tool. It tool a month or so planning but we were able to do the entire move over a weekend. A few things we learned in the process:

1. Plan your repository architecture well in GitHub, what doc sets will live where, what branching structure you'll use, and how content can be shared between repos (we used git subtrees for that but there are other solutions such as the git subrepo tool).
2. Make sure the team are trained well on Git workflows. Tools like GitHub Desktop and the Oxygen Git plugin make that a lot easier for those team members who don't like the Git CLI commands.
3. Make sure you train your team on Oxygen. I think most people when they become confident with Oxygen never want to write DITA in anything else.
4. Take advantage of Github Actions for CI/CD stuff.