chore: update dev docs (Sofie-Automation#1552)

* chore: update some wording in dev docs

* chore: update some old links

Author: Julusian

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -13,7 +13,7 @@ body:
         and to help the community to collaborate in troubleshooting and fixing them.
 
         Before you post, be sure to read our Contribution guidelines:
-        https://sofie-automation.github.io/sofie-core//docs/for-developers/contribution-guidelines
+        https://sofie-automation.github.io/sofie-core/docs/for-developers/contribution-guidelines
 
   - type: textarea
     attributes:

.github/ISSUE_TEMPLATE/other.yml

@@ -9,7 +9,7 @@ body:
     attributes:
       value: |
         Before you post, be sure to read our Contribution guidelines:
-        https://sofie-automation.github.io/sofie-core//docs/for-developers/contribution-guidelines
+        https://sofie-automation.github.io/sofie-core/docs/for-developers/contribution-guidelines
 
   - type: textarea
     attributes:

.github/ISSUE_TEMPLATE/question.yml

@@ -9,7 +9,7 @@ body:
     attributes:
       value: |
         Before you post, be sure to read our Contribution guidelines:
-        https://sofie-automation.github.io/sofie-core//docs/for-developers/contribution-guidelines
+        https://sofie-automation.github.io/sofie-core/docs/for-developers/contribution-guidelines
 
   - type: textarea
     attributes:

.github/ISSUE_TEMPLATE/rfc.yml

@@ -10,7 +10,7 @@ body:
     attributes:
       value: |
         Before you post, be sure to read our Contribution guidelines:
-        https://sofie-automation.github.io/sofie-core//docs/for-developers/contribution-guidelines
+        https://sofie-automation.github.io/sofie-core/docs/for-developers/contribution-guidelines
 
   - type: textarea
     attributes:

.github/PULL-REQUEST-TEMPLATE.md

@@ -1,6 +1,6 @@
 <!--
 Before you open a PR, be sure to read our Contribution guidelines:
-https://sofie-automation.github.io/sofie-core//docs/for-developers/contribution-guidelines
+https://sofie-automation.github.io/sofie-core/docs/for-developers/contribution-guidelines
 -->
 
 ## About the Contributor
@@ -79,4 +79,4 @@ If they're not, please open the PR as a Draft.
 - [ ] PR is ready to be reviewed.
 - [ ] The functionality has been tested by the author.
 - [ ] Relevant unit tests has been added / updated.
-- [ ] Relevant documentation (code comments, [system documentation](https://sofie-automation.github.io/sofie-core//)) has been added / updated.
+- [ ] Relevant documentation (code comments, [system documentation](https://sofie-automation.github.io/sofie-core/)) has been added / updated.

CHANGELOG.md

@@ -1,2 +1,2 @@
 - [Changelog for _Sofie Core_](meteor/CHANGELOG.md)
-- [_Sofie_ Releases](https://sofie-automation.github.io/sofie-core//releases)
+- [_Sofie_ Releases](https://sofie-automation.github.io/sofie-core/releases)

CONTRIBUTING.md

@@ -1,13 +1,13 @@
 # How to Contribute to this Repository
 
-Before contributing to this specific repository, please read the [Contribution Guidelines](https://sofie-automation.github.io/sofie-core//docs/for-developers/contribution-guidelines) for the Sofie project.
+Before contributing to this specific repository, please read the [Contribution Guidelines](https://sofie-automation.github.io/sofie-core/docs/for-developers/contribution-guidelines) for the Sofie project.
 
 ## Branches
 
 This repository uses the following branches:
 
-- **_master_** is our main branch. We consider it stable and it is used in production.
+- **_main_** is our main branch. We consider it stable and it is used in production.
 - The **_releaseXX_** branches are our in-development branches. When a release is ready, we decide to “freeze” that branch and create a new **_releaseXX+1_** branch.
 
 We require contributions to be based based on the latest **_release\*_** branch.
-The [_Sofie Releases_](https://sofie-automation.github.io/sofie-core//releases) page collects the status and timeline of the releases.
+The [_Sofie Releases_](https://sofie-automation.github.io/sofie-core/releases) page collects the status and timeline of the releases.

DEVELOPER.md

@@ -6,20 +6,20 @@ Before you start, be sure to read the [Contribution guidelines](CONTRIBUTING.md)
 
 ### Documentation
 
-The documentation can be found at [Sofie TV Automation Documentation](https://sofie-automation.github.io/sofie-core//) and its for subsection [For Developers](https://sofie-automation.github.io/sofie-core//docs/for-developers/intro). Specific _Sofie Core_ information can also be in `DOCS.md` and `DEVELOPER.md` in the subfolders of this git project, for example [meteor/server/api/playout](meteor/server/api/playout/DOCS.md).
+The documentation can be found at [Sofie TV Automation Documentation](https://sofie-automation.github.io/sofie-core/) and its for subsection [For Developers](https://sofie-automation.github.io/sofie-core/docs/for-developers/intro). Specific _Sofie Core_ information can also be in `DOCS.md` and `DEVELOPER.md` in the subfolders of this git project, for example [meteor/server/api/playout](meteor/server/api/playout/DOCS.md).
 
 ### Monorepo Layout
 
-This repository is a monorepo and contains both the main application (usually called server-core) as well as multiple auxiliary projects. In the `meteor` folder you will find the main Meteor application with `server` and `client` sub folders for the server-side application and front end. The `packages` folder contains other libraries and apps used together with Sofie Core.
+This repository is a monorepo and contains both the main application (usually called server-core) as well as multiple auxiliary projects. In the `meteor` folder you will find the main Meteor application with `server` for the server-side application. The `packages` folder contains the frontend, other libraries and apps used together with Sofie Core.
 
 ## Getting Started with Local Development
 
-Follow these instructions to start up Sofie Core in development mode. (For production deploys, see [System documentation](https://sofie-automation.github.io/sofie-core//docs/user-guide/installation/intro).)
+Follow these instructions to start up Sofie Core in development mode. (For production deploys, see [System documentation](https://sofie-automation.github.io/sofie-core/docs/user-guide/installation/intro).)
 
 ### Prerequisites
 
-- Install [Node.js](https://nodejs.org) 20 (using [nvm](https://github.com/nvm-sh/nvm) or [nvm-windows](https://github.com/coreybutler/nvm-windows) is the recommended way to install Node.js)
-- Install [Meteor](https://www.meteor.com/install) (`npm install --global meteor`)
+- Install [Node.js](https://nodejs.org) 22 (using [nvm](https://github.com/nvm-sh/nvm) or [nvm-windows](https://github.com/coreybutler/nvm-windows) is the recommended way to install Node.js)
+- Install [Meteor](https://www.meteor.com/install) (`npx meteor`)
 - Enable [corepack](https://nodejs.org/api/corepack.html#corepack) (`corepack enable`) as administrator/root. If `corepack` is not found, you may need to install it first with `npm install --global corepack`
 
 - If on Windows, you may need to `npm install --global windows-build-tools` but this is not always necessary
@@ -72,7 +72,7 @@ The Sofie ui (served by Vite) can be accessed at `http://localhost:3005`. The me
 
 ### Lowering memory, CPU footprint in development
 
-If you find yourself in a situation where running Sofie in development mode is too heavy, but you're not planning on modifying any of the low-level packages in the `packages` directory, you may want to run Sofie in the _UI-only mode_, in which only meteor will be rebuilt and type-checked on modification:
+If you find yourself in a situation where running Sofie in development mode is too heavy, but you're not planning on modifying any of the low-level packages in the `packages` directory, you may want to run Sofie in the _UI-only mode_, in which only meteor and the ui will be rebuilt and type-checked on modification:
 
 ```bash
 yarn dev --ui-only

README.md

@@ -9,7 +9,7 @@ The _Core_ is a _Meteor/Node.JS_-based web server that serves the web GUIs as we
 ## General Sofie System Information
 
 - [_Sofie_ Documentation](https://sofie-automation.github.io/sofie-core/)
-- [_Sofie_ Releases](https://sofie-automation.github.io/sofie-core//releases)
+- [_Sofie_ Releases](https://sofie-automation.github.io/sofie-core/releases)
 - [Contribution Guidelines](CONTRIBUTING.md)
 - [License](LICENSE)
 

packages/documentation/docs/for-developers/for-blueprint-developers/manipulating-ingest-data.md

@@ -1,6 +1,6 @@
 # Manipulating Ingest Data
 
-In Sofie we receive the rundown from an NRCS in the form of the `IngestRundown`, `IngestSegment` and `IngestPart` types. ([Source Code](https://github.com/nrkno/sofie-core/blob/master/packages/shared-lib/src/peripheralDevice/ingest.ts))
+In Sofie we receive the rundown from an NRCS in the form of the `IngestRundown`, `IngestSegment` and `IngestPart` types. ([Source Code](https://github.com/Sofie-Automation/sofie-core/blob/master/packages/shared-lib/src/peripheralDevice/ingest.ts))
 These are passed into the `getRundown` or `getSegment` blueprints methods to transform them into a Rundown that Sofie can display and play.
 
 At times it can be useful to manipulate this data before it gets passed into these methods. This wants to be done before `getSegment` in order to limit the scope of the re-generation needed. We could have made it so that `getSegment` is able to view the whole `IngestRundown`, but that would mean that any change to the `IngestRundown` would require re-generating every segment. This would be costly and could have side effects.