matrix-spec/scripts/generate-matrix-org-assets

#!/bin/sh
#
# generate a tarball of assets suitable for the matrix.org site

cd `dirname $0`/..

mkdir -p assets

# generate the spec docs
./scripts/gendoc.py -d assets/spec

# and the swagger
./scripts/dump-swagger.py -o assets/spec/client_server/unstable.json

# also need the supporting-docs, which become the jekyll posts.
cp -rT supporting-docs assets/jekyll-posts

# create a tarball of the assets. Exclude the spec index for now, as
# we want to leave it pointing at the release versions of the specs.
# (XXX: how to maintain this?)
tar -czf assets.tar.gz --exclude="assets/spec/index.html" assets
Move jekyll back out of matrix-doc again Having the jekyll assets here is a mistake, because they need to be versioned separately to the spec: we keep old versions of the spec, but they sometimes need to be restyled to match the latest website. 7 years ago			`#!/bin/sh`
			`#`
			`# generate a tarball of assets suitable for the matrix.org site`

			cd `dirname $0`/..

			`mkdir -p assets`

			`# generate the spec docs`
			`./scripts/gendoc.py -d assets/spec`

Generate the swagger for export We may as well generate the unstable version of the C-S swagger. 7 years ago			`# and the swagger`
			`./scripts/dump-swagger.py -o assets/spec/client_server/unstable.json`

Move jekyll back out of matrix-doc again Having the jekyll assets here is a mistake, because they need to be versioned separately to the spec: we keep old versions of the spec, but they sometimes need to be restyled to match the latest website. 7 years ago			`# also need the supporting-docs, which become the jekyll posts.`
			`cp -rT supporting-docs assets/jekyll-posts`

			`# create a tarball of the assets. Exclude the spec index for now, as`
			`# we want to leave it pointing at the release versions of the specs.`
			`# (XXX: how to maintain this?)`
			`tar -czf assets.tar.gz --exclude="assets/spec/index.html" assets`