I was about 60% done developing a software user guide with the old page editing tools. The new editing experience is nice but removes some of the options I was using to layout page content such as 60/40 split 2 column layouts that filled the whole page width. The new experience updates have centered the page title and it no longer looks right. If I select the the centered fixed-width column that resembles the new centered column of text on the new page layout, the PDF export cuts off the first few letters of all my pages. I did a test by creating a new blank page with the new editing experience and pasted in the content from an older page and the export worked correctly. I'm trying to avoid having to redo all 380+ pages of my user guide with this same method. Is there an easier way to convert all my current pages over to the new page style?
Welcome to Community; it's nice to meet you!
As far as I am aware, that's the only way to convert individual pages, but the Cloud team might have a better way. This process is always changing, so I would recommend that you reach out to them directly:
That way, you can provide your Cloud URL to them, and they can let you know if it's possible to change all of your pages over.
Maybe I missed the relevant section in Mike's question – but what is the way to convert existing pages to the new editing experience? I don't see any option anywhere.
I don't have so much content to convert as him, but I'd still like to actually convert the pages (instead of recreating them), just to keep the history.
Thanks a lot!
@Mike_Standal and @[deleted],
I am so sorry that I neglected to answer that question.
Per the feature request, CONFCLOUD-65768 (Convert pages and templates to new editing experience):
You can opt-in your instance to have all your pages migrated to the new editor by contacting Cloud Support. This means every existing page, including templates, will be migrated as you edit the page.
We're working to offer in the future an option to migrate each page proactively without having to opt-in your entire instance.
Any templates that we can migrate will convert to the new editor, but if a template has content that isn't supported in the new editor it will remain in the old editor unless you remove the content that is unsupported (i.e. a table nested inside a table for example).
This is direct from our Product Manager himself.
I hope that helps! Let us know if you have any questions.
- Create your own custom emoji 🔥 - "Shake for Feedback" on mobile 📱 - An endless supply of GIFs via GIPHY 🤩 Is there anything quite as nice as a pleasant surprise? Comment below with what...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events