Rename seven->aurora docs (#100)

* Rename seven->aurora

* Changelog

* Further rename

Author: sneridagh

.github/ISSUE_TEMPLATE/1_bug_report.md

@@ -1,6 +1,6 @@
 ---
 name: '🐞 Bug report'
-about: 'Create a report to help us improve Volto'
+about: 'Create a report to help us improve Plone Aurora'
 title: ''
 labels: ['01 type: bug', '30 needs: triage']
 assignees: ''
@@ -27,7 +27,7 @@ If applicable, add screenshots or videos to help explain your problem.
 
 - OS: [e.g. iOS]
 - Browser [e.g. firefox, chrome, safari]
-- Volto Version [e.g. 18.4.0]
+- Plone Aurora Version [e.g. 18.4.0]
 - Plone Version [e.g. 6.1.0]
 - Plone REST API Version [e.g. 9.1.0]
 

.github/ISSUE_TEMPLATE/2_feature_request.md

@@ -1,6 +1,6 @@
 ---
 name: '🦄 Feature request'
-about: 'Suggest an idea for Volto'
+about: 'Suggest an idea for Plone Aurora'
 title: ''
 labels: '04 type: enhancement'
 assignees: ''

…/workflows/docs-rtd-pr-preview-volto.yml …ows/docs-rtd-pr-preview-plone-aurora.yml.github/workflows/docs-rtd-pr-preview-volto.yml renamed to .github/workflows/docs-rtd-pr-preview-plone-aurora.yml .github/workflows/docs-rtd-pr-preview-volto.yml renamed to .github/workflows/docs-rtd-pr-preview-plone-aurora.yml

@@ -1,11 +1,11 @@
-# .github/workflows/docs-rtd-pr-preview-volto.yml
+# .github/workflows/docs-rtd-pr-preview-plone-aurora.yml
 name: readthedocs/actions
 on:
   pull_request_target:
     types:
       - opened
     # Execute this action only on PRs that touch
-    # documentation files for Volto.
+    # documentation files for Plone Aurora.
     branches:
       - main
     paths:
@@ -18,7 +18,6 @@ on:
       - "packages/layout/**/*.stories.*"
       - "packages/cmsui/.storybook/**"
       - "packages/cmsui/**/*.stories.*"
-      - "packages/volto/.storybook/**"
       - .readthedocs.yaml
       - requirements-docs.txt
 
@@ -31,5 +30,5 @@ jobs:
     steps:
       - uses: readthedocs/actions/preview@v1
         with:
-          project-slug: "volto"
+          project-slug: "plone-aurora"
           single-version: "true"

README.md

@@ -63,34 +63,34 @@ You can find it at https://plone-storybook.readthedocs.io/?path=/docs/introducti
 
 ## Create a Plone Aurora frontend-only project
 
-To create a project with a frontend-only scaffold using Plone Aurora, follow the [Plone installation documentation](https://volto.readthedocs.io/seven/get-started/create-package.html).
+To create a project with a frontend-only scaffold using Plone Aurora, follow the [Plone installation documentation](https://plone-aurora.readthedocs.io/get-started/create-package.html).
 
 
 ## Documentation
 
-You can find the documentation at [https://volto.readthedocs.io/seven/](https://volto.readthedocs.io/seven/).
+You can find the documentation at [https://plone-aurora.readthedocs.io/](https://plone-aurora.readthedocs.io/).
 
 
 ## Supported Plone, Python, and Plone REST API versions
 
-See [Plone, Python, and Plone REST API compatibility](https://volto.readthedocs.io/seven/contributing/version-policy.html#version-policy-plone-python-and-plone-rest-api-compatibility)
+See [Plone, Python, and Plone REST API compatibility](https://plone-aurora.readthedocs.io/contributing/version-policy.html#version-policy-plone-python-and-plone-rest-api-compatibility)
 
 See the [Plone Release Schedule](https://plone.org/download/release-schedule) for details of maintenance and support.
 
 
 ## Supported Node.js versions
 
-See [Node.js version policy](https://volto.readthedocs.io/seven/contributing/version-policy.html#version-policy-plone-python-and-plone-rest-api-compatibility).
+See [Node.js version policy](https://plone-aurora.readthedocs.io/contributing/version-policy.html#version-policy-plone-python-and-plone-rest-api-compatibility).
 
 
 ## Supported browsers
 
-See [Supported browsers](https://volto.readthedocs.io/seven/contributing/version-policy.html#version-policy-supported-browsers).
+See [Supported browsers](https://plone-aurora.readthedocs.io/contributing/version-policy.html#version-policy-supported-browsers).
 
 
 ## Contributing
 
-To contribute to the Plone Aurora project by writing code, documentation, translations, and so on, please read [Contributing to Plone](https://6.docs.plone.org/contributing/index.html) and [Contributing to Volto](https://volto.readthedocs.io/seven/contributing/index.html).
+To contribute to the Plone Aurora project by writing code, documentation, translations, and so on, please read [Contributing to Plone](https://6.docs.plone.org/contributing/index.html) and [Contributing to Plone Aurora](https://plone-aurora.readthedocs.io/contributing/index.html).
 
 For newcomers to Plone Aurora, Plone, or open source software, you must read and follow [First-time contributors](https://6.docs.plone.org/contributing/first-time.html).
 

apps/aurora/news/+rename-seven-aurora.documentation

@@ -0,0 +1 @@
+Search and replace seven->aurora. @sneridagh

docs/_inc/_branch-policy.md

@@ -20,12 +20,6 @@ legacy
     Legacy versions won't receive any new features.
     They might receive occasional bug fixes or security updates, subject to approval from the Volto Team.
 
-`seven`
-:   This is the branch for the successor of Volto.
-    It is under active development, and it will be released when it is ready.
-    It is not a stable version, and it should not be used in production.
-    The Plone's modular architecture packages are released from this branch.
-
 `main`
 :   This is the bleeding edge branch in git.
     It is the branch upon which future development occurs, and from which future releases shall be cut.

docs/_inc/_hardware-requirements.md

@@ -3,12 +3,18 @@ The hardware requirements below give a rough estimate of the minimum hardware se
 A single Plone installation is able to run many Plone sites.
 
 -   Installation of the Plone backend and Classic UI frontend requires a minimum of 256 MB of RAM and 2GB of disk swap space.
--   Installation of the Seven frontend requires a minimum of 2GB of RAM.
+-   Installation of the Plone Aurora frontend requires a minimum of 2GB of RAM.
 -   After installation, running Plone requires a minimum of 256 MB RAM and 512 MB of disk swap space per Plone site.
     2 GB or more RAM per Plone site is recommended.
 -   Minimum 512 MB hard disk space is required.
     40 GB or more hard disk space is recommended.
 
+```{disclaimer}
+The above hardware requirements for Plone Aurora are estimates based on the experience of the Plone community with Plone Volto.
+The hardware requirements for Plone Aurora should be lower than those of Plone Volto, as Plone Aurora is bundled with Vite, which is faster and more efficient than Webpack, the bundler used in Plone Volto.
+The hardware requirements for Plone Aurora may also change as the project evolves and new features are added.
+Once we have more data on the hardware requirements for Plone Aurora, we will update this section accordingly.
+```
 
 ````{warning}
 {term}`Add-on` products and caching solutions may also increase RAM and disk swap space requirements.

docs/_inc/_install-nodejs.md

@@ -1,4 +1,4 @@
-1.  Install or update the supported LTS versions of Node.js, then activate the version supported in Seven.
+1.  Install or update the supported LTS versions of Node.js, then activate the version supported in Plone Aurora.
 
     ```shell
     nvm install --lts

docs/conceptual-guides/add-on-driven-configuration.md

@@ -4,13 +4,13 @@ myst:
     "description": "Add-on driven configuration"
     "property=og:description": "Add-on driven configuration"
     "property=og:title": "Add-on driven configuration"
-    "keywords": "Seven, add-ons, configuration"
+    "keywords": "Plone Aurora, add-ons, configuration"
 ---
 
 # Add-on driven configuration
 
-Seven is a frontend framework that can be extended using add-ons.
-Add-ons can provide configuration to customize or extend the default configuration of Seven.
+Plone Aurora is a frontend framework that can be extended using add-ons.
+Add-ons can provide configuration to customize or extend the default configuration of Plone Aurora.
 
 See {ref}`what-is-an-addon` for more information about add-ons.
 

docs/conceptual-guides/add-on-loader.md

@@ -4,7 +4,7 @@ myst:
     "description": "An explanation of the add-ons configuration loader in @plone/registry"
     "property=og:description": "An explanation of the add-ons configuration loader in @plone/registry"
     "property=og:title": "Add-ons configuration loader"
-    "keywords": "Seven, @plone/registry, registry, add-ons, loader"
+    "keywords": "Plone Aurora, @plone/registry, registry, add-ons, loader"
 ---
 
 # Add-ons configuration loader
@@ -14,7 +14,7 @@ This chapter explains how the add-ons configuration loader loads configuration f
 
 ## Loader process
 
-The add-ons configuration loader is a mechanism provided by `@plone/registry` to allow add-ons to customize or extend the default configuration of Seven.
+The add-ons configuration loader is a mechanism provided by `@plone/registry` to allow add-ons to customize or extend the default configuration of Plone Aurora.
 `@plone/registry` reads the value of the `main` key entry point in the add-on {file}`package.json`, which specifies the source of the loader.
 This should be a JavaScript or TypeScript file, such as {file}`index.ts` or {file}`index.js`, placed somewhere in your add-on, conventionally at its root.