27 posts tagged with "faq"

FAQ pages are one of the most visited sections of any documentation site. In Confluence, they serve a specific purpose: giving your team or customers quick answers to the questions they ask most often, without making them read through pages of documentation. A well-structured FAQ page reduces repetitive questions in Slack channels, shortens onboarding time for new team members, and deflects support tickets before they are created.

But Confluence does not have a built-in FAQ feature. Teams typically resort to manual workarounds — tables, toggle macros, or expand sections — that look cluttered and are hard to maintain. This guide shows you three methods to create professional FAQ pages in Confluence, from a quick manual setup to a fully featured FAQ macro.

Confluence is great for documentation, but it has no built-in FAQ macro or Q&A tool. If you need FAQ pages, knowledge bases, or community-style Q&A in Confluence, NGPILOT offers two purpose-built apps.

Dark mode has moved from a developer preference to an expectation across every tool in the modern workspace. Confluence Cloud introduced a native dark mode toggle, which is a welcome step, but the reality of implementing a fully dark-themed Confluence experience is more nuanced than flipping a single switch.

Confluence's built-in editor is strictly WYSIWYG — there is no native Markdown editor. For teams who already write in Markdown (README files, docs repos, pull request descriptions), that means manually reformatting every doc through toolbar buttons, losing time and introducing inconsistencies. Enhanced Markdown for Confluence solves this by embedding a full Markdown editor with live split preview directly inside Confluence — and it renders Mermaid diagrams, KaTeX/LaTeX math, and 190+ code-highlighted languages, all in one macro.

This FAQ answers the questions teams ask most often about writing Markdown in Confluence.

Sequence diagrams are one of the most widely used diagram types in software documentation. They show exactly how participants -- users, services, databases, external APIs -- exchange messages over time. For Confluence teams, embedding sequence diagrams directly on wiki pages means architecture docs, API specifications, and incident post-mortems stay in one place instead of scattered across external tools.

Mermaid's text-based syntax makes sequence diagrams fast to write and easy to update, but the syntax has its own set of rules that can trip you up. This FAQ answers the questions Confluence users ask most often about building sequence diagrams with Mermaid, with expanded explanations, working code examples, and copy-paste templates you can drop straight into a Mermaid Plus macro.

Page navigation is one of those things that nobody notices when it works well and everyone complains about when it does not. In Confluence, where pages routinely grow to thousands of words — technical specifications, onboarding guides, compliance documentation, project charters — helping readers find the right section quickly is not a nice-to-have. It is the difference between a knowledge base that people use and one that people ignore.

Confluence pages are powerful containers for knowledge, documentation, and team collaboration. But when it comes to displaying visual content -- product screenshots, event photos, marketing banners, or process walkthroughs -- the standard page layout falls short. Images stacked vertically create long, scroll-heavy pages that are difficult to scan, and Confluence's built-in gallery macro only offers a static thumbnail grid with no interactive slideshow behavior.

Widget Carousel for Confluence solves this by adding a fully interactive image carousel macro that you can embed on any Confluence page. You select images from page attachments or upload new ones directly, then display them in a customizable slider with configurable width options. The result is a polished, professional-looking carousel that transforms how visual content is presented in your Confluence workspace.

This FAQ covers the most common questions teams have about Widget Carousel for Confluence -- from basic setup and content types to advanced configuration, responsive design, and how it compares to Confluence's native gallery macro. Whether you are building a company dashboard, a project landing page, or a team portal, this guide will help you get the most out of the carousel.

When teams need to add diagrams to Confluence, two tools come up again and again: Excalidraw and draw.io (also known as diagrams.net). Both are popular Confluence diagram apps on the Atlassian Marketplace, but they take fundamentally different approaches to visual communication — and picking the wrong one wastes time and licensing budget.

The short version: for live whiteboarding, brainstorming, and freeform sketching, Excalidraw wins. For formal, finalized diagrams (UML, network topology, BPMN), draw.io is the better fit. Most teams end up needing both — and the rest of this post is the honest, feature-by-feature comparison so you can make the right call for your workflow.

Graphviz has been the backbone of automated graph visualization for over three decades. Originally developed at AT&T Labs, it powers dependency graphs in build systems, call graphs in profilers, and database schemas in ORMs -- anywhere that diagrams need to be generated from structured data rather than drawn by hand. Graphviz Charts for Confluence brings that same engine directly into your Confluence pages, letting you write DOT language descriptions and get polished, auto-laid-out diagrams without leaving your wiki.

