> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mindli.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Thinking workflows plan

# Thinking Workflows Page Plan

Date: 2026-May-28
Status: Draft for review

## 1. Goal

Add a cross-functional docs hub for pages that teach people how to use MindLi to think better across multiple screens and features.

This should not become a new top-level docs section yet. It should be a page under `More`, placed as the last item, and that page can lead to deeper workflow pages over time.

## 2. Recommended Name

Use:

`Thinking Workflows`

Why:

* It is task and outcome oriented, not screen oriented.
* It clearly fits cross-functional topics such as capture, clarify, organize, research, plan, review, write, and decide.
* It works for both human readers and AI agents because the word `Workflows` signals goal-based guidance.
* It does not conflict with existing `Quick Tip` and `Smart Tip` callout naming.

Avoid:

* `Workflows` alone, because it is too generic.
* `Smart Tips`, because that is already an in-page callout pattern.
* A product-object name such as `Spark`, `Box`, or `Home`, because this content should cross product areas.

## 3. Recommended Location

Place it under `More` as the last item.

Expected page path:

`more/thinking-workflows.mdx`

Expected docs URL:

`/more/thinking-workflows`

Suggested nav shape:

```text theme={null}
More
- General
- Add Sparks
- Settings
- Stats
- Advanced
- Thinking Workflows
```

## 4. Page Purpose

The page should act as a hub, not a long reference page.

It should explain:

* Use `Work with MindLi` pages when the reader needs screen-by-screen help.
* Use `Thinking Workflows` when the reader has a real thinking task and needs to move across screens.
* Use linked workflow pages for deeper step-by-step guidance.

## 5. Suggested Hub Intro

Draft intro:

```text theme={null}
Use these guides when you want to use MindLi across screens to think through real work, not just learn one button or one page.
```

## 6. Initial Workflow Topics

Start with a small set of workflow links. Each linked page can be added later.

```text theme={null}
Capture Ideas
Clarify a Spark
Organize with Boxes
Build a Research Trail
Plan a Project
Review and Refine Ideas
Prepare to Write
Make a Decision
```

## 7. AI Agent Guidance

This page should be useful as an AI retrieval hub.

Recommended rule:

```text theme={null}
If the user asks how to accomplish a thinking task, start from Thinking Workflows.
If the user asks where a button or control is, start from Work with MindLi.
```

This keeps the documentation split clean:

```text theme={null}
Thinking Workflows = goal-based guides
Work with MindLi  = screen and control reference
Quick/Smart Tips  = local in-page advice
```

## 8. Implementation Plan

1. Add `more/thinking-workflows.mdx`.
2. Add it as the last item in the `More` group in `docs.json`.
3. Keep the first version as a hub page with short link cards or concise sections.
4. Add deeper pages only after the hub wording feels right.
5. Reuse existing docs conventions for callouts:
   * `Note` for neutral guidance.
   * `Check` for helpful success-oriented tips.
   * Avoid `Warning` in MindLi-authored docs content.

## 9. Open Questions

1. Should the first version link to placeholder pages, or only list topics until each page exists?
2. Should the hub title be exactly `Thinking Workflows`, or should the visible nav label be shorter?
3. Should the first deeper workflow be `Capture Ideas` or `Clarify a Spark`?