Skip to content

Commit

Permalink
docs: polish FAQ
Browse files Browse the repository at this point in the history
  • Loading branch information
brillout committed Jun 25, 2024
1 parent fbe80b4 commit 749131b
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion docs/components/IntegrationHelp.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ function IntegrationHelp() {
return (
<blockquote>
<p>
<Link href="/faq#i-ve-difficulties-integrating-a-tool-can-i-get-help">Feel free to reach out</Link> if you
<Link href="/faq#i-can-t-achieve-what-i-want-can-i-get-help">Feel free to reach out</Link> if you
run into an issue for integrating a tool.
</p>
</blockquote>
Expand Down
8 changes: 4 additions & 4 deletions docs/pages/faq/+Page.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ import { projectInfo } from '../../utils'

- <Link href="#how-can-i-reach-out-for-help" doNotInferSectionTitle />
- <Link href="#how-can-i-reach-out-for-business-inquiries" doNotInferSectionTitle />
- <Link href="#i-ve-difficulties-integrating-a-tool-can-i-get-help" doNotInferSectionTitle />
- <Link href="#i-can-t-achieve-what-i-want-can-i-get-help" doNotInferSectionTitle />

**Project**

Expand Down Expand Up @@ -42,11 +42,11 @@ Contact `brillout`:
> Don't privately contact `brillout` for getting help unless you're a sponsor, see <Link href="#how-can-i-reach-out-for-help" doNotInferSectionTitle />

## I've difficulties integrating a tool, can I get help?
## I can't achieve what I want, can I get help?

Yes, and you can use GitHub Discussions to get help from the Vike team, see <Link href="#how-can-i-reach-out-for-help" doNotInferSectionTitle />

If it turns out that your difficulties are because of Vike, then we consider this a blocker on Vike's side and we will prioritize resolving your issue.
If it turns out that your issue is caused by a Vike flaw, we will consider it a blocker on Vike's side and prioritize resolving it accordingly.

In general, Vike <Link href="#can-i-use-vike-to-achieve-what-i-want">aims to be highly flexible</Link> and resolving blockers is important to us, ideally by design and at the very least by providing help.

Expand Down Expand Up @@ -84,7 +84,7 @@ Beyond common use cases, Vike has been designed from the ground up to be flexibl

If you have a use case you aren't sure you can implement with Vike then <Link href="#how-can-i-reach-out-for-help">feel free to reach out</Link>.

> In general, Vike aims to be as less blocking as possible. If you run into a blocker then don't hesitate to reach out. See also: <Link href="#i-ve-difficulties-integrating-a-tool-can-i-get-help" doNotInferSectionTitle />
> In general, Vike aims to be as less blocking as possible. If you run into a blocker then <Link href="#i-can-t-achieve-what-i-want-can-i-get-help">don't hesitate to reach out</Link>.

## Will Vike survive?
Expand Down
2 changes: 1 addition & 1 deletion docs/pages/why/+Page.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ Vike is flexible not only by design but also by prioritization: we focus on the
> - <Link href="/pre-rendering">SSG</Link> apps, which usualy lean more on the client.
> - SSR apps, which usually lean more on the server.
<Link href="/faq#i-ve-difficulties-integrating-a-tool-can-i-get-help">We encourage users to reach out</Link> if they run into a blocker caused by Vike. It also helps us resolving blockers (ideally by design and at least by providing help).
<Link href="/faq#i-can-t-achieve-what-i-want-can-i-get-help">We encourage users to reach out</Link> if they run into a blocker caused by Vike. It also helps us resolving blockers (ideally by design and at least by providing help).

A common source of blockers are bugs, and that's why we [systematically and quickly fix bugs](https://github.com/vikejs/vike/issues?q=label%3A%22bug+%3Aboom%3A%22+) &mdash; usually under 24 hours.

Expand Down

0 comments on commit 749131b

Please sign in to comment.