Mermaid supports 30 diagram types — from flowcharts and sequence diagrams to C4 architecture, swimlanes, Gantt charts, ER diagrams, git graphs, and more. With Mermaid Plus Diagrams & AI Agent for Confluence, all 30 render from plain text inside a single macro. This page is the complete reference: every type, its keyword, its category, when to use it, and worked examples for the ones a software team reaches for most.

If you are deciding which diagram type fits your use case, jump to When to use each Mermaid diagram type. For the quick reference table, see below. For installation and the macro basics, see Create Mermaid diagrams in Confluence.

Mermaid is the most popular text-based diagramming language for technical documentation. One line of code generates a flowchart. A few more produce a sequence diagram, ER diagram, or Gantt chart. Teams using Confluence can embed Mermaid diagrams directly on their pages, keeping diagrams alongside the documentation they illustrate.

FAQ sections are one of the most practical elements you can add to a Confluence page. Whether you are documenting product details, building an IT help desk resource, or writing an onboarding guide, a well-structured FAQ section lets readers find answers without scrolling through walls of text or pinging someone on Slack.

The problem is that Confluence does not give you a built-in way to create FAQ sections. Teams typically resort to manual workarounds: bullet lists, tables, or toggles built from expand macros. These methods work, sort of, but they are tedious to maintain, hard to reorder, and look inconsistent from page to page.

Modern FAQ for Confluence solves this by giving you a dedicated macro for building FAQ sections with drag-and-drop reordering, WYSIWYG editing, and two display themes. This guide walks through the entire process, provides ready-to-use templates, and shares best practices so your FAQ pages actually help people find what they need.

Managing a Jira instance at scale means sooner or later you will need to act on dozens, hundreds, or even thousands of issues at once. Whether you are migrating projects, cleaning up stale tickets, bulk-downloading attachments for an audit, or exporting an entire backlog for offline analysis, doing it one issue at a time is not realistic. Bulk operations let teams apply the same change across many issues simultaneously, saving hours of repetitive manual work and reducing the risk of inconsistency that comes with editing tickets individually.

However, bulk operations carry real risk. A single misconfigured bulk edit can change the status, assignee, or custom field value of hundreds of issues in seconds, and Jira does not offer a one-click undo. That is why understanding the right tools, permissions, safeguards, and workflows is critical before you run any bulk job. This FAQ covers the most common questions teams ask when planning and executing bulk operations in Jira, from safety and rollback strategies to performance tuning and permission requirements.

Confluence has been the go-to knowledge base and documentation platform for thousands of organizations. At its core, Confluence uses a WYSIWYG (What You See Is What You Get) editor that lets users format content visually -- clicking toolbar buttons for headings, bold text, tables, and macros without writing a single line of markup.

But an increasing number of teams are asking a different question: can we write Confluence content in Markdown instead?

Markdown is a lightweight plain-text formatting syntax originally created by John Gruber in 2004. It has become the default writing format for developers, technical writers, and content teams who work with Git repositories, static site generators, and API documentation. Its appeal is simple: you focus on structure and meaning rather than visual styling, and the formatted output is generated automatically.

Teams choose Markdown over WYSIWYG for several compelling reasons. Developer-heavy teams often already write in Markdown daily -- in README files, pull request descriptions, and documentation repos. Switching to a WYSIWYG editor for Confluence pages feels like a step backward. Markdown content is also plain text, which means it works seamlessly with version control systems like Git, diff tools, and automated pipelines. Finally, Markdown files are portable; the same .md file can be published to GitHub, a static site, or a Confluence page without reformatting.

On the other hand, WYSIWYG editing remains the better choice for non-technical users who prefer visual feedback, drag-and-drop file attachments, and toolbar-driven formatting. Many business teams have no interest in learning syntax rules, no matter how lightweight.

This FAQ addresses the most common questions teams have when evaluating Markdown versus WYSIWYG editing in Confluence, and explains how Enhanced Markdown for Confluence by NGPILOT bridges the gap between both worlds.

Exporting Jira issues sounds simple until you try it at scale. Jira's native CSV export works for small result sets, but teams quickly hit field mismatches, encoding errors, custom field headaches, timeouts on large projects, and the question of what to do with attachments. This FAQ walks through each common problem and the practical fix — most of which Simple Bulk Issues Excel CSV Export for Jira handles out of the box.

Teams need two types of knowledge sharing in Confluence: structured FAQ sections for pages, and community Q&A forums for ongoing discussion. Confluence has no built-in solution for either.

We built two apps to cover both needs — Modern FAQ for Confluence for polished, drag-and-drop FAQ sections, and Modern Questions for Confluence for structured Q&A with voting and accepted answers. In this post we compare both against the alternatives on the Atlassian Marketplace.