Feature Ideas

Allow users to connect their Atlassian workspace and use content from tools like Confluence and Jira as resources for generating documentation. This would make it easier to reuse existing internal knowledge, specifications, and project information without manually copying content. By using Atlassian content as a resource, users could keep their documentation aligned with their current workflows and tools.

While documentation is being generated, there is no indication of progress or remaining work, increasing perceived latency.

add the Previous/Back and Next/Front buttons add option to add emojis copying the content, doesn't retain the style and when pasted somewhere else in the doc - pastes without formatting

When navigating the generation wizard, the interface appears dense and progression through steps is not immediately clear.

When issues or ideas are encountered, there is no clear in-product way to submit feedback or report bugs.

When evaluating long-term adoption, there is no visibility into product direction or planned improvements, reducing confidence in continued development.

When questions arise, there is no central in-product location explaining workflows, features, or best practices.

When exploring features for the first time, there is no guided explanation of actions or expected outcomes, increasing friction and uncertainty.

When accessing the product for the first time, the flow does not clearly communicate what to do next or how steps relate to each other, especially for non-technical users.

When multiple resources are provided, all sources are treated equally, causing important documents to lose influence in the final output.

When content generation starts, the document structure is fixed and cannot be reviewed or adjusted beforehand, making corrections costly after generation.

When generation is triggered, the AI proceeds without understanding the intended structure, audience, or purpose. This results in outputs that do not consistently align with user expectations.

When PDFs, websites, and individual files are combined, the generated documentation shows fragmented structure and inconsistent flow. Content may repeat, jump between topics, or miss logical connections.

When documentation generation is started, the process takes a very long time to complete. There is little feedback during execution, making it unclear whether progress is being made. This creates friction and slows down iteration.

Introduce an alternative documentation layout designed for internal knowledge exploration. This experience would integrate documentation with connected content sources, allowing users to browse files, documents, and resources directly within the interface. In addition, users could ask AI-powered questions across all available content and receive contextual answers based on documentation and connected resources. This layout would focus on discovery, search, and knowledge access, offering a different experience from the current public documentation layout with a traditional sidebar. This approach would be ideal for teams looking to centralize internal knowledge and interact with it in a more dynamic way.