Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
101 changes: 101 additions & 0 deletions apps/web/content-collections.ts
Original file line number Diff line number Diff line change
Expand Up @@ -401,6 +401,44 @@ const vs = defineCollection({
},
});

const shortcuts = defineCollection({
name: "shortcuts",
directory: "content/shortcuts",
include: "*.mdx",
exclude: "AGENTS.md",
schema: z.object({
title: z.string(),
description: z.string(),
category: z.string(),
prompt: z.string(),
}),
transform: async (document, context) => {
const mdx = await compileMDX(context, document, {
remarkPlugins: [remarkGfm, mdxMermaid],
rehypePlugins: [
rehypeSlug,
[
rehypeAutolinkHeadings,
{
behavior: "wrap",
properties: {
className: ["anchor"],
},
},
],
],
});

const slug = document._meta.path.replace(/\.mdx$/, "");

return {
...document,
mdx,
slug,
};
},
});

const roadmap = defineCollection({
name: "roadmap",
directory: "content/roadmap",
Expand Down Expand Up @@ -445,16 +483,79 @@ const roadmap = defineCollection({
},
});

const handbook = defineCollection({
name: "handbook",
directory: "content/handbook",
include: "**/*.mdx",
exclude: "AGENTS.md",
schema: z.object({
title: z.string(),
section: z.string(),
summary: z.string().optional(),
author: z.string().optional(),
created: z.string().optional(),
updated: z.string().optional(),
}),
transform: async (document, context) => {
const toc = extractToc(document.content);

const mdx = await compileMDX(context, document, {
remarkPlugins: [remarkGfm, mdxMermaid],
rehypePlugins: [
rehypeSlug,
[
rehypeAutolinkHeadings,
{
behavior: "wrap",
properties: {
className: ["anchor"],
},
},
],
],
});

const pathParts = document._meta.path.split("/");
const fileName = pathParts.pop()!.replace(/\.mdx$/, "");

const sectionFolder = pathParts[0] || "general";

const isIndex = fileName === "index";

const orderMatch = fileName.match(/^(\d+)\./);
const order = orderMatch ? parseInt(orderMatch[1], 10) : 999;

const cleanFileName = fileName.replace(/^\d+\./, "");
const cleanPath =
pathParts.length > 0
? `${pathParts.join("/")}/${cleanFileName}`
: cleanFileName;
const slug = cleanPath;

return {
...document,
mdx,
slug,
sectionFolder,
isIndex,
order,
toc,
};
},
});
Comment on lines +486 to +545
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion | 🟠 Major

Extract shared transform logic with docs collection.

The handbook transform (lines 499-544) duplicates nearly all the logic from the docs collection transform (lines 145-189). Both compute toc, pathParts, fileName, sectionFolder, isIndex, order, and slug identically.

Consider extracting the shared transform logic into a helper function:

+function createDocsLikeTransform() {
+  return async (document: any, context: any) => {
+    const toc = extractToc(document.content);
+
+    const mdx = await compileMDX(context, document, {
+      remarkPlugins: [remarkGfm, mdxMermaid],
+      rehypePlugins: [
+        rehypeSlug,
+        [
+          rehypeAutolinkHeadings,
+          {
+            behavior: "wrap",
+            properties: {
+              className: ["anchor"],
+            },
+          },
+        ],
+      ],
+    });
+
+    const pathParts = document._meta.path.split("/");
+    const fileName = pathParts.pop()!.replace(/\.mdx$/, "");
+
+    const sectionFolder = pathParts[0] || "general";
+
+    const isIndex = fileName === "index";
+
+    const orderMatch = fileName.match(/^(\d+)\./);
+    const order = orderMatch ? parseInt(orderMatch[1], 10) : 999;
+
+    const cleanFileName = fileName.replace(/^\d+\./, "");
+    const cleanPath =
+      pathParts.length > 0
+        ? `${pathParts.join("/")}/${cleanFileName}`
+        : cleanFileName;
+    const slug = cleanPath;
+
+    return {
+      ...document,
+      mdx,
+      slug,
+      sectionFolder,
+      isIndex,
+      order,
+      toc,
+    };
+  };
+}

Then use it in both collections:

 const docs = defineCollection({
   name: "docs",
   directory: "content/docs",
   include: "**/*.mdx",
   exclude: "AGENTS.md",
   schema: z.object({
     title: z.string(),
     section: z.string(),
     summary: z.string().optional(),
     category: z.string().optional(),
     author: z.string().optional(),
     created: z.string().optional(),
     updated: z.string().optional(),
   }),
-  transform: async (document, context) => {
-    // ... duplicated logic
-  },
+  transform: createDocsLikeTransform(),
 });

 const handbook = defineCollection({
   name: "handbook",
   directory: "content/handbook",
   include: "**/*.mdx",
   exclude: "AGENTS.md",
   schema: z.object({
     title: z.string(),
     section: z.string(),
     summary: z.string().optional(),
     author: z.string().optional(),
     created: z.string().optional(),
     updated: z.string().optional(),
   }),
-  transform: async (document, context) => {
-    // ... duplicated logic
-  },
+  transform: createDocsLikeTransform(),
 });

Committable suggestion skipped: line range outside the PR's diff.


export default defineConfig({
collections: [
articles,
changelog,
docs,
legal,
templates,
shortcuts,
hooks,
deeplinks,
vs,
handbook,
roadmap,
],
});
15 changes: 15 additions & 0 deletions apps/web/content/handbook/about/0.what-hyprnote-is.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
---
title: "What Hyprnote is"
section: "About"
summary: "Hyprnote is the first open-source AI notetaker for the enterprise, designed with a privacy-first, local-first philosophy."
---

Hyprnote is the first open-source AI notetaker for the enterprise, designed with a privacy-first, local-first philosophy. At its core, Hyprnote is more than just a notetaker — it's the beginning of an AI-native executive assistant.

## Reducing Cognitive Load

Note-taking reduces cognitive load. We're extending that idea: what other cognitive burdens can we offload to software? Our vision is for Hyprnote to take care of your notes today, and in the future, your email, calendar, and broader workflow — giving you the experience of having someone trustworthy "taking care of things" on your behalf.

## Simple and Accessible

Hyprnote is simple, accessible, and platform-agnostic. Like Apple Notes, but built for meetings. Like an assistant that not only records but also understands and organizes what matters.
19 changes: 19 additions & 0 deletions apps/web/content/handbook/about/1.how-hyprnote-was-born.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "How Hyprnote was born"
section: "About"
summary: "Hyprnote was born from real frustration with existing meeting tools."
---

Hyprnote was born from real frustration.

## The Founders' Perspectives

**John's background in sales** meant living through countless meetings where tools like ClovaNote or Granola weren't enough — they transcribed, but didn't go further.

**Yujong's deep open-source background** brought the conviction that the best solutions must be transparent, extensible, and community-driven. The world is built on open source, and we believe the best way forward is to create massive value first, then capture some of it.

**Together with Duck**, we wanted a product that reflected our shared obsession with craft and simplicity. Hyprnote had to feel trustworthy, reliable, and uncompromising in quality.

## Perfect Timing

The rise of LLMs made this timing perfect: ideas can be prototyped faster, models run locally, and hardware performance keeps getting stronger. What once felt impossible (AI assistants running fully on-device) is now real.
17 changes: 17 additions & 0 deletions apps/web/content/handbook/about/2.the-team.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
title: "The team behind Hyprnote"
section: "About"
summary: "Meet the founders building Hyprnote."
---

## The Founders

**Jeeheon "John" Jeong**: Product design and sales background. Passionate about simplicity, industrial design, and thoughtful UX. Believes in products that remove friction rather than add it.

**Yujong Lee**: Open-source engineer, contributor to projects like Hono and LiteLLM. Systems thinker who goes deep into fundamentals, ensuring robust, scalable architecture.

**Deokhaeng "Duck" Lee**: CS major from Duke, relentless about product quality and code craftsmanship. Obsessed with reliability, testing, and never compromising on user experience.

## Shared Values

We've worked together for years, and though our backgrounds are different, our strength is shared values: we care about craft, simplicity, and building things that people truly want to use.
19 changes: 19 additions & 0 deletions apps/web/content/handbook/about/3.why-hyprnote-is-important.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "Why Hyprnote is important"
section: "About"
summary: "In a world where work is increasingly digital, individuals and companies need tools they can trust."
---

In a world where work is increasingly digital and fragmented, individuals and companies need tools they can trust. Most note-taking and assistant products are cloud-first, with trade-offs in privacy and control. Hyprnote proves another path is possible:

## Our Differentiators

**Local-first, privacy-first.** Your data stays yours.

**Enterprise-grade, open-source.** Compliance-ready, extensible, and transparent.

**Future-proof.** Hardware is advancing rapidly, and local AI is becoming the norm. Hyprnote is built to harness this shift.

## Our Belief

We believe every company and individual deserves software that works for them, not against them.
19 changes: 19 additions & 0 deletions apps/web/content/handbook/about/4.where-were-heading.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "Where we're heading"
section: "About"
summary: "Hyprnote today is a notetaker. But tomorrow, it will be much more."
---

Hyprnote today is a notetaker. But tomorrow, it will be much more:

## Our Vision

**A trusted executive assistant** for managing not only your notes, but also your inbox, calendar, and workflow.

**A suite of open-source, AI-native tools** that empower individuals and organizations without locking them into opaque platforms.

**A fortress-grade enterprise solution** that serves compliance-sensitive industries while remaining simple enough for everyday use.

## Our Ambition

Our ambition is simple: build the AI-native productivity stack that feels as natural and indispensable as having a world-class assistant by your side.
11 changes: 11 additions & 0 deletions apps/web/content/handbook/communication/0.why-this-matters.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
---
title: "Why This Matters"
section: "Communication"
summary: "Communication is how we build trust with our community and customers."
---

Communication is how we build trust with our community and customers. In a world of noisy marketing and empty promises, we stand out by being genuine, helpful, and transparent.

## The Stakes

Every piece of content we publish, every interaction we have, shapes how people perceive Hyprnote. We take this responsibility seriously.
7 changes: 7 additions & 0 deletions apps/web/content/handbook/communication/1.our-north-star.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
title: "Our North Star"
section: "Communication"
summary: "The guiding principle for all our communications."
---

Our north star is simple: be genuinely helpful. Every piece of content should either educate, inspire, or solve a problem. If it doesn't do one of these things, we don't publish it.
21 changes: 21 additions & 0 deletions apps/web/content/handbook/communication/2.principles.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
title: "Communication Principles"
section: "Communication"
summary: "The four principles that guide how we communicate."
---

## 1. Own the Channel

We control our narrative by owning our communication channels — our website, blog, documentation, and social presence. We don't rely on third-party platforms for our core messaging.

## 2. Consistency Across Everything

Whether it's a tweet, a blog post, or a support email, the voice should feel unmistakably Hyprnote — clear, helpful, and human.

## 3. Frictionless Publishing

We've built systems that make it easy to publish and update content. No bureaucracy, no approval chains for routine updates. Move fast, stay accurate.

## 4. Build in Public, Transparently

We share our journey openly — the wins, the challenges, the lessons learned. This builds trust and invites our community to be part of the story.
15 changes: 15 additions & 0 deletions apps/web/content/handbook/go-to-market/0.customers.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
---
title: "Who our customers are"
section: "Go-to-market"
summary: "Understanding who we build for and why."
---

Our customers are knowledge workers, teams, and enterprises who need to capture and act on their conversations. They value privacy, want control over their data, and appreciate tools that work reliably without complexity.

## Primary Segments

**Individual professionals** who attend frequent meetings and need organized, searchable notes.

**Teams** that want to stay aligned without spending hours on documentation.

**Enterprises** in compliance-sensitive industries that need on-premises or self-hosted solutions.
17 changes: 17 additions & 0 deletions apps/web/content/handbook/go-to-market/1.value-we-provide.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
title: "The value we provide"
section: "Go-to-market"
summary: "What makes Hyprnote valuable to our customers."
---

We give people back their focus. Instead of frantically taking notes or trying to remember what was said, our users can be fully present in their conversations knowing Hyprnote has them covered.

## Core Value Propositions

**Time savings** — No more manual note-taking or post-meeting documentation.

**Better recall** — Searchable transcripts and summaries mean nothing gets lost.

**Privacy and control** — Local-first architecture means your data stays yours.

**Simplicity** — Powerful features that feel effortless to use.
17 changes: 17 additions & 0 deletions apps/web/content/handbook/go-to-market/2.how-customers-find-us.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
title: "How customers find us"
section: "Go-to-market"
summary: "Our approach to reaching potential customers."
---

We believe in building in public and letting our work speak for itself.

## Discovery Channels

**Open source community** — Our GitHub presence and contributions to the ecosystem.

**Content and SEO** — Blog posts, documentation, and educational content.

**Word of mouth** — Happy users who share Hyprnote with their networks.

**Direct outreach** — For enterprise customers with specific compliance needs.
17 changes: 17 additions & 0 deletions apps/web/content/handbook/go-to-market/3.how-we-talk-with-them.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
title: "How we talk with them"
section: "Go-to-market"
summary: "Our communication approach with customers."
---

We communicate with honesty and clarity. No marketing fluff, no overpromising. We tell people what Hyprnote does well and where we're still improving.

## Communication Principles

**Be direct** — Say what we mean, mean what we say.

**Be helpful** — Focus on solving problems, not selling features.

**Be responsive** — Treat every piece of feedback as valuable.

**Be transparent** — Share our roadmap, acknowledge our limitations.
15 changes: 15 additions & 0 deletions apps/web/content/handbook/go-to-market/4.how-we-price.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
---
title: "How we price our product"
section: "Go-to-market"
summary: "Our pricing philosophy and approach."
---

We believe powerful tools should be accessible. Our core product is free and open source. We monetize through enterprise features and support for organizations with specific needs.

## Pricing Philosophy

**Free for individuals** — The core Hyprnote experience is free forever.

**Fair for teams** — Reasonable pricing that scales with value delivered.

**Custom for enterprise** — Tailored solutions for compliance-sensitive organizations.
19 changes: 19 additions & 0 deletions apps/web/content/handbook/how-we-work/0.work-styles.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "Work styles"
section: "How-we-work"
summary: "At Hyprnote, our way of working is designed to maximize focus, creativity, and speed."
---

At Hyprnote, our way of working is designed to maximize focus, creativity, and speed. Each founder has a different style, and we embrace that diversity to get the best out of ourselves.

## Individual Styles

**John** works best when in motion, shifting between spaces — coffee shops, parks, different environments. Moving helps reset focus, and speaking ideas aloud (almost like talking to someone) is part of his creative process.

**Yujong** thrives in calm, ordered environments where he can achieve deep focus and think through systems at the root level.

**Duck** prefers structure and used to maintain an office commute for better concentration, showing that physical separation helps him be fully engaged at work.

## Our Culture

Our culture acknowledges these differences. Productivity comes not from forcing uniformity, but from creating conditions where each person can deliver their best.
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
---
title: "Communication and focus"
section: "How-we-work"
summary: "We balance independence with frequent sync to stay aligned and focused."
---

We balance independence with frequent sync. Too much disturbance kills focus; too little sync causes drift. To stay aligned, we use:

## Our Tools

**Slack and async docs** for day-to-day communication.

**GitHub Issues** as our single source of truth for product development and feedback (integrated with Linear).

**Open documentation culture** we're still building, so everyone can contribute and learn.
11 changes: 11 additions & 0 deletions apps/web/content/handbook/how-we-work/2.customer-feedback.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
---
title: "Customer feedback and issues"
section: "How-we-work"
summary: "GitHub Issues is our main public channel for feedback, keeping us open-source friendly and transparent."
---

Early on, we had too many feedback channels — email, Intercom, Canny, Discord, GitHub, Linear. We've since streamlined. Today, GitHub Issues is our main public channel, with everything else synced into it. This helps us stay open-source friendly, transparent, and focused.

## The Principle

The principle is simple: one source of truth, open to everyone.
Loading
Loading