This article contains information about each macro available in the app.
You can pull Markdown from other applications like GitHub, Bitbucket, or GitLab, or, from a URL, or directly in the macro body. The list of macros and how to add one to a page are as shown in the image:
Select any of the links to learn more:
Markdown
Add the Markdown macro to the required Confluence page.
Then paste your content into the macro editor:
Or, you can paste the content directly in the macro on the page as shown:
Click Insert and publish the page.
Markdown from Github
Add the Markdown from Github macro to the required Confluence page.
Select the Github token from the list and enter the path of the Markdown file to be displayed in URL.
Administrators configure these tokens from the Markdown Extensions Configuration page.
Click Insert and publish the page.
Markdown from Bitbucket
Add the Markdown from Bitbucket macro to the required Confluence page.
Select the token in Bitbucket token and URL in the Enter URL tab. Click Check to check the connection.
Enter the required information in the Enter Repository Settings tab and click Insert.
Publish the page to view the accessed data.
The following table explains each parameter in the macro editor:
Parameter name | Description |
|---|---|
Enter URL tab | |
Bitbucket token | Specify the Bitbucket account to be accessed. Administrators configure these tokens from the Markdown Extensions Configuration page. This parameter is common to both the tabs. |
URL | Enter the full path to the required Markdown file. This is a mandatory field. If a URL is provided, the settings in the Enter Repository Settings tab can be skipped. Click Check to test the connection and accessibility. |
Enter Repository Settings tab | |
Username/Organization Name | Enter the username or organization name under which the repository is hosted. For example: This is a mandatory field. |
Repository | Specify the repository to be accessed. For example: This is a mandatory field. |
Branch or Commit Hash | Specify the branch from where the file is available. For example: This is a mandatory field. |
File Path | Enter the directory path where the file is hosted. For example: This is a mandatory field. |
Markdown from Gitlab
Add the Markdown from Gitlab macro to the required Confluence page.
Select the token in Gitlab token and URL in the Enter URL tab. Click Check to check the connection.
Enter the required information in the Enter Repository Settings tab and click Insert.
Publish the page to view the accessed data.
The following table explains each parameter in the macro editor:
Parameter name | Description |
|---|---|
Enter URL tab | |
Gitlab Token | Specify the GitLab account to be accessed. Administrators configure these tokens from the Markdown Extensions Configuration page. This parameter is common to both the tabs. |
URL | Enter the URL of the Markdown file to be displayed. The URL can be a link to either a regular or a raw file. If a URL is provided, the settings in the Enter Repository Settings tab can be skipped. For example: This is a mandatory field. |
Enter Repository Settings tab | |
Username/Organization Name | Enter the username or organization name under which the repository is hosted. For example: This is a mandatory field. |
Repository | Specify the repository name to be accessed. For example: This is a mandatory field. |
Branch or Commit Hash | Enter the branch name where the file is located. For example: This is a mandatory field. |
File Path | Enter the directory path where the file is hosted. For example: This is a mandatory field. |
Markdown from a URL
Add the Markdown from a URL macro to the required Confluence page. The macro is displayed as a sidebar in the right:
Add your URL to the URL parameter. The changes made to the editor are always saved automatically. Make sure your URL is pointing to raw Markdown!
Publish the page to see the content.