Initial commit.

Author: Scott Straughan

.github/dependabot.yml

@@ -0,0 +1,7 @@
+version: 2
+
+updates:
+  - package-ecosystem: 'npm'
+    directory: ''/'
+    schedule:
+      interval: 'weekly'

.github/workflows/build.yml

@@ -0,0 +1,77 @@
+name: Build Website
+
+on:
+  push:
+    branches: [ 'main' ]
+  pull_request:
+    branches: [ 'main' ]
+  schedule:
+    - cron: '0 0 * * *'
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+env:
+  SITE_URL: https://codeplaysoftware.github.io/sycl.tech-website/
+  CONTENT_URL: https://codeplaysoftware.github.io/sycl.tech-content
+
+jobs:
+  # Generates a series of routes that Angular can then use to pre-render
+  generate-routes:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332
+      - name: Set up Python 3.11
+        uses: actions/setup-python@82c7e631bb3cdc910f68e0081d67478d79c6982d
+        with:
+          python-version: '3.11'
+          cache: 'pip'
+      - name: Install Dependencies
+        run: pip install -r ./scripts/routes/requirements.txt --require-hashes --no-deps
+      - run: python ./scripts/routes/generate.py "$CONTENT_URL" >> routes.txt
+      - name: Upload to GitHub Artifacts
+        uses: actions/upload-artifact@0b2256b8c012f0828dc542b3febcab082c67f72b
+        with:
+          name: routes
+          path: routes.txt
+
+  # Build the Angular site
+  build:
+    needs: generate-routes
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332
+      - uses: actions/download-artifact@fa0a91b85d4f404e444e00e005971372dc801d16
+        with:
+          name: routes
+          merge-multiple: true
+      - run: ls -a
+      - name: Setup Node.js 22
+        uses: actions/setup-node@60edb5dd545a775178f52524783378180af0d1f8
+        with:
+          node-version: 22
+          cache: 'npm'
+      - name: Install Dependencies
+        run: npm ci
+      - name: Build
+        run: npm run build -- --base-href "$SITE_URL" --configuration=production
+      - name: Upload to GitHub Artifacts
+        uses: actions/upload-pages-artifact@56afc609e74202658d3ffba0e8f6dda462b719fa
+        with:
+          path: ./dist/sycl.tech-front-end/browser
+
+  # Deployment the site to GitHub Pages
+  deploy:
+    if: (github.event_name == 'push' && github.ref_name == 'main') || github.event_name == 'workflow_dispatch'
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@d6db90164ac5ed86f2b6aed7e0febac5b3c0c03e

.github/workflows/scorecard.yml

@@ -0,0 +1,45 @@
+name: Scorecard Supply-Chain Security
+
+on:
+  branch_protection_rule:
+  schedule:
+    - cron: '27 15 * * 0'
+  push:
+    branches: [ 'main' ]
+  workflow_dispatch:
+
+# Declare default permissions as read only.
+permissions: read-all
+
+jobs:
+  analysis:
+    name: Scorecard analysis
+    runs-on: ubuntu-latest
+    permissions:
+      security-events: write
+      id-token: write
+
+    steps:
+      - name: 'Checkout code'
+        uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
+        with:
+          persist-credentials: false
+
+      - name: 'Run Analysis'
+        uses: ossf/scorecard-action@0864cf19026789058feabb7e87baa5f140aac736 # v2.3.1
+        with:
+          results_file: results.sarif
+          results_format: sarif
+          publish_results: true
+
+      - name: 'Upload Artifact'
+        uses: actions/upload-artifact@97a0fba1372883ab732affbe8f94b823f91727db # v3.pre.node20
+        with:
+          name: SARIF file
+          path: results.sarif
+          retention-days: 5
+
+      - name: 'Upload to Code-Scanning'
+        uses: github/codeql-action/upload-sarif@1b1aada464948af03b950897e5eb522f92603cc2 # v3.24.9
+        with:
+          sarif_file: results.sarif

.gitignore

@@ -0,0 +1,6 @@
+.idea
+.angular
+node_modules
+.DS_Store
+dist
+src/environments/environment.development.ts

CODE_OF_CONDUCT.md

@@ -0,0 +1,61 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making
+participation in our project and our community a harassment-free experience for everyone, regardless of age, body size,
+disability, ethnicity, sex characteristics, gender identity and expression , level of experience, education,
+socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take
+appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits,
+issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the
+project or its community in public spaces. Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting as an appointed representative at an
+online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team
+at <info@codeplay.com>. All complaints will be reviewed and investigated and will result in a response that is deemed
+necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to
+the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent
+repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+---
+
+If there are any issues or suggestions relating to the current set of rules, you can reach us at <info@codeplay.com>.

CONTRIBUTING.md

@@ -0,0 +1,48 @@
+# Contributing to sycl.tech Website
+
+## Pull requests
+
+We really appreciate all pull requests to this project, but we also have a few guidelines in place to help keep the
+project consistent and reduce the noise in commits, pull requests and code. Hopefully these guidelines are clear and
+easy to follow, if not then feel free to add an issue to address this.
+
+Before starting any development please make an issue to communicate your intent and ensure that you are not duplicating
+work.
+
+### Formatting
+
+Please ensure that any contributions are formatted using the following guidelines:
+
+* Empty line at the end of each plaintext file
+* Use "LF" line endings
+* Use 2 character spaces as much as possible
+* Following the naming conventions of the files currently in the repository
+* For images, webp is preferred although for larger images you can use JPEG.
+* For source files, a line length of 120 is encouraged
+* Following the same formatting as currently in use
+
+### Pull request guidelines
+
+* Submit any pull request to the `main` branch, unless you are really sure you need to push your changes elsewhere.
+
+* Unless your pull request is trivial, expect comments and suggestions on your pull request. We will provide feedback as
+  soon as possible.
+
+* We cannot accept or test any pull request with merge conflicts, so please fix these before submitting your pull
+  request.
+
+* Please ensure pull requests are small and focussed. This means that they should only address a single feature, change
+  or bug fix. Larger pull requests trying to fix multiple things at once should be split into smaller pull requests.
+
+* All tests must pass before a pull request is accepted.
+
+* If your pull request adds a new feature, please make sure that you add new test cases to cover this feature.
+
+### Commit guidelines
+
+* In your commit messages, the first line should be a short summary of the changes. Following this should be an empty
+  line, then the remaining commit message explaining the changes in more detail.
+
+* Use the present tense to say what the commit changes.
+
+* Check for any unnecessary whitespace changes with `git diff --check` before committing your changes.