Infrastructure#
The Turing Way consists of many parts which need to work together to make sure the book can be built, renders correctly and is available on the internet. There are processes to build, deploy and ensure the quality of the book. There is also configuration which may direct those processes or the site. While infrastructure can be defined in many ways, collectively we call these things infrastructure.
Some examples include:
Instructions to build the site from the source files, both locally and for deployment
Continuous integration Continuous Integration tasks to look for problems in the source
Redirect rules to help site navigation and avoid ‘404 Not Found’ errors
Some of this is controlled by data in the repository itself. For example, quality control processes to ensure the book will build and help maintain accessibility standards are part of the Continuous Integration process and described in the .github/workflows/ directory.
Some aspects may not be declared in the repository. For example, hosting is provided by Netlify which holds some of its own configuration.
This section of the book describes the infrastructure that The Turing Way uses. The aim is to demystify how things work, ensure that the infrastructure is described openly, and to help people contribute to infrastructure.