You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
svelte/site
thollander adcd13f6dd
Fix the shadow in scrollbar of docs sidebar
7 years ago
..
content Update text.md, line 34 (#2541) 7 years ago
cypress
scripts site: use master branch of template in svelte-app 7 years ago
src Fix the shadow in scrollbar of docs sidebar 7 years ago
static
test/utils
.dockerignore site: use gcloud CLI to build Docker image 7 years ago
.eslintrc.json
.gcloudignore site: use gcloud CLI to build Docker image 7 years ago
.travis.yml
Dockerfile Merge pull request #2479 from sveltejs/gcloud-builds 7 years ago
Makefile site: use gcloud CLI to build Docker image 7 years ago
README.md
appveyor.yml
config.js
cypress.json
package-lock.json Merge branch 'master' into site/deps 7 years ago
package.json Merge branch 'master' into site/deps 7 years ago
rollup.config.js

README.md

Running locally

Set up the project:

git clone https://github.com/sveltejs/svelte.git
cd svelte/site
npm ci
npm run update

Start the server with npm run dev, and navigate to localhost:3000.

Using a local copy of Svelte

By default, the REPL will fetch the most recent version of Svelte from https://unpkg.com/svelte. To use the local copy of the compiler and runtime from this repo, you can navigate to localhost:3000/repl?version=local. To produce the proper browser-compatible UMD build, you will need to run npm run build with the PUBLISH environment variable set (to any non-empty string).

REPL GitHub integration

In order for the REPL's GitHub integration to work properly when running locally, you will need to create a GitHub OAuth app. Set its authorization callback URL to http://localhost:3000/auth/callback, and in this project, create site/.env containing:

GITHUB_CLIENT_ID=[your app's client id]
GITHUB_CLIENT_SECRET=[your app's client secret]
BASEURL=http://localhost:3000

Translating the API docs

Anchors are automatically generated using headings in the documentation and by default (for the english language) they are latinised to make sure the URL is always conforming to RFC3986.

If we need to translate the API documentation to a language using unicode chars, we can setup this app to export the correct anchors by setting up SLUG_PRESERVE_UNICODE to true and SLUG_LANG to the ISO 639-1 two-letter language code of your choice in config.js.