Can feature 'XYZ' be added to WikiTraccs?
It depends.
Adding XYZ to WikiTraccs vs. project-specific solutions
The development of WikiTraccs is mostly driven by customer demand. That, and changes by Microsoft and Atlassian to their services.
Every environment and migration project is different, but there are similar challenges. If customers (or I) face the same challenge over and over again, it’s usually time to think about extending WikiTraccs to support the underlying use cases.
New WikiTraccs feature?
I’m open to extending WikiTraccs if the new feature helps with an often-faced challenge that is not isolated to a specific migration project.
New WikiTraccs features must:
- ✅ work in a standard SharePoint Online environment, without having to install third-party apps
- ✅ solve a challenge for multiple clients
- ✅ have a technical solution
- ✅ take reasonable time to implement
If some of those boxes cannot be checked then the solution is usually project-specific, although we should definitely talk this through.
Project-specific solution?
Project-specific solutions solve challenges for a specific migration project or a specific environment.
Modifying the page header to comply with CI/CD? Turn off the comments section on pages? Add page metadata for HR? Those are unique requirements within a project.
Project-specific solutions usually involve a combination of configuration (search configuration, content types, managed metadata), low-code solutions (Power Automate workflows), and scripting (PowerShell, JavaScript).
Missing feature XYZ is a blocker for me - can you add it to WikiTraccs?
I’d like to learn more. Does the feature check all of above boxes? That’s a good start.
The less time it takes to implement a feature, the more likely it is that I’ll add it for you. The more time it takes, the more useful it has to be in a broader sense.
I consider anything below ~2 days of end-to-end development effort as relatively low effort. Adding transformations for yet-unknown but simple-to-handle macros fall into that category. Or adjustments to text placeholders.
Note that I cannot give a guarantee that or when a feature will be added.
That being said - I’m always open for feature proposals as this is the way for me to learn about real-world challenges.
If we haven’t been already in touch via a demo or email or GitHub, please get in touch!
Help me help you
When looking at your challenge, I need to understand it first. Please help me with that.
Screenshots help illustrate your case
Screenshots are a good way to start diagnosing migration results.
Something looks unexpected after migrating pages to SharePoint? Take a screenshot of the source Confluence page and a screenshot of the migrated page in SharePoint. Highlight your expectations in the screenshots and write some lines about what you expect.
Create the expected outcome manually in SharePoint
Help me see the SharePoint page as you envision it to look after the migration.
Create a new modern SharePoint page and edit it. Manually add all the necessary elements to make it resemble the source Confluence page as closely as possible. Use only out-of-the-box SharePoint web parts - no PnP, no third-party tools (I nevertheless like to hear about those as well! Maybe it’s the exception to the rule).
Send me a screenshot of both the source Confluence page and target SharePoint page.
This ensures that it is technically possible to achieve what you’d like to see on the SharePoint side and serves as a mockup for me to understand your requirements.
Furthermore, It would help a great deal if you could send me the SharePoint storage format of the page. Here’s how to get that: Get the SharePoint Storage Format
Send me the Confluence page’s storage format XML
There is a Confluence page that contains something that you’d like to see migrated differently? Like a macro that ends up being a placeholder in SharePoint?
Send me a screenshot of the Confluence page.
I also need to see the page how WikiTraccs sees it to estimate how much effort it takes to support new transformations.
Send me the storage format XML. Here’s how to get that: Get the Confluence Storage Format.
The storage format XML contains a page’s text content, structure, formatting, and most importantly information about all macros, including their parameters.
Closing note
Please review the existing feature proposals in the GitHub issue list and vote for those you’d like to see gain traction. Alternatively, you can create a new feature proposal or start a discussion.