RFC-63: Page Extension in Editor, Design changes and more

General Request for Comments (RFC)
, ,
51

Closure statement

What did we hear?

  • There were concerns about the potential loss of dynamic byline items, as many apps rely on this feature to display crucial information at a glance.
  • Many expressed that hiding apps in the byline and consolidating app extension points into the sidebar and byline might reduce discoverability and negatively impact user experience.
  • Additionally, concerns were raised about the deprecation of key extension points like atl.footer and atl.page.metadata.banner, which are critical for some apps.

What did we change?

In response to the feedback, we made the following adjustments:

Byline improvements:

  1. We revised the experience to display up to 4 apps by default in the byline by default and increased the text size for improved visibility. If a page contains more than 4 apps, the additional apps will be hidden in an overflow menu that users can open to display all byline apps. Based on current and projected app installations, we anticipate that this change will not cause any major issues but will monitor user feedback.

  2. Apps can have dynamic names (up to 25 characters) and dynamic icons, which addresses the need for displaying real-time information. If the app display name is longer than 25 characters, it will be truncated.

  3. Visibility control: The ability for admins or users to control app visibility and order in the byline is being considered for future implementation, although it’s currently outside the scope of this RFC.

What is coming next?

  1. atl.metadata.banner
    Based on design requirements, we believe the byline location will serve as a suitable replacement.

  2. atl.footer
    After considering your input, we’ve decided to retain the atl.footer location but will remove the UI component, allowing it to be used for running background scripts only and not displaying content to Confluence users.

  3. Deprecation: We are still considering the deprecation of:

    1. page.metadata.banner
    2. atl.page.metadata.banner
    3. system.content.button
    4. atl.editor.savebar
    5. system.editor.precursor.buttons

  4. NB: Deprecation notices will be sent out shortly

We are also exploring adding new locations and alternative design solutions, which will be introduced in a future RFC.

Timelines - next steps:

  1. The extension point changes in this RFC will be tested with the Live Pages Early Access Program (EAP) at the end of October 2024.

  2. Later in December, we will offer an optional open beta for existing customers, allowing them to opt-in to the new experience. This will bring the changes outlined in this RFC to both the editor and renderer, creating design parity across both.

  3. Further updates will be shared as we approach the planned rollout for April 2025. Keep an eye out for upcoming discussions.

Thank you for your feedback and collaboration on this RFC. Your input has been invaluable in shaping our approach. We appreciate your support!