DEV Community: Frankie

Search Confluence or Jira with Raycast

Frankie — Thu, 15 Jan 2026 07:07:05 +0000

Preface

If you’ve used Alfred but haven’t tried Raycast yet, it’s worth a shot. The free plan is more than enough for day-to-day use (see Raycast vs Alfred).

Free users can’t use Raycast’s built-in data sync, but you can still sync via Raycast’s Export/Import Settings & Data plus iCloud Drive.

Background

At our company, we use Atlassian’s Confluence and Jira for our knowledge base and project management.

We frequently open Wiki and Jira pages to look things up. To find a specific article or issue, it often takes several steps: open the website, focus the search box, search, filter, and so on. A slightly faster way is to bookmark commonly used links, or create Raycast Quicklinks plus Aliases for quick access.

Quicklinks are great in some scenarios—for example, searching documentation with https://developer.mozilla.org/en-US/search?q={Query}, where {Query} is a dynamic parameter (i.e., what you want to search for). Any site that supports URL-based search parameters can use this approach—for instance, Google’s https://www.google.com/search?q={Query}.

However, this kind of search doesn’t work for internal company Wiki/Jira sites. Also, using Quicklinks for internal doc searching isn’t really ideal. Over time, the links you need to visit or save only keep growing—whether they’re browser bookmarks or Quicklinks.

That led to the idea of building a Raycast extension to support fast search (and a few simple actions) for Confluence and Jira. Conveniently, our self-hosted (Data Center) deployment also supports authentication via Personal Access Tokens, which is a secure way to integrate with external programs. Learn more

Before You Start

After installing Raycast, go to the Raycast Store and install the Atlassian Data Center (Self-Hosted) extension.

When you run commands from this extension, it will guide you through some initial setup. Prepare the following:

Confluence Base URL: e.g. https://confluence.example.com
Confluence PAT: go to your company’s Confluence site, then Profile (avatar) → Personal Access Tokens → Create token (keep the token safe; if it leaks, revoke it immediately)
Jira Base URL: https://jira.example.com
Jira PAT: create it the same way as Confluence

TIP: Since the fields above are required, if you only use one of them, you can just fill the other with any non-empty value.

Usage Guide

TIP: You can also set an Alias for each command based on your own habits for quicker access.

Currently, Atlassian Data Center provides the following commands:

Confluence
- Search Contents - Search pages (articles), blog posts, attachments, and comments; supports favoriting
- Search Spaces - Search spaces
- Search Users - Search users
Jira
- Search Issues - Search issues, and supports a few simple actions such as transitioning issue status and creating worklogs
- Board View - Boards, such as the current Active Sprint
- Worklog View - Your worklogs
- Notification View - Notifications (if there are “unread” messages, the Search Issues list will also show a hint)
- Manage Fields - Helps Search Issues display more information in search results

Each search panel includes many commonly used filters (usually more than enough for everyday use):

Search Contents
- All Contents
- Full Text Search - Expand the search scope from title ~ "xxx" to text ~ "xxx", instead of only searching titles
- Viewed Recently
- Updated Recently
- Created by Me
- Contributed by Me
- Mention Me
- My Favourites
- Watched by Me
Search Issues
- All Issues
- Full Text Search - Expand the search scope from summary ~ "xxx" to text ~ "xxx"
- Open Issues
- My Open Issues
- Assigned to Me
- Reported by Me
- Created Recently
- Updated Recently
- Resolved Recently
- Viewed Recently
- Watched by Me

As mentioned earlier, Quicklinks tend to grow endlessly over time. I think favoriting articles is a good alternative (the Action Panel provides quick Favorite/Unfavorite actions). When searching, just switch to the My Favourites option.

In addition, it also supports typing full CQL or JQL for customized advanced queries:

One more thing:

Since Jira allows custom fields—and there are many field types, and each Jira instance can differ a lot—the extension includes the Manage Fields command to help Search Issues show more information.

For example, search for Test Engineer on the Manage Fields screen and add it via “Add to Search”. Then the Search Issues list will display that field.

Screenshots

Because Raycast List has limited space, lots of additional information can only be hidden in tooltips. You can reveal it by moving the cursor over icons, titles, subtitles, timestamps, avatars, and so on.

▼ Confluence

▼ Jira

More screenshots

Others

Some Raycast extensions I personally use. They may not be for everyone—pick what you need:

Lark Documents - Search Lark docs
Cursor - Commonly used: Search Recent Projects
DeepWiki - Great for Q&A to quickly understand internal implementations of some libraries

Build a Personal Blog with VS Code + GitHub

Frankie — Sun, 22 Dec 2024 12:14:11 +0000

Candidate Options

