The solution: I could enhance the CSOAP source code to get the required functionality: different user name and password on the target server. usernames and passwords were different.īecause there exists a SOAP based command line interface using Confluence's remote API which provides a copySpace functionality to the same instance or to a different instance but in its current revision it requires that one uses the same username and password on both source and target servers. but the biggest caveat was that the two instances of Confluence used different access mechanisms (one was using the corporate LDAP and the other an access list of its own) i.e. On the first glance not difficult (just transfer the raw wiki markup text), on second glance challenging when you think about attachments, comments etc. The task was to transfer a number of spaces from one instance to the other. Problem: I didn't have site admin rights on either instance so the natural XML export/import path was closed and I had to find another solution.Ĭontent in Confluence is organized in so called spaces, think of them as topics maintained by lists of users with varying degrees of permissions (admin, read, write, export aso.), each space consisting of a set of pages. Browse them by category on the Atlassian Plugin Exchange.Confluence is a professional enterprise wiki and recently I was tasked with transferring contents from one Confluence instance to another. There are hundreds of open-source and commercial plugins available for Confluence. The Gliffy and Balsamiq plugins are pre-installed with Confluence Hosted Evaluations.Ĭonfluence comes with a set of bundled plugins (macros) that you can use right away with the Macro Browser. You can reuse a whole bunch of Mockups that have been contributed by the community. Once you've completed your mockup, select Save and Close from the Mockup menu in the top-left of the Balsamiq editor.Use the Balsamiq Web-based editor to complete your mockup.Hover your cursor over the Add menu on any Confluence page.The mockups are then given to our 'Web Team' to implement. Our 'Marketing Team' use Balsamiq to create mockups of pages for our website in Confluence.The Balsamiq Mockup below eventuated in the new Image Browser that shipped in Confluence 3.1. Our 'Development Team' uses Balsamiq to mockup new features for our products.'Single-Click' Export - If you use this button (See the blue arrow), Scroll will automatically start exporting the Confluence page to a Word document using a default Word template or the settings you used in your previous session.Įver heard the saying 'a picture is worth a thousand words'? Using the Balsamiq Mockups Plugin you can create and visualise mockups of diagrams for proposed layouts of website content, new features, and much more, right within Confluence.These settings can be set as your default settings or they can be adjusted each time you want to export documentation (See the picture on the right). Export to Word - By clicking this button (See the red arrow), you will be able to customise your export settings.The Scroll Office plugin provides two options: Scroll Office uses Word files and their styling information as templates to output native Word 2007 documents having the desired look. Collaborate and author all your content in your wiki, and generate a properly formatted Word document to store, exchange and print information. Scroll Office makes it easy to apply your corporate style guidelines to your documentation that lives in the wiki. The Scroll Office Plugin integrates seamlessly with Confluence to provide an efficient and innovative way of exporting Confluence documentation into Microsoft Word. They then export the new release to PDF, HTML and XML, for those customers who prefer offline versions of the documentation.Then they unhide all the new pages and copy the content of the updated pages to the proper pages, then delete the copies. On release date, they rebrand the main documentation space to reflect the new release number.When release date is near, they copy the documentation space to create a snapshot of the current release as an archive using the Copy Space plugin.If they need to update existing pages, they create a hidden copy of the page and apply the updates to the copy. For new features, they create new pages with restricted permissions. Leading up to release date, they work with ‘hidden drafts’ in the documentation space.Here’s an overview of the process they follow: The Atlassian Tech Writers use spaces as as their version-control mechanism. The Copy Space plugin allows a space administrator to copy a space, including the pages within the space, but excluding (so far) page history, blog posts and email.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |