Skip to content

Clarify Quick Start workflow#48

Merged
ilya-chizhov-a merged 3 commits intomasterfrom
docs/quick-start-canonical-workflow
May 6, 2026
Merged

Clarify Quick Start workflow#48
ilya-chizhov-a merged 3 commits intomasterfrom
docs/quick-start-canonical-workflow

Conversation

@ilya-chizhov-a
Copy link
Copy Markdown
Collaborator

@ilya-chizhov-a ilya-chizhov-a commented May 6, 2026

Summary

  • Clarify the Quick Start as a canonical first workflow around a generated REST Draft endpoint.
  • Make the sample row values reproducible so the expected response matches the walkthrough.
  • Move commit/HEAD after the first Draft endpoint query as an optional publishing/versioning step.
  • Add a safety note for public visibility and an expected response shape for the curl request.

Notes

This is intentionally focused on the Quick Start flow, not a full documentation rewrite.

Checks

  • npm run typecheck
  • npm run build

Summary by CodeRabbit

  • Documentation
    • Reorganized quick-start guide with tabbed environment selectors (Cloud, Standalone, Docker)
    • Added setup steps for each environment
    • Introduced new example project with sample data
    • Added API endpoint creation and testing instructions
    • Included curl examples, JSON responses, and Swagger UI guidance
    • Clarified Draft vs. HEAD endpoint differences

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 6, 2026

Warning

Rate limit exceeded

@ilya-chizhov-a has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 22 minutes and 22 seconds before requesting another review.

To continue reviewing without waiting, purchase usage credits in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b4c2e5d1-db24-4bbf-a9c5-1e67866d397e

📥 Commits

Reviewing files that changed from the base of the PR and between 1d8b99b and 6da83ae.

📒 Files selected for processing (1)
  • docs/quick-start.md
📝 Walkthrough

Walkthrough

The quick-start documentation was reorganized and expanded with several structural changes. A tabbed environment selector was introduced at the beginning for Cloud, Standalone, and Docker setup options. A new blog project example was added featuring a typed posts table with explicit row creation and field values. The documentation steps were reordered: Step 6 changed from "Commit Changes" to "Create an API Endpoint" with REST Draft endpoint configuration instructions. Step 7 (Query Your Data) was expanded to include guidance on making endpoints public, curl command examples, a complete JSON response example, and Swagger UI usage. A new Step 8 was added describing the optional commit workflow and the distinction between Draft and HEAD endpoints. Supporting content and visual references were updated throughout to accommodate these changes.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Clarify Quick Start workflow' accurately and concisely summarizes the main change of reorganizing and expanding the quick-start documentation to clarify the workflow.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/quick-start-canonical-workflow

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)
docs/quick-start.md (2)

154-154: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Avoid introducing an unrelated user table in this walkthrough.

This quick start only creates posts; mentioning an extra user table here breaks the narrative continuity and can confuse readers.

Suggested doc tweak
-Click the **code icon** (`</>`) to open the Swagger UI. Notice how Head shows only committed tables, while Draft includes uncommitted changes (e.g., a new `user` table added after the last commit):
+Click the **code icon** (`</>`) to open the Swagger UI. Notice how Head shows only committed state, while Draft includes uncommitted changes:
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/quick-start.md` at line 154, Remove the unrelated example of a `user`
table in the sentence "Notice how Head shows only committed tables, while Draft
includes uncommitted changes (e.g., a new `user` table added after the last
commit)" and replace it with an example that matches the quick start (e.g.,
reference the `posts` table) so the walkthrough remains consistent with the
content that only creates posts; update the parenthetical example to mention
`posts` or remove the parenthetical entirely.

82-82: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Use the Cloud app URL instead of the signup URL in the “Open the Admin UI” step.

For Step 2, linking to /signup can misdirect returning users; this step should point to the actual app/sign-in entry point.

Suggested doc tweak
-- **Cloud:** [cloud.revisium.io](https://cloud.revisium.io/signup) — sign in with Google or GitHub
+- **Cloud:** [cloud.revisium.io](https://cloud.revisium.io) — sign in with Google or GitHub
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/quick-start.md` at line 82, In the "Open the Admin UI" step update the
Cloud link so it points to the app/sign-in entry rather than the signup page:
replace the current markdown line "**Cloud:**
[cloud.revisium.io](https://cloud.revisium.io/signup)" with a link to
"https://cloud.revisium.io" (or the app's main sign-in entry) so returning users
are directed to the proper app entry point instead of /signup.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@docs/quick-start.md`:
- Line 154: Remove the unrelated example of a `user` table in the sentence
"Notice how Head shows only committed tables, while Draft includes uncommitted
changes (e.g., a new `user` table added after the last commit)" and replace it
with an example that matches the quick start (e.g., reference the `posts` table)
so the walkthrough remains consistent with the content that only creates posts;
update the parenthetical example to mention `posts` or remove the parenthetical
entirely.
- Line 82: In the "Open the Admin UI" step update the Cloud link so it points to
the app/sign-in entry rather than the signup page: replace the current markdown
line "**Cloud:** [cloud.revisium.io](https://cloud.revisium.io/signup)" with a
link to "https://cloud.revisium.io" (or the app's main sign-in entry) so
returning users are directed to the proper app entry point instead of /signup.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1b3f4bed-9e50-4bdb-b1b8-59624f155b69

📥 Commits

Reviewing files that changed from the base of the PR and between a893df3 and 1d8b99b.

📒 Files selected for processing (1)
  • docs/quick-start.md

Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

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

No issues found across 1 file

@ilya-chizhov-a
Copy link
Copy Markdown
Collaborator Author

Addressed the CodeRabbit feedback in 4a2af4a:

  • changed Cloud links to https://cloud.revisium.io so returning users land on the main app entry point
  • removed the unrelated user table example from the Draft vs HEAD explanation
  • re-ran npm run typecheck and npm run build locally

There are no open review threads to resolve.

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented May 6, 2026

@ilya-chizhov-a
Copy link
Copy Markdown
Collaborator Author

Final local check after the alt text tweak:

  • npm run typecheck passed
  • npm run build passed
  • production preview /quick-start returned 200 locally
  • all referenced Quick Start screenshots exist
  • no open review threads

@ilya-chizhov-a ilya-chizhov-a merged commit ec45da6 into master May 6, 2026
5 checks passed
@ilya-chizhov-a ilya-chizhov-a deleted the docs/quick-start-canonical-workflow branch May 6, 2026 20:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant