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
Copy file name to clipboardExpand all lines: README.md
+35-28
Original file line number
Diff line number
Diff line change
@@ -2,52 +2,59 @@
2
2
3
3
This is the source to [Jupyter.org](https://jupyter.org/).
4
4
5
-
# Build instructions
5
+
##Build the site locally
6
6
7
-
The site is built using GitHub Pages Jekyll, see [Jekyll
8
-
website](https://jekyllrb.com/) for customizing the build process, and detail on how
9
-
what where.
7
+
The site is built with Jekyll, see [the Jekyll website](https://jekyllrb.com/) for how to customize the build process.
10
8
11
-
# Quick local testing
9
+
The easiest way to build the site locally is by using the [`nox` command line tool](https://nox.thea.codes/). This tool makes it easy to automate commands in a repository, and we have included a `build` command to quickly install the dependencies and build the site.
12
10
13
-
Clone this repository locally, and cd into it:
11
+
To build and preview the site locally, follow these steps:
This will install the needed dependencies in a virtual environment using [the `conda` package manager](https://docs.conda.io/en/latest/).
32
32
33
-
Open your browser to localhost:4000.
33
+
**When the build is finished, go to `localhost:4000`**. When Jekyll finishes building your site, it will open a port on your computer and serve the website there so that you may preview it.
34
34
35
-
Edit the various parts, the `liveserve` option should automatically rebuild and
36
-
refresh the pages when changes occur.
35
+
**You can make changes and watch the preview auto-update**. When you make changes to the website, they will automatically be updated in your preview in the browser.
37
36
38
37
To stop serving the website, press **`Ctrl`**-`C` in your terminal
39
38
40
-
Enjoy.
39
+
### Build the site manually
40
+
41
+
To build the site manually, check out the installation commands that are in `noxfile.py`. These use `nox` syntax, but they should give you a clear idea of which packages must be installed in order to build the documentation.
42
+
43
+
## Where the site is hosted
41
44
42
-
# What is where
45
+
The site is automatically built with [Netlify](https://netlify.com), a hosting service for static websites. When any changes are merged into the `master` branch, Netlify will automatically build them and update the website at [jupyter.org](https://jupyter.org).
46
+
47
+
**You can preview changes in Pull Requests**. Netlify will automatically build a preview of the website in an open Pull Request. To see this, click on the **`Show all checks`** button just above the comment box in the Pull Request window. Then click on **`deploy/netlify`** to see a preview of the built site.
48
+
49
+
## Structure of this website
43
50
44
51
Most pages are located at the place where their URL is, nothing fancy. Headers
45
52
and footer are in `_includes/head.html`, `_includes/header.html`,
46
53
`_includes/footer.html`.
47
54
48
55
The **navbar** is in `_data/nav.yml` and looks like that:
49
56
50
-
```
57
+
```yaml
51
58
head:
52
59
- Home
53
60
- title: Install
@@ -70,7 +77,7 @@ which means, insert in order the following links into the navbar:
70
77
The navbar will automatically target `_blank` pages where the url is explicit,
71
78
and mark the correct link as the "current" one.
72
79
73
-
#How do I create a new page?
80
+
## Create a new page
74
81
75
82
Create `my_page.html` (will have url `https://jupyter.org/my_page.html`)
76
83
or `my_page/index.html` (will have url `https://jupyter.org/my_page/`), start with the following:
@@ -88,7 +95,7 @@ You cannot do it yet with .md file, but you will be able soon.
88
95
89
96
Add commit (and don't forget to add to `_data/nav.yml`).
90
97
91
-
#Previewing a Pull Request
98
+
## Preview a Pull Request
92
99
93
100
Netlify is used to provide a link to a rendered website with the changes proposed
94
101
in a PR. This convenience helps reviewers see how the change would look
0 commit comments