-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
5
-
1
-
I would really like to be able to maintain documents in Stash formatted with Confluence wiki markup, and then embed those documents in Confluence pages. Since we can't edit the markup directly in newer Confluence releases, this would be a great way to make such editing available. (I'd rather do my editing locally, anyway.)
Thanks.
- is related to
-
- Closed
[BSERV-2634] Stash-Confluence integration with wiki markup import
Brad Beyenhof
added a comment - I was thinking mostly of notes, but it would be awesome if I could use this method to continue writing documentation in wiki markup.
I actually wasn't thinking of pushing from Stash to Confluence, though; I was thinking more like including macro code on a Confluence page that causes it to go out to Stash and find data to render into page contents (similar to the live-updating JIRA issue status macro). It seems like it would be easier to specify on the Confluence end where to grab content than to try to tell Stash where to push something.
Brad Beyenhof
added a comment - I was thinking mostly of notes, but it would be awesome if I could use this method to continue writing documentation in wiki markup.
I actually wasn't thinking of pushing from Stash to Confluence, though; I was thinking more like including macro code on a Confluence page that causes it to go out to Stash and find data to render into page contents (similar to the live-updating JIRA issue status macro). It seems like it would be easier to specify on the Confluence end where to grab content than to try to tell Stash where to push something. Hi Brad,
Thanks for the feedback. Confluence still supports wiki markup as a way to input content into pages, meaning a conversion from markup into XML. However, conversion from XML into markup is not supported.
This means that you should be able to maintain your pages in Stash and push them into Confluence via the remote API. Unfortunately we currently don't have any automated way of doing this though.
Are they mostly notes that you are looking to maintain via Stash or any other type of documentation?
Brad Beyenhof
added a comment - Hi, Jens.
We don't really have a use case; it was really more of a 'wouldn't it be cool if...' from the get-go. It came about because I was keeping all of my notes from this year's Atlassian Summit in a local git repository, and I was formatting them in wiki markup because it's what I know and was using for all of my documentation at the time (in Confluence 3.5.9).
After I got home from San Francisco, I pushed my local notes repository up to Stash; also, I manually copied those wiki-markup text files into Confluence pages. I found myself making a few edits as time went on, and each time I had to re-copy the changes to my Confluence pages. It would have been cool if Confluence could have read those files from the HEAD of the master branch and automatically rendered the latest wiki markup from the repository (like php or config-file 'includes') rather than my clumsy manual synchronization method.
However, we have since upgraded to Confluence 4.3, and the wiki markup syntax is now unavailable, so I don't see how that would work anymore. We've installed the Confluence Source Editor plugin, so we can expose the raw XML, but I really dislike coding in XML and I'm unlikely to use that format for documentation in local git repositories.
If, somehow, pushing raw text content into Stash like this could bring back the capacity to write documentation in wiki markup, I'd be ecstatic! But I'm not really interested if the C4 upgrade means the backend page source would require me to keep the documentation repo in XML.
Brad Beyenhof
added a comment - Hi, Jens.
We don't really have a use case; it was really more of a 'wouldn't it be cool if...' from the get-go. It came about because I was keeping all of my notes from this year's Atlassian Summit in a local git repository, and I was formatting them in wiki markup because it's what I know and was using for all of my documentation at the time (in Confluence 3.5.9).
After I got home from San Francisco, I pushed my local notes repository up to Stash; also, I manually copied those wiki-markup text files into Confluence pages. I found myself making a few edits as time went on, and each time I had to re-copy the changes to my Confluence pages. It would have been cool if Confluence could have read those files from the HEAD of the master branch and automatically rendered the latest wiki markup from the repository (like php or config-file 'includes') rather than my clumsy manual synchronization method.
However, we have since upgraded to Confluence 4.3, and the wiki markup syntax is now unavailable, so I don't see how that would work anymore. We've installed the Confluence Source Editor plugin, so we can expose the raw XML, but I really dislike coding in XML and I'm unlikely to use that format for documentation in local git repositories.
If, somehow, pushing raw text content into Stash like this could bring back the capacity to write documentation in wiki markup, I'd be ecstatic! But I'm not really interested if the C4 upgrade means the backend page source would require me to keep the documentation repo in XML. Thanks for the update Brad. I would love to talk to you about your use-case for wiki markup. What type of documentation are you writing and what are the requirements that Confluence doesn't cater for anymore?
Brad Beyenhof
added a comment - Well, since we're now on Confluence 4.3.2, and wiki markup isn't even supported anymore, I suppose this ticket is dead now. Please close.
Brad Beyenhof
added a comment - Well, since we're now on Confluence 4.3.2, and wiki markup isn't even supported anymore, I suppose this ticket is dead now. Please close. 
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Bitbucket Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues.
Kind regards,
Bitbucket Data Center