Change how to guide arrangement (#443) #381

	# Sample workflow for building and deploying a VitePress site to GitHub Pages
	#
	name: Deploy VitePress site to Pages

	on:
	# Runs on pushes targeting the `main` branch. Change this to `master` if you're
	# using the `master` branch as the default branch.
	push:
	branches: [main]

	# Allows you to run this workflow manually from the Actions tab
	workflow_dispatch:

	# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
	permissions: write-all

	# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
	# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
	concurrency:
	group: pages
	cancel-in-progress: false

	jobs:
	# Build job
	build:
	runs-on: ubuntu-latest
	steps:
	- name: Checkout
	uses: actions/checkout@v3
	with:
	fetch-depth: 0 # Not needed if lastUpdated is not enabled
	# - uses: pnpm/action-setup@v2 # Uncomment this if you're using pnpm
	- name: Setup Node
	uses: actions/setup-node@v3
	with:
	node-version: 18
	cache: yarn # or pnpm / npm
	- name: Setup Pages
	uses: actions/configure-pages@v3
	- name: Install dependencies
	run: yarn install # or pnpm install / npm ci
	- name: Build with VitePress
	run: yarn docs:build # or pnpm docs:build / npm docs:build
	- name: Deploy to GitHub Pages
	uses: peaceiris/actions-gh-pages@v3
	with:
	github_token: ${{ secrets.GITHUB_TOKEN }}
	publish_dir: ./.vitepress/dist
	cname: rollkit.dev

Provide feedback