Help Center: Reusable content

Respondida

22 Comentários

  • Tony Poetz
    Ações de comentário Permalink

    +1 for basic DITA capabilities. 

    Our software uses specific terms and phrases that occasionally change. When our Product Management department states we now refer to "Resume Parser" as "Resume Processor," it would be great if that tagged value could be edited in one place to affect the 259 instances of the term "Resume Parser."

    Thanks!

    6
  • Ryan McGrew
    Ações de comentário Permalink

    Hey All,

    In general, yes we're looking at re-useable content and there's a few different use cases around that I'll try to outline below and give a few insights into where it might fit into our plan

    • Publishing a single article to multiple sections or Help Centers - I've said this in a few other places as well but this is part of a larger work stream and we plan to have an EAP of this functionality available in Q1 2019
    • Article templates - This is about being able to create an article from a base template and the author can fill in the details. We currently have some functionality around this using our Knowledge Capture applications. We are doing deeper research here to understand more about his and flesh out how it will work. No timeline yet on feature availability
    • Re-use of portion of an article in multiple articles - We currently have some support in macros and themes for Dynamic Content. We are looking at ways to up-level this into truly re-useable excerpts kind of like Atlassian. No timeline yet on feature availability.
    • DITA Support - As mentioned in a few places in this thread, there are a number of DITA based tools like Oxygen and Paligo. These are great and complex tools for documentation authoring. A few of these have already built integrations to Zendesk using our APIs or could be extended to integrate with Zendesk via the API. We haven't yet settled on any plans to investigate this further.

    Also @Sarah, awesome to see people nerd out about this stuff :)

    6
  • Ted Cox
    Ações de comentário Permalink

    How we'd employ content reuse:

    • Using a string of text to insert a URL into an article. For example, let's say we have five articles that link to https://some-website.com/common-resource.

      With content reuse, that URL could be referenced with something like a shortcode:

      [common-resource-URL]

      We then drop the shortcode into all five articles. Guide parses the shortcode and then displays the URL in all five articles.

    • Using a string of text to substitute for a definition. Let's say we have five articles that all include a short paragraph describing our product, Foobar. With content reuse, we drop in the shortcode [foobar-definition] into the article bodies. Guide would display an identical definition in each article body.

    • Using a string of text to substitute for an ordered list. Let's say we have five articles that all include these steps:

      1. Update the foo.
      2. Select the bar.
      3. Save your changes.

      With content reuse, we can reference that ordered list with a shortcode: [foo-the-bar-procedure]. So anytime we drop that shortcode in an article, the ordered list generates automatically.

     

    Now the why:

    Without content reuse, we have to manually update those five articles whenever a URL, definition, or procedure changes. And with articles spanning multiple categories or sections, we have to hope that running a search on Zendesk tells us all the places where we need to update certain content.

    With content reuse, all you have to do is update one piece of content and the changes are deployed across multiple articles. See https://en.wikipedia.org/wiki/Single_source_of_truth. 

    3
  • Dovile Janule
    Ações de comentário Permalink

    Hi everyone,

    We are doing research around various customer needs related to how they might user variables (sometimes called placeholders) in Guide Content. Specifically we'd like to hear more about how you and your organisation would use features like: Frequently used names, contextual information, placeholders and formatted snippets, inline images, etc.

    If you're interested in this research and would like to share your opinion, please fill out this form.

     

    Guide team.

    2
  • Sarah Holdgrafer
    Ações de comentário Permalink

    I'm currently trialing a cloud-based CCMS that integrates with ZenDesk Guide that could be a viable solution for some on this thread. 

    https://paligo.net/

    • Uses topic-based authoring
    • Enables topic re-use
    • Based on DocBook framework (but also integrates with Oxygen XML Author/Editor for those who prefer DITA)

    I've published a few articles to our ZD sandbox and it was very straightforward, though I'll have to do some editing of our ZD theme and the Paligo CSS file to maintain the styles we want in our articles. 

    It looks like this might be a great solution for teams that don't have the time/resources to learn Python and manually leverage the ZD API. Paligo handles all of that for you and frees up the documentation team to focus on the content and strategy. I am giving myself a crash course on structured authoring right now (a huge topic, really) but this experience has been really eye-opening. 

     

    1
  • Sarah Holdgrafer
    Ações de comentário Permalink

    Hey Rebecca, 

    The Paligo trial has been super interesting and a great learning experience (I basically got a crash course in structured and topic-based authoring in the last month and a half, which has completely changed my perspective on how my company has been doing things - shout out to the Write the Docs community for chatting with me and sending me tons of great content).

    The rep I've been working with (Steve) and the support people who answered my questions have all been incredibly responsive and also quite knowledgeable about how to manage the ZenDesk integration effectively. It's also clear they are really passionate about their platform and its benefits.

    We decided to get a license for my team and we are also bringing the Paligo trainer down to train my team on advanced features (like versioning and localization), best practices, and strategies. Since all of our content is currently unstructured, the trainer will also be workshopping our content directly with us to ensure we can hit the ground running.

    The platform itself is super intuitive, as is the publishing workflow. I'm really looking forward to developing our new strategy, and already have a ton of ideas that go well beyond just our knowledge base that would be logistically very difficult without such a platform. 

    I've shown it to our marketing dept with some of my ideas about how we can use it for various types of user documentation (specifically for onboarding), so they're intrigued as well but don't have the bandwidth to handle it right now. Meaning, I'm basically the company guinea pig :-) I think in a few months I can come to them with some deliverables, blow their mind, and then train them all on it as well. Is it weird that I'm so excited about this? ;-)

     

    1
  • Claire Nasuti
    Ações de comentário Permalink

    +1

    0
  • Ted Cox
    Ações de comentário Permalink

    +1

    0
  • Mollie Swenson
    Ações de comentário Permalink

    +1

    0
  • Jan-Hendrik Spieth
    Ações de comentário Permalink

    +1!

    0
  • James Esquivel
    Ações de comentário Permalink

    +1

    0
  • Nicole - Community Manager
    Ações de comentário Permalink

    Hey all - 

    Please make sure you've used the voting buttons on the original post to add your +1. Does anyone else have examples of how you would use this functionality or why you need it? 

    0
  • Sarah Holdgrafer
    Ações de comentário Permalink

    this would be great to have natively within ZD, but as a secondary option does anyone know of content management tools that could be used to create/manage KB content and then uses the ZD API to push the content to Guide?

     

    0
  • Jenn
    Ações de comentário Permalink

    Hello,

    I am wondering if you have developed a way to integrate DITA content and Oxygen template design into Zendesk. Above you state that you use a DITA author (Oxygen?) to create your content and then convert to html and then push to the Knowledge Base? That seems a rather inefficient way to create content.

    Are you looking at a way where we could use oxygen to create the content and not have to convert then push?

    Also, when will one be able to create subsections within sections, and other ways to more cleanly display your KB topics? I have not seen anything about when this may, if ever, be available. I would like to be able to subdivide sections and have the subsections collapsible as I can when using Oxygen. 

    0
  • Nicole - Community Manager
    Ações de comentário Permalink

    Hi Jenn - 

    More flexibility with categories and sections are tentatively planned for development later this year. Timelines may change and it is not guaranteed, but we do have it on the roadmap. 

    0
  • Rebecca McMurry
    Ações de comentário Permalink

    +1 for basic DITA capabilities.

    I am also interested in your https://paligo.net/ experience Sarah Holdgrafer  Its been a few weeks how is it going?

     

    Is there any intention of putting DITA on the Guide roadmap in the next 18 months?

    0
  • Nicole - Community Manager
    Ações de comentário Permalink

    Hey Rebecca - 

    I'll check with the product managers and see if that's something they're discussing. 

    0
  • Jonathan March
    Ações de comentário Permalink

    @Ryan, thanks -- Dynamic Content in article text would be huge!

    0
  • Rebecca McMurry
    Ações de comentário Permalink

    Agree with Johathan's comment on Dynamic Content being huge. It would make changing a product or company name soooo much easier.

    0
  • Yehudit Kunkel
    Ações de comentário Permalink

    @nicole @ryan - any update vis-a-vis timetable to get ZD to work with re-usable content?

    0
  • Rebecca McMurry
    Ações de comentário Permalink

    Hi Ryan, 

    Any progress on the Dynamic Content? It would be a huge plus to be able to re-use content.

     

    0

Por favor, entrar para comentar.

Desenvolvido por Zendesk