Skip to content

Commit a71e224

Browse files
committed
Remove Netlify configuration
1 parent d69b493 commit a71e224

File tree

1 file changed

+0
-48
lines changed

1 file changed

+0
-48
lines changed

docs/contributing/documentation/admins.md

Lines changed: 0 additions & 48 deletions
Original file line numberDiff line numberDiff line change
@@ -122,51 +122,3 @@ Plone projects currently self-host their official documentation.
122122
123123
1. For the version that you want to deactivate, click its {guilabel}`…` icon, and select {guilabel}`Configure version`.
124124
1. Toggle the {guilabel}`Active` option off, and click {guilabel}`Update version`.
125-
126-
127-
## Add a project to Netlify
128-
129-
To add a new site to Netlify to preview built documentation or storybooks, you need to add a new site to Netlify.
130-
131-
1. Visit [Team Overview](https://app.netlify.com/teams/plone/overview).
132-
1. Click {guilabel}`Add a new site` and select {guilabel}`Import an existing project`.
133-
1. Click {guilabel}`Deploy with GitHub`.
134-
1. Select {guilabel}`plone` for the GitHub organization.
135-
1. Click {guilabel}`Configure Netlify on GitHub`.
136-
1. Select the organization to where you want to install Netlify.
137-
1. Click {guilabel}`Select repositories` and select the repository that you want to add.
138-
1. Click {guilabel}`Update access`.
139-
1. Netlify sends an email to members of the email group `admins` at `plone.org`, who need to review and approve the request.
140-
However the email doesn't specify the repository, and admins will not know what to do.
141-
You must send email to that group, including in your request the organization and repository, such as `plone/volto`.
142-
1. The admin must login to GitHub as an organization owner, then navigate to the requested repository's {guilabel}`Settings`. [What else Admin person?]
143-
1. The admin replies to the requestor, letting them know the request was approved.
144-
145-
From here you need to update your repository to work with Netlify.
146-
For an example, see the following files.
147-
148-
- [Volto `Makefile`](https://github.com/plone/volto/blob/main/Makefile), specifically the `netlify` section.
149-
This will become the command used to build docs on Netlify.
150-
- [Volto `requirements-docs.txt`](https://github.com/plone/volto/blob/main/requirements-docs.txt) specifies the requirements to build the docs.
151-
- [Volto `netlify.toml`](https://github.com/plone/volto/blob/main/netlify.toml) specifies when to build the docs, specifically only when there are changes to documentation files.
152-
153-
Finally you need to configure your site in Netlify.
154-
You may have done some of these steps earlier, but you might need to refine them.
155-
The critical pieces are the following.
156-
157-
1. From the dashboard, select the site to edit it.
158-
1. Click {guilabel}`Site configuration`.
159-
1. One time only, under {guilabel}`General > Site details` click {guilabel}`Change site name`.
160-
A modal dialog appears.
161-
Enter the site name using the pattern `ORGANIZATION_NAME-REPOSITORY_NAME`.
162-
For example, `plone-components`.
163-
Click {guilabel}`Save`.
164-
1. Under {guilabel}`Build & deploy > Continuous deployment`, scroll to {guilabel}`Build settings`, and click {guilabel}`Configure`, then enter the following values.
165-
- {guilabel}`Base directory`: `/`
166-
- {guilabel}`Package directory`: `/`
167-
- {guilabel}`Build command`: `make netlify`.
168-
This is the command you would define in your `Makefile`.
169-
- {guilabel}`Publish directory`: `_build/html`.
170-
This is where the `make` command will output files.
171-
- Finally click {guilabel}`Save`.
172-
1. Under {guilabel}`Build & deploy > Continuous deployment`, scroll to {guilabel}`Branches and deploy contexts`, and click {guilabel}`Configure`, then enter appropriate values.

0 commit comments

Comments
 (0)