-
Notifications
You must be signed in to change notification settings - Fork 0
Move Support Articles guidance under Storefront #19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
24 changes: 12 additions & 12 deletions
24
content/docs/build-a-store/storefront/support-content.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,31 +1,31 @@ | ||
| --- | ||
| title: "Support Content" | ||
| description: "Create FAQs and a Support knowledge base on your storefront" | ||
| title: "Support Articles" | ||
| description: "Manage FAQs and knowledge base articles on your storefront" | ||
| --- | ||
| ## Categories & Articles | ||
| ## Articles & Categories | ||
|
|
||
| Provide your customers with answers to their most common inquiries by building storefront content such as FAQs, Tutorials, and Policies. | ||
|
|
||
| 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. | ||
|
|
||
| <Callout type="info"> | ||
| 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. Set the Display Order to determine in which order the articles will appear within their respective storefront categories. | ||
|
|
||
| Depending on your **Store Theme**, you may have additional Support Content options available for editing via the Dashboard. | ||
| 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. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. SUGGESTION: Same "tab" terminology concern as the Articles paragraph above - confirm against the dashboard UI. Reply with |
||
|
|
||
| </Callout> | ||
| <Callout type="info"> | ||
|
|
||
| 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. | ||
| Depending on your **Store Theme**, you may have additional Support Article settings available in the Dashboard. | ||
|
|
||
| Set the Display Order to determine in which order the articles will appear within their respective storefront categories. | ||
| </Callout> | ||
|
|
||
| ### Creating and Editing Support Content | ||
| ### Creating and Editing Support Articles | ||
|
|
||
| Choose New Category or New Article from the respective support view to view the content editor. Enter a Title, Excerpt and Body for your content. | ||
| Choose **New Category** or **New Article** from the respective tab to open the content editor. Enter a Title, Excerpt and Body for your content. | ||
|
|
||
| Note that the Excerpt and Body editor sections support HTML and CSS, and will publish the content to your storefront carrying the **Store Theme** styles. | ||
|
|
||
| <Callout type="info"> | ||
|
|
||
| If your store supports multiple [**Languages**](/docs/start-here/get-started/add-locations-and-languages#additional-languages), you will have the option to create separate content for each language in the editor view | ||
|
|
||
| </Callout> | ||
| </Callout> | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SUGGESTION: Card title and the underlying page slug no longer match.
The Card title was renamed to "Support Articles" but the
hrefstill points to/docs/build-a-store/storefront/support-content, and the underlying file issupport-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 tosupport-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 itto have Kilo Code address this issue.