Skip to content

Commit 0d48ac9

Browse files
dragos-cimpeanudragos-cimpeanu
committed
Created file with oXygen XML Web Author.
1 parent 8769ed0 commit 0d48ac9

File tree

1 file changed

+142
-0
lines changed

1 file changed

+142
-0
lines changed

‎content-fusion_vs_web-author.dita

+142
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,142 @@
1+
<?xml version="1.0" encoding="UTF-8"?>
2+
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
3+
<topic id="content-fusion_vs_web-author">
4+
<title>Web Author vs. Content Fusion</title>
5+
<body>
6+
<p><b>Oxygen XML Web Author</b> is an online application that leverages the advanced authoring
7+
technology of <term>Oxygen XML Editor/Author</term> to bring XML editing and reviewing to
8+
mobile devices, as well as desktop systems, from anywhere you have internet access.</p>
9+
<p><b>Oxygen Content Fusion</b> is a flexible, intuitive collaboration solution designed to
10+
adapt to virtually any type of workflow that a collaborative team may use for their
11+
documentation review process. <b>Oxygen XML Web Author</b> is integrated into the <b>Content
12+
Fusion</b> interface as its online visual editor.</p>
13+
<p>Both products are designed to provide the ability to collaborate with other members of your
14+
team, from anywhere, and both have an adaptive and innovative user interface designed to allow
15+
you to interact with XML content in the most efficient and productive way possible.</p>
16+
<p>The following table briefly describes the differences between the two products:<table
17+
id="table_wgy_djj_ffb" colsep="1" rowsep="1" frame="all">
18+
<tgroup cols="3">
19+
<colspec colname="c1" colnum="1" colwidth="1*"/>
20+
<colspec colname="newCol2" colnum="2" colwidth="1*" align="center"/>
21+
<colspec colname="c2" colnum="3" colwidth="1*" align="center"/>
22+
<thead>
23+
<row>
24+
<entry>Feature</entry>
25+
<entry>Web Author</entry>
26+
<entry>Content Fusion</entry>
27+
</row>
28+
</thead>
29+
<tbody>
30+
<row>
31+
<entry>Tight integration with the CMS</entry>
32+
<entry>Yes</entry>
33+
<entry>No</entry>
34+
</row>
35+
<row>
36+
<entry>CMS/File server support</entry>
37+
<entry align="left">
38+
<ul id="ul_y42_5kj_ffb">
39+
<li>Git</li>
40+
<li>SharePoint</li>
41+
<li>Any CMS with WebDAV interface</li>
42+
<li>Any CMS that develops a connector using our API</li>
43+
</ul>
44+
</entry>
45+
<entry align="left">Any CMS or file server as long as content authors work with local
46+
files on their computer or using WebDAV.<ph product="fusion"> See <xref
47+
href="using_cf_with_cms.dita"/>.</ph><p>For example:<ul id="ul_xx5_2lj_ffb">
48+
<li>Any version control system: Git, SVN, Perforce</li>
49+
<li>CMS with WebDAV interface.</li>
50+
</ul></p></entry>
51+
</row>
52+
<row>
53+
<entry>Review workflow</entry>
54+
<entry>Can be integrated in an existing workflow</entry>
55+
<entry>Flexible built-in review workflow</entry>
56+
</row>
57+
<row>
58+
<entry>Change tracking</entry>
59+
<entry>Supported</entry>
60+
<entry>Supported and enabled by default</entry>
61+
</row>
62+
<row>
63+
<entry>Comments</entry>
64+
<entry>Yes</entry>
65+
<entry>Yes</entry>
66+
</row>
67+
<row>
68+
<entry>Built-in real-time messaging mechanism</entry>
69+
<entry>No</entry>
70+
<entry>Yes</entry>
71+
</row>
72+
<row>
73+
<entry>Reviewers need a CMS account</entry>
74+
<entry>Yes</entry>
75+
<entry>No</entry>
76+
</row>
77+
<row>
78+
<entry>Reviewers need an account for the review tool</entry>
79+
<entry>No</entry>
80+
<entry>Yes (can use their company account via LDAP)</entry>
81+
</row>
82+
<row>
83+
<entry>Reviewers change the document directly in the CMS</entry>
84+
<entry>Yes</entry>
85+
<entry>No</entry>
86+
</row>
87+
<row>
88+
<entry>Available in the SDK</entry>
89+
<entry>Yes</entry>
90+
<entry>No</entry>
91+
</row>
92+
</tbody>
93+
</tgroup>
94+
</table></p>
95+
<section id="section_nt3_2nj_ffb">
96+
<title>Collaboration Scenarios</title>
97+
<p>An organization can use both products to solve various collaboration scenarios. Here are
98+
just some example scenarios:</p>
99+
<p>
100+
<dl>
101+
<dlentry>
102+
<dt>Collaboration Scenario: Support Team Corrects a Problem in Published Documentation
103+
Using Web Author</dt>
104+
<dd>
105+
<p>The support team notices a problem in the published documentation while offering
106+
support to a customer. </p>
107+
<p><b>Oxygen XML Web Author</b> can be integrated with a repository (for example,
108+
GitHub) and the output can be configured to include an <xref
109+
href="https://www.oxygenxml.com/doc/ug-waCustom/topics/webauthor-integrate-embedded-launch.html"
110+
format="html" scope="external">edit link</xref> and clicking that link would open
111+
the document in <b>Oxygen XML Web Author</b> where they can correct the problem
112+
directly in the source, precisely at the location of the problem, and while it is
113+
fresh in their mind. They could then commit the changes to the repository (for
114+
example, submit the changes as a <xref
115+
href="https://help.github.com/articles/about-pull-requests/" format="html"
116+
scope="external">Pull Request</xref> on GitHub) so that the documentation team can
117+
proofread the changes and easily merge them into their project.</p>
118+
</dd>
119+
</dlentry>
120+
<dlentry>
121+
<dt>Collaboration Scenario: Documentation Team Collaborates with Subject Matter Expert
122+
To Create Content</dt>
123+
<dd>
124+
<p>The documentation team needs to collaborate with a subject matter expert during
125+
content creation. For example, they have questions, or want to see if they worded
126+
something correctly, or they want the SME to add content (such as a code
127+
snippet).</p>
128+
<p>The content author can use <b>Oxygen Content Fusion</b> to create a task with the
129+
documents attached, upload it, and then they can simply share a link to the task
130+
with the SME. The SME simply follows the link to access the review task in a browser
131+
and they use the web-based visual editor to proofread, add comments, and suggest
132+
changes. They can communicate with the content author directly in the <b>Content
133+
Fusion</b> interface, and when they are finished, the content author can easily
134+
merge the suggested changes back into the original documents in <term>Oxygen XML
135+
Editor/Author</term>.</p>
136+
</dd>
137+
</dlentry>
138+
</dl>
139+
</p>
140+
</section>
141+
</body>
142+
</topic>

0 commit comments

Comments
 (0)