You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -42,24 +42,24 @@ We hope you’ll find the Cookbook creation process to be streamlined! **Test ou
42
42
43
43
## Attribution
44
44
Thanks to everyone who was involved in our sprint day (alphabetical):
45
-
Drew Camron
46
-
Rowan Cockett
47
-
Katelyn FitzGerald
48
-
Robert Ford
49
-
Julia Kent
50
-
Angus Hollands
51
-
Christian Okyere
52
-
Brian Rose
53
-
Kevin Tyle
45
+
-Drew Camron
46
+
-Rowan Cockett
47
+
-Katelyn FitzGerald
48
+
-Robert Ford
49
+
-Julia Kent
50
+
-Angus Hollands
51
+
-Christian Okyere
52
+
-Brian Rose
53
+
-Kevin Tyle
54
54
55
55
[^buildcommand]: Our shared [build-book.yaml workflow](https://github.com/ProjectPythia/cookbook-actions/blob/main/.github/workflows/build-book.yaml) accepts an arbitrary build_command input argument to accommodate using different HTML building tools. We switched the default build_command from jupyter-book build . to myst build –execute –html. You can restore previous behavior by explicitly setting the input argument from your workflow file like this:
[^baseurl]: Unlike Sphinx, [MyST needs to know where a site is being deployed at build time](https://mystmd.org/guide/deployment-github-pages#base-url-configuration-for-github-pages). That means we have to pass different arguments depending on whether we are building a preview or the actual site since the previews are deployed to subdirectories of each site’s base URL.
0 commit comments