...
So you start at the top of the tab add a tab-in-group and then cut&-and-paste the contextcontent. Don’t forget to make sure that the titles correspondtab’s title corresponds. It is a bit tricky to cut and paste inside a tab (you tend to collect the containing macro) but adding some text before and after aid selection. After a while musvle muscle memory cuts in.
If I am converting a bunch of pages which have a Common XML Attributes / Common XML Elements I usually make the change for one page and leave it unconverted but in the editor. Then you can cut and paste from this into each page (doing change the table tabs gets old very quickly and anything to speed it up helps)
...
If the popup at the bottom disallows conversion you need to find out what else is wrong. The problem is usually nesting, a table inside a table or ( sometimes ) a code within codea table.
3) Make sure all changes are saved
...
Make sure that the tables do not contain and any monospace/code (this formatting. This used to be the our standard for attribute and element names ). The but the new editor does not allow code format to coexist with hyperlinks (because, you know, that might be useful) and . Equally the conversion is uneven (; sometimes code comes out as monospace, but sometimes in a code macro). Finally it monospace/code formatting looks particularly ugly inside a table.
Make sure that the page is full width. Sometime pages are converted narrow, and sometimes full width. You’ll see a
‘<- ->’or a‘-><-’in the top right (ish) of the editor screenpage when in edit-mode.You may need to replace Jira links. The macro works still exists but it doesn’t always seem to get converted cleanly.
Save and then check the rendered output. Tables may need some adjustment to stop needless swap inside cells (but this is less common than when the content was monospace). This can require several iterations/.
Repeat the previous bullet until done.