There are plenty of choices, and the barrier to entry is low.

Existing platforms:

Juejin
Yuque
Zhihu
Jianshu
Cnblogs
WeChat Official Account
SegmentFault
Medium
...

Self-hosting:

WordPress
Hexo
GitBook
VuePress
dumi
...

How to Choose?

The motivations for writing a personal blog are usually something like:

Document pitfalls you’ve run into, tough problems you’ve solved, life, etc.
Build a knowledge base and influence
Summarize and refine, improving your writing and communication
Output content, share opinions, discuss, and iterate
...

What I want:

Edit and publish anytime, anywhere
Solid Markdown support, plus image hosting
No content review/censorship (especially obvious in China—for example, mentioning competitors or including certain URLs can easily lead to throttling or bans)
Good SEO (I still want what I write to be seen by more people)
Stay focused on creating content
...

If you’re in China, platforms like Juejin, Yuque, and Cnblogs might be better overall. Their user base is mostly programmers, which can lead to more discussion. Zhihu’s Markdown support is terrible. Jianshu’s content moderation is pretty unfriendly—I wrote on Jianshu for years, but later its moderation became so robotic that even tiny edits could get you banned. I eventually couldn’t take it anymore and left.

If you self-host, you need to think about SEO, image hosting, domain registration/filing, ops costs, and so on. If you choose a domestic platform, moderation is basically unavoidable—change a word and you may still have to wait for approval. 🙄

In short, every option has pros and cons—just pick what suits you.

My Choice

My blog: 种一棵树，最好的时间是十年前。其次，是现在。

Use GitHub Blogger as the editor for fast writing and publishing (a VS Code WebView extension)
Use GitHub + jsDelivr as the image host, with CDN acceleration
Use a GitHub Repository to archive posts; every edit is recorded
Use GitHub Issues as the post list
Use GitHub Labels to tag and categorize posts
Use Raycast Quicklinks to quickly search posts, e.g. search by title with https://github.com/tofrankie/blog/issues?q=in%3Atitle+{Query}+

GitHub Blogger

Inspired by Aaronphy/Blogger.

After leaving Jianshu, I thought about continuing on Juejin. But Juejin isn’t as good as it used to be, and it’s now full of clickbait and a lot of “anxiety marketing”. Later I found Aaronphy/Blogger, and finally had a place where I could just write in peace.

After using it for a while, I noticed some rough edges and a few bugs, and the author hadn’t updated it for a long time. So I forked and built on top of it—fixed some bugs, added new features—and that’s how GitHub Blogger was born.

For the original author’s design approach, see “在 VSCODE 中写博客吧”.

On top of the original, I made a few tweaks:

Tweak the UI theme
Adjust the Markdown theme to match GitHub
Support more Markdown formats, such as math formulas and diagrams
Support searching by title and multiple labels
Provide a search panel
Support opening posts on GitHub
Support post backups—every save gets recorded in your blog repository
Fix label-search pagination not working
Fix not being able to create labels when creating a post
Fix Labels only showing the first 20 items

In mid 2025, it got a full rewrite, and the whole UX now feels basically the same as GitHub itself. It looks like this 👇

If you happen to like it too, feel free to give it a try~ 👋

How to Use GitHub Blogger?

Since GitHub Blogger uses jsDelivr for image hosting internally—and jsDelivr does not support private repositories (more)—your blog repository must be public, otherwise images won’t display.

It’s simple:

Create a GitHub account (skip if you already have one)
Install VS Code, Cursor, or another editor (in theory, editors based on VSCodium should work)
Install the extension from VS Code Marketplace or Open VSX. You can also search for the GitHub Blogger extension inside the editor.
Prepare your GitHub Personal Access Token (classic) (needed for calling the GitHub API)
Open the command palette with Command + Shift + P or Ctrl + Shift + P:
1. Type Configure GitHub Blogger to finish the initial setup (you can select an existing public repository)
2. Type Open GitHub Blogger to open the editor, and you’re ready to go.

Extension configuration:

{
  "github-blogger.token": "xxx", // Your GitHub Personal Access Token
  "github-blogger.user": "xxx", // Your GitHub Username
  "github-blogger.repo": "xxx", // Your GitHub Repository Name
  "github-blogger.branch": "main" // Your GitHub Repository Branch Name
}

The branch defaults to main. It determines which branch your images and archived posts are committed to. A blog repository typically doesn’t have multiple branches like a real project, so you usually don’t need to change it—just keep it as the repo’s default branch.

You can pair it with github-issue-toc, which generates a table of contents on the right side of GitHub Issue pages.

GitHub Flavored Markdown (GFM) not only supports standard CommonMarkdown syntax, but also includes additional GitHub-specific features. See here for details.