Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Scribbled notes on converting from old editor to new editor

Before conversion

1) Convert tabs

The start point is

  • TabGroup

    • Tab

      • Content

    • Tab

      • Content

The end point is

  • TabGroup

    • Tab-In-Group

    • Content

    • Tab-In-Group

    • Content

So you start at the top of the tab add a tab-in-group and then cut-and-paste the content. Don’t forget to make sure that the tab’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 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 (change the tabs gets old very quickly and anything to speed it up helps)

2) Get rid of Excerpts

I couldn’t get them to work and eventually created a sub page (

3) Save and reopen in the editor

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 code within a table.

4) Make sure all changes are saved
5) Open in the Editor and convert
6) Final tidy

  • Make sure that the tables do not contain any monospace/code formatting. This used to be our standard for attribute and element names but the new editor does not allow code format to coexist with hyperlinks (because, you know, that might be useful). Equally the conversion is uneven; sometimes code comes out as monospace, but sometimes in a code macro. Finally 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 page when in edit-mode.

  • You may need to replace Jira links. The macro 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.
    Whether tables wrap correctly is a function of whether the LHS pull across (the sort of tree-of-contents view) is visible or not. I tend to have this visible, but if a table renders ok with it hidden I leave it (I think this is also related to the full width thing I mentioned above)

  • Repeat the previous bullet until done.

Other notes

  • No labels