Automation modules
Bitbucket modules
Common modules
Compass modules
Confluence modules
Jira modules
Jira Service Management modules
Rovo modules
Last updated Jul 1, 2025

Confluence full page (EAP)

Confluence full page apps are now available through Forge's Early Access Program (EAP). View the announcement for more information. You can sign up here start testing this feature.

EAPs are offered to selected users for testing and feedback purposes. APIs and features under EAP are unsupported and subject to change without notice. APIs and features under EAP are not recommended for use in production environments.

For more details, see Forge EAP, Preview, and GA.

The confluence:fullPage module lets you to create fully customised app experiences within Confluence Cloud. Full page apps occupy the entire web page, providing ample space to deliver UI for a broader range of use cases, such as specialised content views or internal tools that reflect your own branding.

Full page apps can be accessed from the browser address bar in the format: /full-page/:appId/:forgeEnvId.

EAP limitations

To deploy apps containing confluence:fullPage modules during this EAP, you can utilise the --no-verify option with the Forge CLI deploy command to avoid manifest validation errors.

Many features exposed by the Forge bridge SDKs have not been made available during the EAP. Review the linked announcement and share your feedback on features you’d like to see in future releases. Your input will help us prioritise features that matter most to you.

Manifest structure

1
2
modules []
└─ confluence:fullPage {}
   ├─ key (string) [Mandatory]
   ├─ resource (string) [Mandatory]
   ├─ render (string) [Optional]
   └─ resolver {} [Optional]

resources []
├─ key (string) [Mandatory]
└─ path (string) [Mandatory]

Properties

PropertyTypeRequiredDescription
key

string

Yes

A key for the module, which other modules can refer to. Must be unique within the manifest.

Regex: ^[a-zA-Z0-9_-]+$

resourcestringIf using Custom UI or modern versions of UI KitThe key of a static resources entry that your module will display. See resources for more details.
render'native'If using modern versions of UI KitIndicates the module uses UI Kit.
functionstringDeprecated Required if using UI Kit 1The key of a function module that returns a UI Kit 1 component.
resolver{ function: string } or
{ endpoint: string }

Set the function property if you are using a hosted function module for your resolver.

Set the endpoint property if you are using Forge Remote to integrate with a remote back end.

i18n object

KeyTypeRequiredDescription
i18nstringYesA key referencing a translated string in the translation files. For more details, see Translations.

Extension context

UI Kit and Custom UI

Use the useProductContext hook to access the extension context in UI Kit or getContext bridge method in custom UI.

PropertyTypeDescription
typestringThe type of the module.
locationstringThe full URL of the host page where this module is displayed.

Example

This example shows you how to create a simple UI kit app that spans the entire page.

Manifest

1
2
modules:
  confluence:fullPage:
    - key: hello-full-page-app
      resource: main

Full page app

1
2
import React, { useState } from "react";
import ForgeReconciler, { Box, Text, xcss } from "@forge/react";

const boxStyle = xcss({
  backgroundColor: "color.background.accent.yellow.subtle",
});

const App = () => {
  return (
    <Box xcss={boxStyle}>
      <Text>My full page app!</Text>
    </Box>
  );
};

ForgeReconciler.render(
  <React.StrictMode>
    <App />
  </React.StrictMode>
);

Rate this page: