Welcome!
Our blog contains various useful articles and tutorials covering various aspects of editing, developing, and publishing using Oxygen XML Editor with various XML technologies.
Sometimes (quite often actually) articles originally written for the blog are curated by our technical writers and end up being part of our official documentation: https://www.oxygenxml.com/doc/ug-editor/. However, the blog allows us to deploy various small articles faster, without the need to wait for documentation updates.
Follow us!
You can use an RSS feed reader to follow the blog for new articles: https://blog.oxygenxml.com/rss.xml.
Or you can register to receive emails when new articles are posted.
History of the Oxygen XML Editor Blog
The blog was originally hosted by Google Blogs and the first articles on the blog appeared around 2007. Since Google Blogs did not allow enough flexibility in creating the published content (for example, the inability to create a table of contents) the blog was migrated to DITA XML content stored on GitHub and is now hosted both on the Oxygen XML Web site and on the Netlify platform: https://oxygenxmlblog.netlify.com/.
How the Oxygen XML Editor Blog Works
The entire source code of the Oxygen XML Editor blog is stored in DITA content on a public GitHub repository: https://github.com/oxygenxml/blog.
- Color themes can be easily changed with CSS to modify how the output looks.
- Search functionality. Possibility to add index terms.
- RSS Feed is automatically generated from the entire list of topics.
- PDF output is automatically generated using Oxygen Chemistry Engine and can be customized with CSS.
- EPUB output is automatically generated using DITA For Publishers plugins.
- Each page has an Edit online link allowing it to be edited in the Oxygen XML Web Author.
- Each page has a comments section build using the Oxygen Feedback platform.
- Each time content is added to the project there is a configured GitHub action which runs a validation report of the DITA content (reporting for example broken links).
How You can Contribute to the Oxygen XML Editor Blog.
We want to encourage our end users and collaborators to start creating small Oxygen-related articles for our blog. To post your own articles, follow these steps:
- Create your own GitHub account, if you do not already have one.
- Fork the contents of the Oxygen XML Editor GitHub repository in your own GitHub Repository: https://github.com/oxygenxml/blog. More details about how to fork a repository: https://docs.github.com/en/get-started/quickstart/contributing-to-projects.
- Make changes to your forked project or to a branch from it.
- If you have the Oxygen XML Editor application installed, you can download our Git add-on that should allow you to clone the fork, make changes, and then commit and push them to your repository.
- As an alternative, you can use the Oxygen XML Web Author browser editing tool that has its own Git connector: https://www.oxygenxml.com/oxygen-xml-web-author/app/oxygen.html.
- Please remember to add the name of the author and the created date for
the topic in the DITA topic prolog section
like:
This prolog section will be used to add in the published HTML output the author information after the topic title.<prolog> <author>Radu Coravu</author> <critdates> <created date="2020-01-14"/> </critdates> </prolog>
- Each commit message must include a sign off.
- After all changes have been made to your fork of the project, you can create a pull request to the Oxygen XML Editor original GitHub project.
- There is a GitHub action implemented in the project which will automatically run DITA validation on the entire project branch and will report on the pull request if the validation is successful.
- We will review your changes and if your pull requests is accepted, the blog web site will be automatically updated with the new changes.
Technologies Used to Store, Build and Publish the Oxygen XML Blog
- The blog content is stored on a public GitHub repository.
- GitHub's issues list is used to organize the work and add new improvement ideas.
- Offline editing the blog is done using Oxygen XML Editor with its Git add-on installed.
- Online editing is done using Oxygen Web Author.
- A Gradle build file is used to download a custom DITA Open Toolkit which contains the Oxygen WebHelp Responsive and PDF CSS plugins pre-installed, then run the publishing and validation stages.
- The DITA
Open Toolkit is used along with custom plugins to publish the DITA
content.
- Oxygen WebHelp is used to publish the DITA content to HTML output. Publishing templates are used to customize the published output.
- The Oxygen Feedback system is used for adding feedback forms to each page.
- Oxygen PDF Chemistry is used to produce PDF for the publishing platform.
- The DITA For Publishers plugins are used to produce the EPUB output.
- Oxygen DITA Validate and Check for Completeness is run as a GitHub action with the help of a special scripting license.
- Netlify is used to connect to the repository, run Gradle and publish the WebSite.