tldraw/apps/docs/.gitignore

# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.

# dependencies
/node_modules
/.pnp
.pnp.js

# testing
/coverage

# next.js
/.next/
/out/

# production
/build

# misc
.DS_Store
*.pem

# debug
npm-debug.log*
yarn-debug.log*
yarn-error.log*
.pnpm-debug.log*

# local env files
.env*.local

# vercel
.vercel

# typescript
*.tsbuildinfo
next-env.d.ts


content/gen
content.json
api-content.json
transfer-out: transfer out 2023-04-25 11:01:25 +00:00			`# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.`

			`# dependencies`
			`/node_modules`
			`/.pnp`
			`.pnp.js`

			`# testing`
			`/coverage`

			`# next.js`
			`/.next/`
			`/out/`

			`# production`
			`/build`

			`# misc`
			`.DS_Store`
			`*.pem`

			`# debug`
			`npm-debug.log*`
			`yarn-debug.log*`
			`yarn-error.log*`
			`.pnpm-debug.log*`

			`# local env files`
			`.env*.local`

			`# vercel`
			`.vercel`

			`# typescript`
			`*.tsbuildinfo`
			`next-env.d.ts`


			`content/gen`
Auto content refresh for docs site (#1606) This PR improves the author experience when working on the docs site. When running `docs-dev`, the site's content will now update whenever a content file is changed. ### Context In the docs project, we generate content from two sources: from API documentation generated by api-extractor and from markdown files in the docs/content folder. Generating API docs is a relatively slow process because it involves building and parsing TypeScript declaration files for each package in the monorepo; however, generating docs from the markdown files is basically instantaneous. The same script used to address both tasks, which meant it was too slow to run on each save. Instead, the script needed to be run manually or the dev server would need to be restarted. We now split the generation into two separate scripts. First, the script runs to generate the API content; and then a second script runs to generate the markdown content. The second script also imports and combines the two sources of content. When we build the docs, both scripts are run. When a markdown file changes, the new watcher only runs the second script. This allows the site's content to be updated quickly without having to generate the API docs each time. Note that this does not incorporate live changes to package APIs, though I can't think of a time where we be developing the docs and the APIs at the same time. ### Change Type - [x] `documentation` — Changes to the documentation only 2023-06-17 09:46:46 +00:00			`content.json`
			`api-content.json`