Sign up for Confluence Full Page module EAP

[VickyHu]

By signing up for this Early Access Program (“EAP”), you acknowledge that use of the Confluence Full Page App module is governed by the Atlassian Developer Terms. The Confluence Full Page App module is considered “Early Access Materials”, as set forth in Section 10 of the Atlassian Developer Terms and is subject to applicable terms, conditions, and disclaimers.

Summary of project:

The Confluence Full Page module aims to enable developers to build fully custom, chromeless app experiences within Confluence Cloud, hosted directly on Forge. This offering is a key step in Atlassian’s strategy to empower partners and customers to build sophisticated, enterprise-grade solutions directly on the Atlassian platform. This post explains our current solution including some high-level technical designs and guidelines. We’re looking for feedback to make sure we build the best possible solution. As we continue to develop this solution, the information outlined below may evolve over time.

To join this Early Access Program, please complete the Forge EAP sign-up form.

Who are we solving for?

Customers

This initiative is designed to support enterprise customers who require branded, full-screen solutions without Atlassian navigation or branding.

Partners

This initiative provides partners with more UI flexibility for their solution.

EAP solution overview

Forge Full-page apps for Confluence can be built by configuring a confluence:fullPage module in the App manifest.yml. Learn more here.

Viewing full-page apps

Right now, there is no easy way (like a button) to open a Confluence full page app. App builders must make the URL themselves to view or test their app. This is a temporary limitation for full page apps in Confluence.

Confluence full-page apps will have the following base URL structure:

https://<site-host-name>/wiki/full-page/<app-id>/<environment-id>

• site-host-name: the base URL of the Atlassian site with Confluence installed, e.g. my-org.atlassian.net
• app-id: The Forge app ID of the app in UUID format
• environment-id: The ID of the environment that the Forge app is deployed to in UUID format

Any subsequent URL segments are managed by the Forge app through the bridge createHistory API.

Known Limitations

1. Forge Modals have not been made available.
2. Many features exposed by the Forge bridge SDKs have not been made available. Feedback is welcomed regarding use cases for existing and new bridge capabilities.

Feedback

We welcome your thoughts on this EAP and, in particular, would greatly appreciate your feedback on the following questions:

1. What are the best use cases for the Full Page UI?
2. What additional types of components would add value to a full page experience for you?
3. What new and existing features of the Forge app SDKs would help you build your use case?

We look forward to your feedback!

[jens]

Hi @VickyHu,

thanks for the RFC, it’s great to see Atlassian is working on fullscreen mechanisms in Forge

In our connect apps we use fullscreen modals and - ignoring the first limitation for now - I was wondering how we would include product context such as spaces, pages, custom content entities in the URL / forge bridge context (view.getContext). Or is that an example for limitation #2?

Without such context I think we could use that module only for very generic views like a getting started page etc.

[shushen]

Hi @VickyHu,

This is exciting, thanks for sharing the EAP.

Would it be possible to make this full page module to be de-coupled with Confluence? A use case we’d like to see is in combination with Cross-Context apps, this full-page module would provide the UI entry point for our customers to work with both Jira and Confluence. Currently we have two separate apps listed on Marketplace, one for Jira and the other for Confluence, and we would very much like them to be combined and have a seamless cross-context experience for the customers.

Ideally:

• The URL would have no wiki component, e.g., https://<site-host-name>/full-page/<app-id>/<environment-id>
• The full-page module can be discovered/navigated from the “Customized application navigator” on the top menu of the site (i.e., where /wiki/admin/application-navigator allows admins to add new items, and in this case, enable/disable the full-page modules if they wish). This location appears to be a logical point of entry for cross-context apps:
  
  

Looking forward to seeing this EAP evolves!

Thanks,
Shu

[shushen]

On Forge bridge, we’d very much like to see the Data Loss Prevention (DLP) APIs being exposed as a (say) requestDLP in Forge bridge API.

This fits into our cross-context app use case, where the app would call the DLP APIs to configured Atlassian Guard settings that applies to both Jira and Confluence (e.g., classification levels). This feature request currently has an outstanding ECO work item: https://jira.atlassian.com/browse/ECO-953.