Every time you start Oxygen or every time before you commit use the.Here's a simplified overview of how you could work with Oxygen and Git: You can also choose Show blame to see who modified each of In the staging area and choose Show in history to see a history ofĬhanges. On resources which have been modified a number of times you can right click.Pull toolbar button allowing you to obtain those To maps and topics are made directly from the GitHub web interface orįrom the Oxygen WebAuthor, the Git Staging view has a If changes are made by someone else using the same technique or if changes.You can check on the remote GitHub repository that the files were Using the same Git Staging view you can see the newlyĪdded files, stage, commit and push them to the remote GitHub repository.Create a DITA Map and a couple of topics.Toolbar Push button to push it to the GitHub Now the file is committed in your local repository. Stage Selected button to stage it, then write aĬommit message and use the Commit message to commit In the Git Staging view the newly created.The Project menu and create a new Oxygen project in Resources in the project, it will just show the modified resources, so go to The Git Staging view does not show all existing.Choose a location on the local drive where the project will be cloned.+ toolbar button to paste the reference to the This blog post is not about learning Git, it'sĪbout having minimum Git skills to get you started. Shared network drives do not address all the features above and they areĭangerous in the fact that you can overwrite other people's work and there is no wayĪccount can cover all these use cases listed above. Some small teams instead of using a version control system resort to shared networkĭrives. Maintain a list of issues which are closed as your work progresses.Be able to tag releases so you can build manuals for older releases with.See who changed what content in each DITA topic and map.Have a history of changes on each DITA resource, being able to revert to.Allow for reviewers to propose changes without having the right to commit.Collaborate with your colleagues on writing content in the same project.This older blog post has some useful links: There are various online resources for learning DITA, there are also learning DITAĬourses held by consulting companies. The same set of tools has been used for editing and publishing the Oxygen XML Blog: Validation problems on an integration server. Oxygen Validate and Check forĬompleteness used with a scripting license to check for Netlify to build and host a web site for theĭITA content. Gradle to script the publishing in preparation for an Oxygen WebHelp Feedback engine forĮmbedding feedback forms in the HTML pages. Publishing to PDF and WebHelp DITA content on an integration server. Publishing Oxygen XML Author for publishing from inside theĪpplication. Review Oxygen Content Fusion for creating Oxygen Web Author for onlineĮditing/reviewing of DITA content. Editing Oxygen XML Author for editing the DITA contentĪnd for offline publishing. The following list of tools and application will be used in our solution: Content Management and Workflow Github for storing the DITA content. Overview of Tools Proposed for the Solution Showcase for the proposed solution we will have the Oxygen XMLīlog. Number of writers and content) using Oxygen XML Author and Github. So this blog post is about setting up a viable, costĮfficient DITA documentation editing and publishing solution which can scale up (both in There are many cases in which a handful of technical writers in a company need toĬollaborate on a DITA project and they may not have the resources to invest in an open
0 Comments
Leave a Reply. |