Here’s your Devpost project submission, adapted from your blog post and formatted into the standard Devpost sections:
Postman Doc: Revived for the Forge Quest Hackathon
Inspiration
Forge Quest by Atlassian was exactly the nudge I needed to revive one of my old-but-loved Forge apps. My app, Postman Doc, had been sitting untouched on the Atlassian Marketplace, flagged as deprecated due to outdated Forge APIs and UI components. Life got in the way, and Forge evolved rapidly—but Forge Quest brought the spark back and gave me a reason to modernize.
What it does
Postman Doc helps teams embed Postman’s public API documentation directly into Confluence pages. This eliminates the need for constant back-and-forth between developers, product managers, and API consumers. Users simply paste a Postman public link, and the app fetches and displays live API documentation—styled to match Confluence.
During the hackathon, I updated it with:
- Support for UI Kit 1 for a more consistent and accessible UX.
- Searchable Postman collections inside Confluence.
- Smart error handling via
ModalDialog. - Improved responsiveness and layout fixes for different screen sizes.
How we built it
The app was originally built with Forge and Confluence’s earlier APIs. For the hackathon, I:
- Migrated the UI to Forge UI Kit 1, leveraging components like
Form,TextField,DynamicTable, andModalDialog. - Used Forge’s backend functions to fetch and parse Postman public doc JSON.
- Implemented search within collections and added error states using
ModalDialog. - Polished the UX with a modern, native-Atlassian feel.
Challenges we ran into
- Understanding the nuances of UI Kit 1, especially compared to older Forge APIs and custom rendering approaches.
- Adapting the app to work smoothly within Confluence’s various screen sizes and layouts.
- Ensuring that Postman doc parsing and rendering remained reliable across different types of Postman public URLs.
Accomplishments that we're proud of
- Successfully revived a deprecated Marketplace app and made it relevant again.
- Shipped a fully updated version with modern Forge standards.
- Simplified the UX with native Atlassian components while retaining functionality.
- Brought a smoother, more intuitive experience to Confluence users interacting with APIs.
What we learned
- UI Kit 1 is much more powerful and accessible than I had assumed.
- Migrating old Forge apps isn't just possible—it can be quite straightforward with the right components.
- Community hackathons like Forge Quest are amazing motivators to revisit old projects and level them up.
- Thoughtful UI and clean architecture go a long way in making Forge apps easier to maintain.
What's next for Postman Doc
- Add support for private Postman collections using API keys or OAuth.
- Enable inline editing of docs or annotation inside Confluence pages.
- Improve customization—let teams choose how much detail from the collection they want to show.
- Explore Jira integration for linking APIs directly to tasks or epics.
🔗 Try the app on the Atlassian Marketplace 🚀 Learn more about Forge 🎯 Hackathon: Forge Quest
Log in or sign up for Devpost to join the conversation.