Zengtudor/Nuxt
1
0
Fork 0
mirror of https://github.com/nuxt/nuxt.git synced 2024-11-25 07:05:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore(docs): add sandbox links (#752)

Browse Source 
Co-authored-by: pooya parsa <pyapar@gmail.com>
This commit is contained in:
Sébastien Chopin 2021-10-12 20:26:16 +02:00 committed by GitHub
parent 47ea41dadb
commit 4608c92c2b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 13 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/components/atoms/ButtonLink.vue
View File

@ -1,7 +1,6 @@
<template> <template>
<Link class="button-link" :class="[size, bold ? 'font-semibold' : 'font-medium']" :to="href" :blank="blank"> <Link class="button-link" :class="[size, bold ? 'font-semibold' : 'font-medium']" :to="href" :blank="blank">
<Markdown unwrap="p ul li" /> <Markdown unwrap="p ul li" />
<template #href> <template #href>
<IconExternalLink v-if="blank" class="w-4 h-4 ml-2" /> <IconExternalLink v-if="blank" class="w-4 h-4 ml-2" />
</template> </template>

9
docs/content/1.getting-started/2.installation.md
View File

@ -7,6 +7,13 @@ If you want to migrate an existing Nuxt 2 project, skip this and follow the [Bri
Learn more in [Introduction](/getting-started/introduction). Learn more in [Introduction](/getting-started/introduction).
:: ::
## Play online
You can start playing with Nuxt 3 in your browser using our online sandboxes:
:button-link[Play on StackBlitz]{href=https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz blank}
:button-link[Play on CodeSandBox]{href=https://codesandbox.io/s/github/nuxt/starter/tree/v3-codesandbox blank}
## New project ## New project
Open a terminal, or from [Visual Studio Code](https://code.visualstudio.com/), open an [integrated terminal](https://code.visualstudio.com/docs/editor/integrated-terminal) and use the following command to create a new starter project: Open a terminal, or from [Visual Studio Code](https://code.visualstudio.com/), open an [integrated terminal](https://code.visualstudio.com/docs/editor/integrated-terminal) and use the following command to create a new starter project:
@ -32,7 +39,7 @@ npm install
``` ```
:: ::
## Development Server ## Development server
Now you'll be able to use `yarn dev` to start your nuxt app in development mode: Now you'll be able to use `yarn dev` to start your nuxt app in development mode:

2
docs/content/3.docs/1.usage/index.md
View File

@ -2,6 +2,6 @@
title: 'Usage' title: 'Usage'
layout.aside: true layout.aside: true
layout.asideClass: '' layout.asideClass: ''
navigation.collapse: true navigation.collapse: false
navigation.redirect: /docs/basics/introduction navigation.redirect: /docs/basics/introduction
--- ---

5
docs/content/4.community/2.reporting-bugs.md
View File

@ -16,7 +16,10 @@ Search through the [open issues](https://github.com/nuxt/framework/issues) and [
It's important to be able to reproduce the bug reliably - in a minimal way and apart from the rest of your project. This narrows down what could be causing the issue and makes it possible for someone not only to find the cause, but also to test a potential solution. It's important to be able to reproduce the bug reliably - in a minimal way and apart from the rest of your project. This narrows down what could be causing the issue and makes it possible for someone not only to find the cause, but also to test a potential solution.
Start with [this Nuxt 3 sandbox](https://codesandbox.io/s/github/nuxt/starter/tree/v3-codesandbox) and add the **minimum** amount of code necessary to reproduce the bug you're experiencing. Start with the Nuxt3 sandbox and add the **minimum** amount of code necessary to reproduce the bug you're experiencing:
:button-link[Nuxt 3 on StackBlitz]{href=https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz blank}
:button-link[Nuxt 3 on CodeSandBox]{href=https://codesandbox.io/s/github/nuxt/starter/tree/v3-codesandbox blank}
Once you've reproduced the issue, remove as much code from your reproduction as you can (while still recreating the bug). Time spent making the reproduction as minimal as possible will make a huge difference to whoever sets out to fix the issue. Once you've reproduced the issue, remove as much code from your reproduction as you can (while still recreating the bug). Time spent making the reproduction as minimal as possible will make a huge difference to whoever sets out to fix the issue.