Skip to content

Commit 05e95e1

Browse files
authored
Update README.md
Some editorial changes Most important was adding: The use of AI tools for research is fine, but a PR must be created and submitted by a person. Signed-off-by: Michael Herzog <mjherzog@aboutcode.org>
1 parent 20b146e commit 05e95e1

1 file changed

Lines changed: 10 additions & 6 deletions

File tree

README.md

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,25 +2,29 @@
22

33
## Overview
44
This is the repository for the AboutCode public website. It is based on [Docusaurus](https://docusaurus.io/docs).
5-
This website is currently in a Beta phase with a primary focus on content over format.
5+
This website is currently in an Alpha phase with the primary focus on content over format.
66

77
We value contributions from members of the community. You can always suggest a new feature or a change to some existing element of the website by opening an issue and, if you're ready, a PR.
88
- The normal process for suggesting changes is to create an issue to explain the change before creating a pull request.
99
- When you create an issue for the website please prefix the issue title with "WWW" and apply the label "website".
1010
- The "WWW" prefix in the title is to make it easy to distinguish an issue from "DOC" issues which are about more general documentation and "POST" issues which are ideas for blog posts.
1111
- The "website" label is to ensure that your issue and activity around it will show up in the AboutCode Slack channel "www-aboutcode-org".
1212
- If you do submit a pull request (PR):
13-
- DO not use CoPilot or other AI tools to create the PR or its content. AboutCode does not accept AI-generated PRs and dealing with them takes away valuable time for our core work.
14-
- Do not include changes to the current project configuration - e.g., do not include an updated package-lock.json or yarn.lock with a PR.
13+
- DO not use CoPilot or other AI tools to create the PR or its content. AboutCode does not accept AI-generated PRs and dealing with them takes away valuable time from our core work. The use
14+
of AI tools for research is fine, but a PR must be created and submitted by a person.
15+
- Do not include changes to the current project configuration - e.g., do not include an updated `package-lock.json` or `yarn.lock` with a PR.
1516
- Do not add new dependencies with your PR.
16-
- It is OK to directly submit a PR to fix typos and other minor corrections.
17+
- It is OK to submit a PR without an issue to fix typos and other minor corrections. Please explain the changes in the PR.
1718

1819
The latest website is published at: https://aboutcode-org.github.io/www.aboutcode.org/.
1920

2021
## Simplified website structure
2122
This section documents the website structure which necessarily follows a Docusaurus template and configuration. There are two primary ways to update the website:
22-
- Many elements of the website -- including the navbar, the footer, the sidebars, the landing page, and the blog's authors.yml and tags.yml files -- are complex to update. In most cases you should create an issue and the core team will need to create the PR or help you create one.
23-
- Most of the primary website content (including the blog posts) is composed of markdown files which are much easier to update. For these pages you will see an "Edit this page" link at the bottom of the text. You can use this link to go directly to the corresponding markdown file in this repository where you can use the GitHub UI to create a new branch and PR or you can create a branch and PR locally in your preferred GitHub tools.
23+
- Many elements of the website -- including the navbar, the footer, the sidebars, the landing page, and the blog's authors.yml and tags.yml files -- are complex to update.
24+
- For these website elements you should create an issue and the core team will create the PR or help you create one.
25+
- Most of the primary website content (including the blog posts) is composed of markdown files which are much easier to update. For these pages you will see an "Edit this
26+
page" link at the bottom of the text. You can use this link to go directly to the corresponding markdown file.
27+
- You can use the GitHub UI to create a new branch and PR or you can create a branch and PR locally in your preferred GitHub tools.
2428

2529

2630
![www.aboutcode.org navbar](./website/static/img/www-aboutcode-org-navbar-2026-02-05.png)

0 commit comments

Comments
 (0)