Open in Gitpod: design branch | develop branch
The web site is developed using a Static Site Generator called 11ty.
- The live/public site is generated from the
mainbranch every 30 minutes. Researchers can edit the markdown content of the site directly on this branch. - The staging site is generated from the
releasebranch every 30 minutes. This branch and site are used by the KDL team to test and demonstrate new features and fixes before publishing them tomainbranch. - The development site is generated from the
developbranch every 30 minutes. This branch and site are used by the KDL team to experiment with new, unstable features.
- The TEI editions of the books are manually edited in the
editionbranch - The HTML chunks are generated from the TEI editions every day at 1pm & 6pm and saved into the
dtsbranch by a github workflow (publish-tei.yml) - The staging (and development) Text Viewer reads HTML chunks from the
dtsbranch - The live Text Viewer reads HTML chunks from the
dts-livbranch. Which is a snapshot done manually from thedtsbranch before a live/public release.
frontend/assets/js/entities.json: the index of entities generated from the entities TEI files in thedtsbranch. This json file is generated on thereleasebranch by a github workflow (index-entities.yml) at 9am, 1pm and 6pm. This index is used by the Entities tab in the side drawer of the text viewer and by the Index page.frontend/assets/js/events.json: the index of events generated from theentities.jsonand other manually updated json files. This json file is generated on thereleasebranch by a github workflow (index-entities.yml). This index is used by the Timeline page.frontend/_site/pagefind/: the full text index of the four editions (modern and semi-diplomatic version). It is generated by Pagefind library from HTML files produced by/apps/textsearch/textsearch.js. Those HTML files are derived from the html chunks found in thedtsbranch (see above). That indexing is done each time a site is deployed.
Other workflows
There are two other workflows on github: build and validate-tei. Those are for validation only, they don't produce any output for the site.
To edit the code of the DTS server locally while testing it with the AT Text Viewer on the AT edition:
- git clone kdl-dts-server in a new folder outside the project
- Start the server:
npm run start:at(will run on localhost:3000)
export SITE_ENV='dev'; npm run rebuild