Move Support Articles guidance under Storefront - #19
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
nextcommerce-docs | df5d726 | Commit Preview URL Branch Preview URL |
Jul 31 2026, 04:36 AM |
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
| Navigate to **Support > Categories** to set up Support Categories. Categories can be set to Public (visible on your storefront to all customers) or non-Public, which will only be available to users with Dashboard permissions. Set the Display Order to determine in which order the categories will appear on the storefront, and choose to Feature certain categories in your storefront's help section. | ||
| Navigate to **Storefront > Articles**, or go directly to `https://<store>.29next.store/dashboard/theme/articles/`, to manage Support Articles and Categories. | ||
|
|
||
| From the **Articles** tab you can view, create, and modify Support Articles, and assign them to Support Categories. Articles can be set to Public (visible on your storefront to all customers) or non-Public, which will only be viewable by users with Dashboard permissions -- this is useful for building an internal knowledge base for your staff that isn't visible to customers. |
There was a problem hiding this comment.
SUGGESTION: Verify "tab" terminology matches the dashboard UI.
The previous wording referred to "Support > Articles menu". The new wording calls Articles and Categories "tabs" within the Storefront > Articles dashboard view. If the in-dashboard page actually shows Articles and Categories as top-level nav items or sections (not literal tabs), readers following these instructions may not be able to locate them. Worth a quick confirmation against the live dashboard.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
|
|
||
| From the **Articles** tab you can view, create, and modify Support Articles, and assign them to Support Categories. Articles can be set to Public (visible on your storefront to all customers) or non-Public, which will only be viewable by users with Dashboard permissions -- this is useful for building an internal knowledge base for your staff that isn't visible to customers. | ||
|
|
||
| From the **Categories** tab, you can create and manage Support Categories. Categories can be set to Public (visible on your storefront to all customers) or non-Public, which will only be available to users with Dashboard permissions. Set the Display Order to determine in which order the categories will appear on the storefront, and choose to Feature certain categories in your storefront's help section. |
There was a problem hiding this comment.
SUGGESTION: Same "tab" terminology concern as the Articles paragraph above - confirm against the dashboard UI.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
|
|
||
| From the **Support > Articles** menu you can view, create, and modify new Support Articles, and assign them to Support Categories. Articles can be set to Public (visible on your storefront to all customers) or non-Public, which will only be viewable by users with Dashboard permissions -- this is useful for building an internal knowledge base for your staff that isn't visible to customers. | ||
|
|
||
| Set the Display Order to determine in which order the articles will appear within their respective storefront categories. |
There was a problem hiding this comment.
WARNING: This sentence is now orphaned after the surrounding paragraph was removed in this PR.
Previously this "Display Order..." line was preceded by the "From the Support > Articles menu you can view, create, and modify new Support Articles..." paragraph, which provided the Articles context. That intro paragraph was deleted by this PR (its content is now folded into the new Articles paragraph at line 11) but the Display Order sentence was left dangling here as a bare sentence. Either move it into the new Articles paragraph at line 11, or rephrase to make its referent clear (e.g. "For Articles, also set the Display Order...").
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| <Card title="SEO" description="Configure meta tags, social sharing, and search appearance across your store" href="/docs/build-a-store/storefront/seo" /> | ||
| <Card title="Customer Accounts" description="Self-service portal for orders, subscriptions, and support" href="/docs/build-a-store/storefront/customer-accounts" /> | ||
| <Card title="Support Content" description="Build FAQ and knowledge base articles for customer self-service" href="/docs/build-a-store/storefront/support-content" /> | ||
| <Card title="Support Articles" description="Build FAQ and knowledge base articles for customer self-service" href="/docs/build-a-store/storefront/support-content" /> |
There was a problem hiding this comment.
SUGGESTION: Card title and the underlying page slug no longer match.
The Card title was renamed to "Support Articles" but the href still points to /docs/build-a-store/storefront/support-content, and the underlying file is support-content.mdx. Users navigating by title ("Support Articles") won't see a matching URL slug. If backward compatibility/redirects matter, leave a redirect in place when renaming the file to support-articles.mdx; otherwise keep the slug stable and document the rename in the release notes so the SEO/permalink drift is intentional.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: 3 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (3 files)
Fix these issues in Kilo Cloud Previous Review Summary (commit 19e1671)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 19e1671)Status: 4 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (3 files)
Reviewed by minimax-m3 · Input: 44.9K · Output: 1.5K · Cached: 120.1K |
1 participant
Summary
Storefront > Articlesand the direct dashboard routeValidation
npm run audit-developer-linksnpm run validate-linksnpm run build(268 static pages)git diff --check