In Docmost, there are no Homepage, and that break Hierachy and fuctionality, many homepages has a Confluence Macro that list children.
In my opinion, that is critical. Even without a homepage, hierachy should always be maintained. Its the same as below
Confluence:
In my opinion, that is critical.
DocMost:
This is also all wrong:
This is problably true for most, and I do think:
Page include - could be supported, but its actually not a good macro for all purposes, for example a "verified page" that has inclusion of other pages - what happend if the included part changes. In confluence nothing, and that its not good. So the importer could set a link in instead.
Its fair that Confluence User macros are not imported(they are custom code).
But there should (at least) be set someting in like:
[Confluence User Macro: me-image] |
For optimal migration, Docmost shoudl have a script "engine" as Conflucene and Wxiki has, that renders code realtime on a page
Confluence:
Storage format:
<table class="wrapped fixed-table">
<colgroup>
<col style="width: 271.0px;"/>
<col style="width: 310.0px;"/>
</colgroup>
<tbody>
<tr>
<th>
<p>Type</p>
</th>
<td>Espresso/Kasse maskine</td>
</tr>
<tr>
<td class="highlight-grey" data-highlight-colour="grey">
<p>Min rating (1-5 Stjerner)</p>
</td>
<td>
<div class="content-wrapper">
<ac:structured-macro ac:macro-id="ff70c249-629b-4f33-a0bd-1cff3e79102b" ac:name="excerpt" ac:schema-version="1">
<ac:parameter ac:name="atlassian-macro-output-type">BLOCK</ac:parameter>
<ac:rich-text-body>
<p>
<ac:emoticon ac:name="yellow-star"/>
<ac:emoticon ac:name="yellow-star"/>
<ac:emoticon ac:name="yellow-star"/>
<ac:emoticon ac:name="yellow-star"/>
</p>
</ac:rich-text-body>
</ac:structured-macro>
</div>
</td>
</tr>
</tbody>
</table> |
Docmost:
