Python/jinja template rendering and Confluence API

[Nahi]

I'm working with the Confluence API using Python. Here's my workflow:

1. Fetch the content of a page using get_page_by_id().
2. Transform the content.
3. Present the transformed content to the user via a web app using Jinja for them to approve or disapprove.

I'd like the content displayed in the web app to match the style it will have when uploaded back to Confluence. The challenge I'm facing is in rendering the content in the HTML template to ensure it looks consistent with the Confluence style.

When the user approves the content, I will be uploading it back to Confluence using the Python API. It's important that what the user views in the web app mostly matches what they will see in their Confluence space.

How can I render the transformed content in my web app to match the Confluence style, ensuring consistency between the preview and the uploaded content?

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Your python code will need to replicate all the stuff Confluence does to render its pages - this is quite a lot of coding for you to do.

I would question the desire to do this as well.  Why are your users not approving the pages in Confluence directly?  What's the point in using yet another application to doit? Why are you not just using something like Comala workflows?

[Nahi]

thanks for replying!

We're creating a page programmatically, we then want to present this to the user and ask if they approve or reject of the created page.

We want the user to have an accurate representation of how the page will actually look in confluence.

Any ideas will help