I was using @Thomas Scully successfully, but today when creating pages with properties as above

'metadata': { 'properties': { 'content-appearance-draft':
{ 'value': 'full-width' }
, 'content-appearance-published':
{ 'value': 'full-width' }
 

I'm getting an HTTP 400 (400 Client Error: Bad Request for url: xxx) error even though the page is successfully added with full width! Strange. So it appears the 400 error is being reported erroneously.

If I remove the properties above, everything works fine, but of course, the page is now narrow in width.

Any ideas?

Thanks a lot for sharing this Thomas!

For those wondering if full-width is possible through the API, it seems that it is possible through the properties endpoints (here) and when you create new content (here) though the documentation for the create content endpoint does not say so.  I found this post which suggests that it is possible through the create content endpoint (here).  I made this work in my side project and will put an example of the body I sent below (python code) in case anyone makes it here and is looking.  The "content-appearance-draft" and "content-appearance-published" are the properties that need to be set for the page width to appear full. 

body = {
  'space': {
    'key': confluence_space_key
  },
  'ancestors': [
    {
      'id': confluence_ancestor_page_id
    }
  ],
  'type': 'page',
  'title': confluence_page_name,
  'metadata': {
    'properties': {
      'content-appearance-draft': {
        'value': 'full-width'
      },
      'content-appearance-published': {
        'value': 'full-width'
      }
    }
  }
}

Choosing between editors ( not just styles ) is one of the strengths I brag about with Confluence to others.

I know from tracking this Confluence issue for 3 years, there is NOT agreement in the user community on what the "right, modern" editor should do clearly. 

There are ( as correctly advertised by Confluence ) some good new features in the new editor.

There are also some features in the old editor that are still far superior ( try adding 10 rows quickly in the older editor vs the new editor – the + sign to hover on at the row level is hopelessly inaccurate ).

The fact that I can use one or the other editor for a page is very good.

The fact that choosing the editor ( and a style ) are easy enough for the average user ( or admin ) to understand is an issue.

Sometimes we have simple sites and the admin will not allow users to choose an editor or a style. In other cases we may want to allow authors a choice of editors or styles to meet their needs.

Having that freedom to setup sites to fit a use case and the freedom to choose editors and styles to fit is a plus. Let's make it easier to do.

Same question.  I'd like to know if this is possible via the REST API.

Yes, same question as Lukas: how do I set the full-width view when creating a page via the Confluence Cloud REST API?

Is there any parameter for setting the wider view when creating a page via the Confluence Cloud REST API?

Is there any parameter for setting the wider view in the Confluence Cloud REST API?

Thank you for making this happen Avinoam.

Hi all,

Thanks for the quick feedback!

For more context on how Full Width works, what's changed, what's coming, and how to stay updated on the documentation around it (public roadmap) - please have a look at our recent Community post here: https://community.atlassian.com/t5/Confluence-discussions/Full-width-mode-is-now-available-for-the-new-editor-in/td-p/1138727#U1139686

Thanks,

Avinoam