New set of APIs

[lalc]

We already use slate for our customer APIs. e.g. https://developer.igrant.io/

We are looking for add a directory for a bunch of new api sets. e.g. https://developer.igrant.io/new-apis

What is the best way to do this? I am looking to reuse our current slate fork

[MasterOdin]

As slate is generating to a single static page (with then additional files being relative to that single page), you just need to set-up your build pipeline to copy the contents of build/ into your sub-folder. An example of that is how we do our own gh-pages branch where we have https://slatedocs.github.io/slate/ as the main site which gets published on new versions of slate and then https://slatedocs.github.io/slate/dev/ which is produced on any new commit to dev branch. Our two GH action workflows to accomplish this:

slate/.github/workflows/deploy.yml

Lines 36 to 41 in e3a3a3a

	- name: Deploy
	uses: peaceiris/actions-gh-pages@v3
	with:
	github_token: ${{ secrets.GITHUB_TOKEN }}
	publish_dir: ./build
	keep_files: true

slate/.github/workflows/dev_deploy.yml

Lines 44 to 50 in e3a3a3a

	- name: Deploy
	uses: peaceiris/[email protected]
	with:
	github_token: ${{ secrets.GITHUB_TOKEN }}
	destination_dir: dev
	publish_dir: ./build
	keep_files: true

As part of this, I would recommend that you utilize the docker image of slate as it then allows you to set folders to make it easy to build out of the same repo, where let's say you have two folders, source_1 and source_2 and you want to build them into build_1 and build_2. You can accomplish that with the following incantations:

docker run --rm --name slate -v $(pwd)/build_1:/srv/slate/build -v $(pwd)/source_1:/srv/slate/source slatedocs/slate

docker run --rm --name slate -v $(pwd)/build_2:/srv/slate/build -v $(pwd)/source_2:/srv/slate/source slatedocs/slate