Documentation

Problem

Selling 150+ scripts to thousands of server owners means the same questions arrive every day: how do I install this, what does this config option do, which framework versions work. Answering them one ticket at a time does not scale, and buyers who cannot find answers quietly stop buying.

What we built

A self-made documentation platform, separate from the store but part of the same ecosystem:

• Per-product documentation with installation guides, configuration references and code samples
• Full-text search, so a customer finds the answer faster than a ticket gets picked up
• The public fmLib documentation, so third-party developers can build against our library
• AI-readable exports via llms.txt, which means the documentation also feeds AI tooling, including the support assistant in the One Studios bot

Stack

Nuxt with Nuxt Content and Nuxt UI Pro, plus nuxt-llms for the machine-readable exports.

Outcome

The portal answers the questions that used to fill the ticket queue, before they become tickets. It is a large part of why reviews keep repeating that installation takes minutes: the answer to almost every setup question is one search away, day and night.