.webp)
We sell SaaSFrame licenses on Gumroad, a secured online selling platform for creators.
SaaSFrame gets updated all the time! Every new update and version will immediately be made available to all SaaSFrame users.
The licence key required to create your SaaSFrame account is send by Gumroad once you made your purchase. If this email is blocked by your email client, send me an email at antoine[at]unmake[dot]io so I can resend the licence key.
You can generate an invoice on Gumroad once you purchased SaaSFrame. You will find the link in the order confirmation email.
If you're not satisfied, you can ask for a refund within 7 days. Just send me an email at antoine[at]unmake[dot]io
SaaS documentation helps users understand a concept, complete a task, or find precise implementation information. Its interface should connect those intentions to the right material without making visitors learn the entire product taxonomy first.
The SaaSFrame references below show documentation homepages and an individual task article. Studying both reveals how discovery and reading need to work together.
A beginner needs orientation; an experienced user may need a procedure or an exact parameter. Give those intentions recognizable routes rather than presenting every page as the same kind of guide.
Use task names where readers seek an outcome and concept names where they need understanding. API reference entries serve a different purpose from a guided first implementation.
Keep the documentation's scope visible. Users should know which product area and relevant version they are reading where those distinctions apply.
The Highnote documentation reference pairs a persistent sidebar and search with product-oriented getting-started cards. A tools section distinguishes API usage, reference material, and an explorer.
This allows visitors to enter through a business task or a technical tool. A documentation homepage should offer a few meaningful starting points rather than duplicating the entire sidebar in the main area.
Explain prerequisites before a procedure asks for unavailable credentials or configuration. A clear entry page can prevent a user from beginning the wrong guide.
The Linear custom-themes article combines sidebar navigation, an in-page contents list, interface images, configuration guidance, a table, and questions. The article's topic remains identifiable while readers move through detail.
Use headings that describe the task's stages or decisions. Screenshots should illustrate the relevant step and remain close to the explanation that identifies their role.
Distinguish visible interface guidance from platform-specific behavior. If a setting differs across environments, make that limitation easy to find in maintained content.
The Lightspark Grid documentation capture offers understanding and start-building routes, a capabilities area, product examples, and further resources. Persistent navigation frames the platform's scope.
This structure helps a newcomer move from the platform model into an implementation path. Avoid leaving the overview at the level of product slogans when the next question is how to begin.
Resources such as sample tools or test-environment routes should be labeled by purpose. A visitor should know whether a link teaches a concept, opens a workspace, or provides implementation material.
Search is valuable when visitors know a term but not its location. Results should identify the relevant product area and page type where ambiguity exists.
Keep no-results feedback useful by offering alternative navigation or a support route. A misspelled query should not feel like proof that documentation does not exist.
Preserve reading position and query context when visitors return from an article, especially in large documentation systems.
A code example or screenshot should support the exact task being explained. Identify relevant versions and prerequisites rather than assuming all readers share the author's environment.
Use placeholders for credentials and avoid publishing real secrets in examples. Keep error examples distinct from successful output.
Review links and screenshots when the interface changes. A correct paragraph paired with an obsolete control location can still prevent users from completing the task.
Procedures need observable outcomes and useful troubleshooting routes. Explain what a reader should see after an important step and where to investigate if that result is absent.
Keep support, feedback, and issue-reporting routes available without interrupting reading. Page feedback can reveal unclear instructions but should not be the only way to report a blocked task.
Use SaaSFrame's documentation references to compare entry points, article hierarchy, and contextual navigation. Design around helping a reader reach a verifiable result.
No. Use the main area to provide meaningful starting points, while navigation supports comprehensive lookup.
Place them near the step or decision they illustrate, with context that explains what the reader should notice.
Include prerequisites, clear actions, expected results, and a recovery route. Instructions alone do not establish that the task succeeded.
