Mapping requirements to Confluence
As we design Capable Images for Confluence, we're carefully evaluating how to integrate a seamless, scalable image management solution into Confluence using the Forge framework. Here's an outline of the architectural possibilities we've considered and why we've chosen certain approaches to best meet our goals.
- Image Storage as Attachments on Custom Content: We explored several storage options for images, but using Confluence's "custom content" with attachments offers a compelling solution. This setup allows us to create custom content types that function similarly to Confluence pages but are specifically tailored to store and manage images. By treating each image as an attachment against a custom content type, we can maintain the flexibility of standard pages while organizing images centrally and logically within the Confluence space. This also enables us to use the Confluence Index to provide search capability to the feature.
- Macro-Based Image Insertion: To maintain a smooth, non-disruptive workflow, we decided to consider a macro-based approach for image insertion. This lets users place images directly into Confluence pages from our image library without taking them out of the content flow or requiring manual uploads each time.
- Project and Global Pages for Management Interface: When thinking about the image management interface, we considered several access points. A combination of project-level and global pages for image organization seems ideal, as this approach offers a familiar Confluence-like experience while allowing users to find and manage images from a single interface. By making the library accessible at both project and global levels, we give teams flexibility in organizing assets by project or sharing them across the organization.
- Permissions via Space Permissions: Managing access and security was another essential factor. After exploring different ways to handle permissions, we determined that aligning our solution with Confluence's space permissions would best meet security needs without adding complexity. This approach ensures that image access naturally follows Confluence's established role-based permissions, keeping assets secure while simplifying permission management.
In summary, we chose these architectural approaches to ensure Capable Images for Confluence feels native to Confluence, leverages Forge's strengths, and seamlessly integrates with users' workflows. This approach should allow us to deliver a feature-rich image management tool that's easy for teams to adopt and use.
Log in or sign up for Devpost to join the conversation.