+ ```
+
+ - **Commit the Merge**: Commit the resolved merge:
+
+ ```shell
+ git commit -m "Resolve merge conflicts"
+ ```
+
+3. **Continue to Step 2 in [Start a New Piece of Work](#start-a-new-piece-of-work) Flow**:
+
+ After resolving any merge conflicts, proceed with the next steps as outlined in
+ [Start a New Piece of Work](#start-a-new-piece-of-work). This typically involves making
+ additional changes, committing them, and pushing to the remote repository.
+
+##### Explanation
+
+By following the workflow outlined in [Start a New Piece of Work](#start-a-new-piece-of-work), you
+ensure that your process remains consistent with the initial setup. T
+
+**Avoid using `force-push` and `rebase` on shared branches.**
+
+- **Force-push (`git push --force`)**: This can overwrite commits in the remote branch, which may
+ undo other contributors' work and create difficult-to-resolve merge conflicts.
+
+- **Rebase (`git rebase`)**: While rebase is useful for maintaining a clean commit history, using it
+ on shared branches can rewrite commit history, leading to conflicts and confusion for other
+ collaborators.
+
+To maintain a smooth workflow, use `merge` to integrate changes from the remote branch instead of
+`rebase`, and avoid `force-push` to preserve the integrity of the shared branch history.
diff --git a/src/content/docs/Resources/Quality Assurance/quality-assurance-overview.md b/src/content/docs/Resources/Quality Assurance/quality-assurance-overview.md
new file mode 100644
index 00000000..63eb6eb0
--- /dev/null
+++ b/src/content/docs/Resources/Quality Assurance/quality-assurance-overview.md
@@ -0,0 +1,52 @@
+---
+title: Guide to Quality Assurance Processes
+sidebar:
+ label: Guide to Quality Assurance Processes
+---
+
+## Contents
+
+- [Why/What is Quality Assurance?](#whywhat-is-quality-assurance)
+- [Software Development and Testing](#software-development-and-testing)
+- [Git Contribution Guide](#git-contribution-guide)
+
+## [Why/What is Quality Assurance?](#whywhat-is-quality-assurance)
+
+Quality Assurance (QA) is a procedure designed to ensure the quality of software products or
+services delivered by an organisation. It focuses on enhancing the software development process to
+meet the defined quality standards effectively.
+
+## [Git Contribution Guide](#git-contribution-guide)
+
+The [Git Contributions Guide](/resources/quality-assurance/git-contributions-guide) outlines the
+processes for git workflows, including branching, commit formatting guidelines, and draft pull
+requests.
+
+### Key Areas Covered
+
+- [Contributing to Repositories: How To](/resources/quality-assurance/git-contributions-guide#contributing-to-repositories-how-to)
+- [Branching Guidelines](/resources/quality-assurance/git-contributions-guide#branching-guidelines)
+- [Commit Guidelines](/resources/quality-assurance/git-contributions-guide#commit-guidelines)
+- [Commit Message Format](/resources/quality-assurance/git-contributions-guide#message-format)
+- [Code Review Guidelines](/resources/quality-assurance/git-contributions-guide#code-review-guidelines)
+- [Git Workflow Summary](/resources/quality-assurance/git-contributions-guide#git-workflow-summary)
+
+## [Software Development and Testing](#software-development-and-testing)
+
+The [Testing and Development Processes Document](/resources/quality-assurance/testing-and-dev)
+offers information and resources related to software conception, development, and documentation. It
+covers Test Driven Development (TDD) and feature development using this approach. Reviewing this
+document before starting your coding tasks is recommended as it integrates testing into the
+development process.
+
+### Key Areas Covered
+
+- [Feature Development: Where to Start?](/resources/quality-assurance/testing-and-dev#feature-development-where-do-i-start)
+- [Epics and User Stories](/resources/quality-assurance/testing-and-dev#epics-and-user-stories)
+- [Software Requirements Specification Document](/resources/quality-assurance/testing-and-dev#software-requirements-specification-document)
+- [Testing and Development](/resources/quality-assurance/testing-and-dev#testing-and-development)
+ - [Test Strategy](/resources/quality-assurance/testing-and-dev#test-strategy)
+ - [Test Plans](/resources/quality-assurance/testing-and-dev#making-a-test-plan)
+ - [Testing Tools](/resources/quality-assurance/testing-and-dev#testing-tools)
+ - [Test Driven Development](/resources/quality-assurance/testing-and-dev#test-driven-development)
+ - [Testing Templates](/resources/quality-assurance/testing-and-dev#testing-templates)
diff --git a/src/content/docs/Resources/Quality Assurance/testing-and-dev.md b/src/content/docs/Resources/Quality Assurance/testing-and-dev.md
new file mode 100644
index 00000000..28ce3345
--- /dev/null
+++ b/src/content/docs/Resources/Quality Assurance/testing-and-dev.md
@@ -0,0 +1,211 @@
+---
+title: Testing and Development
+sidebar:
+ label: Testing and Development
+---
+
+### Contents
+
+- [Feature Development: Where Do I Start?](#feature-development-where-do-i-start)
+- [Epics and User Stories](#epics-and-user-stories)
+ - [Epics](#epics)
+ - [User Stories](#user-stories)
+- [Software Requirements Specification Document](#software-requirements-specification-document)
+- [Testing and Development](#testing-and-development)
+ - [Testing Templates](#testing-templates)
+ - [Making a Test Plan](#making-a-test-plan)
+ - [Test Strategy](#test-strategy)
+ - [Testing Tools](#testing-tools)
+- [Test Driven Development](#test-driven-development)
+ - [Determining Appropriate Tests](#determining-appropriate-tests)
+ - [Writing a Failing Test Case](#writing-a-failing-test-case)
+ - [Writing Code to Pass Your Test](#writing-code-to-pass-your-test)
+ - [Refactoring Code](#refactoring-code)
+
+You might be wondering, before jumping into coding and planning tests for a new feature, _where do
+you begin_?
+
+## Feature Development: Where Do I Start?
+
+- Clearly articulate the problem and the need for changes.
+- Create [epics](#epics) for each feature planned for development.
+- Identify [user stories](#user-stories) associated with the feature.
+- Consider how best to mitigate risks or explore alternate solutions.
+- Determine functional and non-functional requirements.
+- Define acceptance criteria:
+ - What are the metrics for success?
+ - What's in or out of scope?
+- Document your purpose and requirements within your
+ [Software Requirements Specification](#software-requirements-specification-document) document.
+- Plan your testing by defining your Test Strategy and Test Plan:
+ - Using your specifications, outline the expected behaviour for different use case scenarios;
+ these will be tested in your [Test Plan](#making-a-test-plan).
+ - Determine _how_ you will test your scenarios and describe this in your
+ [Test Strategy](#test-strategy).
+
+## Epics and User Stories
+
+### Epics
+
+Epics describe a large body of work that will be broken down into smaller tasks, called user
+stories. They provide a higher-level view of user requests or needs, helping with larger aims,
+value, organization, and hierarchy. Epics will be divided into smaller, more manageable tasks ("user
+stories") for team members.
+
+### User Stories
+
+User Stories are user-centric statements often formatted as:
+
+**"As a [persona], I [want to], [so that]"**
+
+This describes a _persona + need + purpose_.
+
+- **[persona]** β Describes the person for whom we are building this feature. It is more than just a
+ role or job title; it includes understanding who they are, how they work, think, and feel.
+- **[wants to]** β Describes the user's _intent_ (what they want to achieve) rather than the feature
+ itself. Avoid detailing implementation specifics here.
+- **[so that]** β Explains the motivation behind the user's desire and the overall benefit from
+ achieving it.
+
+User stories use non-technical language to provide context and an understanding of what needs to be
+built and why. They focus on user needs, are discrete, and manageable for team members in an Agile
+environment.
+
+Benefits include:
+
+- Keeps focus on the user, solving real-world problems in user-centric ways.
+- Enables collaboration by defining end goals and facilitating teamwork.
+- Drives creative solutions by focusing on end-user needs rather than implementation details.
+
+In Agile methodology, during a sprint or iteration, the team selects which user stories to address,
+discusses requirements, and updates stories with agreed requirements. Tasks and subtasks are tracked
+and assigned using the relevant project management tool, with future user stories remaining in the
+backlog.
+
+When defining user stories, consider:
+
+- Definition of "done": How will we know when a task/story is complete?
+- Tasks or subtasks: What steps need to be completed and by whom?
+- User personas: Who is the user? Are there multiple users (consider creating user stories for
+ each)?
+- Ordered steps: For larger processes, write a story for _each step_.
+- Time: Consider how long a story might take; if it's more than one sprint or appears complex, break
+ it down into smaller stories or an epic.
+
+Further background on user stories can be found at
+[Atlassianβs User Stories Guide](https://www.atlassian.com/agile/project-management/user-stories).
+
+## Software Requirements Specification Document
+
+A Software Requirements Specification (SRS) document outlines expectations for your product, its
+performance, and required functionality. An SRS includes the following components:
+
+---
+
+- **Introduction**:
+ - **Product Purpose**: Define the purpose of the SRS.
+ - **Intended Audience**: Who are the expected readers (testers, developers, leadership team) of
+ the SRS document?
+ - **Intended Use**: How are these readers expected to use the SRS document?
+ - **Scope**: What are the goals and objectives for this product? What should the product do (and
+ what should it _not_ do)?
+ - **Definitions and Acronyms**: Describe relevant terms, definitions, and acronyms needed to
+ understand the document.
+
+---
+
+- **Overall Description**: Describes your product and what you are going to build. Indicate whether
+ it is a new product or an enhancement/add-on to an existing product, who it is for, and its value.
+ This section explains the general background and factors affecting requirements (rather than the
+ specific requirements themselves).
+ - **User Needs**: Who will use your product feature and how? What needs do your end users have
+ that you need to address?
+ - **Assumptions and Dependencies**: List any assumptions made (what are we assuming to be true) or
+ dependencies for your product/feature.
+
+---
+
+- **System Features and Requirements**:
+ - **Functional Requirements**: Essential requirements that provide functionality, often described
+ with "The system shall..." statements.
+ - **External Interface Requirements**: Specific requirements for how your product interfaces with
+ other components, including user, hardware, software, and communications interfaces.
+ - **System Features**: Types of functional requirements needed for system operation.
+ - **Nonfunctional Requirements**: Requirements related to performance, safety, security, and
+ quality.
+
+---
+
+Further references include Perforce's
+[How to Write an SRS Document](https://www.perforce.com/blog/alm/how-write-software-requirements-specification-srs-document)
+and IEEEβs
+[Recommended Practice for Software Requirements Specifications](https://drive.google.com/file/d/1G1vQq-RjnbEmTTzItIUarWuMnbqZchlx/view).
+
+_After completing the SRS, obtain approval from key stakeholders. Ensure everyone reviews the latest
+version of the document._
+
+## Testing and Development
+
+Testing should be integrated into the software development process. Thoth-Tech advocates for a
+[Test Driven Development](#test-driven-development) (TDD) approach. All coding projects should
+consider and document their [Test Plan](#making-a-test-plan) and [Test Strategy](#test-strategy) as
+project deliverables.
+
+### Testing Templates
+
+- [Test Plan Template](/resources/quality-assurance/templates/test-plan-template)
+- [Test Strategy Template](/resources/quality-assurance/templates/test-strategy-template)
+
+### Making a Test Plan
+
+For each product/feature, using the specifications, outline the expected behaviour for different use
+case scenarios. A collaborative approach ensures defining the right problem and solution. These
+scenarios will be detailed in a Test Plan, recording each scenario to be tested, the expected
+outcome, and the actual outcome of tests. A simple Markdown
+[Test Plan Template](/resources/quality-assurance/templates/test-plan-template) is available.
+
+### Test Strategy
+
+Consider _how_ you will test your scenarios, including what [testing tools](#testing-tools) you will
+use, platforms for tests, release processes, and deliverables. This should be part of your Test
+Strategy β a document to be produced as part of the QA process. Other documents may include a Test
+Plan and Bug Reports.
+
+While manual testing might be conducted initially, transitioning to automated tests enhances
+efficiency, code check ease, and is preferred for integrating test automation into the deployment
+pipeline. Testing automation should be part of your strategy.
+
+### Testing Tools
+
+Various tools may be used for testing tasks, depending on the technology stack. Common tools
+include:
+
+- **Testing Frameworks**: Tools for automated testing, such as JUnit, TestNG, Mocha, Jasmine, etc.
+- **Test Automation Tools**: Tools like Selenium, Cypress, or Playwright for web application
+ testing.
+- **Continuous Integration Tools**: Jenkins, GitHub Actions, Travis CI for integrating automated
+ tests into the deployment pipeline.
+- **Bug Tracking Tools**: JIRA, Bugzilla, or GitHub Issues for tracking and managing defects.
+
+## Test Driven Development
+
+### Determining Appropriate Tests
+
+Before coding, identify what you are trying to achieve and how you will test it. Determine the
+requirements you need to meet and plan your tests accordingly.
+
+### Writing a Failing Test Case
+
+Create a test case that will initially fail. This test case should cover the specific functionality
+you are adding or changing and reflect the expected behaviour that the code needs to exhibit.
+
+### Writing Code to Pass Your Test
+
+Implement the code necessary to pass your failing test case. Ensure the implementation focuses
+solely on making the test pass, avoiding unnecessary complexity or features.
+
+### Refactoring Code
+
+After your test case passes, refactor your code to improve its structure and readability while
+ensuring it still passes all tests. This involves cleaning up the code, removing redundancy, and
+enhancing efficiency.
diff --git a/src/content/docs/Resources/documenting-for-thoth-tech.md b/src/content/docs/Resources/documenting-for-thoth-tech.md
new file mode 100644
index 00000000..7ad7f570
--- /dev/null
+++ b/src/content/docs/Resources/documenting-for-thoth-tech.md
@@ -0,0 +1,42 @@
+---
+title: Documenting for Thoth Tech
+sidebar:
+ label: Documenting for Thoth Tech
+---
+
+Documentation plays a vital role in the software development lifecycle at Thoth Tech. It ensures
+that our sustainable solutions are well-understood, accessible, and can be effectively handed over
+or referenced in the future. Proper documentation helps others understand the workings and rationale
+behind projects, facilitating continuity and knowledge sharing.
+
+Documentation provides official information, prepared by the company, for both users and
+contributors. It is tailored to specific audiences and offers insights into the development
+lifecycle and final product.
+
+All Thoth Tech documentation is stored in the
+[Documentation Repository](https://github.com/thoth-tech/documentation) on our company GitHub.
+Documentation should be written in Markdown and cover various aspects such as research, meeting
+minutes, and software user guides.
+
+## Top Tips for Writing at Thoth Tech
+
+Effective documentation is clear, concise, and easy to read. At Thoth Tech, we adhere to the
+principles of plain English, specifically Australian English, to ensure clarity and accessibility.
+
+We aim for our writing to achieve the following goals:
+
+- **Empowerment:** Providing knowledge to help our users and contributors make the most of our
+ products.
+- **Respect:** Creating inclusive and accepting content that values every individual.
+- **Education:** Offering valuable information that supports learning and understanding.
+- **Guidance:** Leading our audience thoughtfully towards their objectives.
+- **Honesty:** Being transparent and focusing on our genuine strengths.
+
+When writing documentation, consider these attributes:
+
+- **Clear:** Ensure the content is easy to understand.
+- **Useful:** Provide practical information that serves a purpose.
+- **Friendly:** Use a tone that is welcoming and approachable.
+- **Appropriate:** Tailor the content to the specific audience and context.
+- **Consistent:** Maintain uniformity in terminology and style.
+- **Accessible:** Ensure the documentation is easily accessible and understandable for all users.
diff --git a/src/content/docs/Resources/faq.mdx b/src/content/docs/Resources/faq.mdx
new file mode 100644
index 00000000..cbc525db
--- /dev/null
+++ b/src/content/docs/Resources/faq.mdx
@@ -0,0 +1,142 @@
+---
+title: Frequently Asked Questions (FAQ)
+description: Frequently Asked Questions
+---
+
+Welcome to Thoth Tech's Frequently Asked Questions (FAQ) section! We understand that you might have
+queries about contributing to Thoth Tech or seek clarification on how to use certain tools. Our aim
+is to provide you with comprehensive and straightforward answers to address your concerns promptly.
+
+
+ Where can I find the link to Thoth Tech GitHub channel?
+
+Find the link [here](https://github.com/thoth-tech/).
+
+
+
+
+ Which Thoth Tech repository should I clone to contribute to the Documentation Website?
+
+To contribute to the Documentation Website, locate the
+["Thothtech-Documentation-Website" repository](https://github.com/thoth-tech/ThothTech-Documentation-Website/tree/main),
+navigate to the `src/content/docs`, and upload your `.md` or `.mdx` file to the relevant folder.
+
+
+
+
+ When I attempt to run the documentation website locally, it says "The .nvmrc file is using
+ a version of node that is not supported by Astro anymore". How do I fix this?
+
+Re-install or upgrade the version of Node.js software on your laptop.
+
+
+
+
+ How do I make a newly created folder appear on the side navbar of the Documentation website?
+
+In the `astro.config.mjs` file, create a new label (if itβs a main folder) or item (if itβs a
+subfolder). You do not need to reinvent the wheel; you can copy from what already exists in the
+`astro.config.mjs` file, insert the copied block into the right location, and modify the labels and
+directory link.
+
+
+
+
+ Is there a video that helps me understand how to migrate documents to the Documentation website?
+
+Yes, there is. Find some helpful links below:
+
+- [Instructional video](https://deakin365.sharepoint.com/:v:/r/sites/ThothTech2/Shared%20Documents/General/Instructional%20Video%20-%20How%20To%20Upload%20Documents%20to%20Starlight.mp4?csf=1&web=1&e=s26lMo).
+- [Help hub session recording](https://deakin.au.panopto.com/Panopto/Pages/Viewer.aspx?id=2bd50464-8fe7-4b23-9724-b1c101654ccc).
+
+
+
+
+ What do I do to resolve Linelint issues in the CI build checks for my Pull Request?
+
+Identify the file with the lint issue from the details section of the CI build check. Open the
+identified file in Visual Studio Code or your editor of choice, right-click on the document, and
+select "Format document with markdownlint". Ensure that you have the markdownlint extension
+installed on your code editor.
+
+
+
+
+ What do I do to resolve Prettier issues in the CI build checks for my Pull Request?
+
+Identify the file with the Prettier issue from the details section of the CI build check. Open the
+identified file in Visual Studio Code or your editor of choice, right-click on the document, and
+select "Format document with Prettier". Ensure that you have the Prettier extension installed on
+your code editor.
+
+
+
+
+ My Pull Request keeps failing the Netlify checks. What should I do?
+
+The primary reason for this issue is often due to the absence of a title block at the start of your
+Markdown file. For example:
+
+```markdown
+title: Frequently Asked Questions (FAQ) description: Frequently Asked Questions
+```
+
+
+
+
+
+ I currently have a Pull Request that is still under review. When I make a commit for a new
+ change, I am unable to create another Pull Request. Why is that?
+
+ Because your Pull Request is still under review and you are pushing changes from the same GitHub
+ account (which is your personal one), your new commit will still fall under your old PR. No cause
+ for alarmβif all checks in your PR have passed, reach out to your approver to approve it so you
+ can create a new PR for new commits.
+
+
+
+
+ How do I set up my local development environment for contributing to the Documentation Website?
+
+ To set up your local development environment, follow these steps: 1. Clone the repository: `git
+ clone https://github.com/thoth-tech/ThothTech-Documentation-Website.git` 2. Navigate to the
+ project directory: `cd ThothTech-Documentation-Website` 3. Install dependencies: `npm install` 4.
+ Run the development server: `npm start` Ensure you have Node.js and npm installed on your machine.
+
+
+
+ What are the guidelines for writing and formatting documentation?
+ When writing and formatting documentation, follow the [Writing Style
+ Guide](/resources/writing-style-guide)
+
+
+
+ How do I update or correct existing documentation?
+ To update or correct existing documentation: 1. Locate the relevant Markdown file in the
+ repository. 2. Make your changes or corrections. 3. Commit your changes and push them to your
+ branch. 4. Create a Pull Request with a clear description of the changes made.
+
+
+
+
+ How do I contribute to the development of new features or improvements for the Documentation
+ Website?
+
+ To contribute to new features or improvements: 1. Fork the repository and create a new branch for
+ your changes. 2. Develop and test your changes locally. 3. Submit a Pull Request with a clear
+ description of the feature or improvement.
+
+
+
+ How do I navigate the documentation website effectively?
+ To navigate the documentation website: - Use the search feature to find specific topics. - Browse
+ the table of contents to locate sections.
+
+
+
+
+ What are the best practices for including code snippets or examples in documentation?
+
+ Best practices for code snippets: - Use fenced code blocks for better readability. - Include
+ comments to explain complex code sections. - Ensure code examples are tested and functional.
+
diff --git a/src/content/docs/Resources/introduction.md b/src/content/docs/Resources/introduction.md
new file mode 100644
index 00000000..4b424707
--- /dev/null
+++ b/src/content/docs/Resources/introduction.md
@@ -0,0 +1,133 @@
+---
+title: Introduction
+---
+
+The Company Operations Guide provides Thoth Tech members with standardised procedures for conducting
+various company activities. This guide aims to ensure consistency in the day-to-day operations
+across all teams and products.
+
+## Table of Contents
+
+- [Storage of Documentation](#storage-of-documentation)
+ - [Documentation Website](#documentation-website)
+ - [Documentation Repository](#documentation-repository)
+ - [Microsoft Teams Channels](#microsoft-teams-channels)
+ - [File & Folder Naming Conventions](#file--folder-naming-conventions)
+- [Conducting Team Meetings](#conducting-team-meetings)
+ - [Location of Team Meetings](#location-of-team-meetings)
+ - [Scheduling Meetings in Private Channels](#scheduling-meetings-in-private-channels)
+ - [Meeting Recordings](#meeting-recordings)
+
+## Storage of Documentation
+
+Proper documentation is a crucial aspect of company operations at Thoth Tech. This includes:
+
+- Research findings
+- Meeting notes
+- Testing processes and results
+- And more
+
+All documentation must adhere to the
+[Writing Style Guide](https://github.com/thoth-tech/handbook/blob/main/docs/processes/documentation/writing-style-guide.md)
+and be stored in designated locations. The following sections describe the appropriate places for
+storing different types of documentation and recommended practices.
+
+### Documentation Website
+
+The Documentation Website serves as the "source of truth" for Thoth Tech, providing high-level
+information about the company, its projects, products, and teams. It includes:
+
+- **Product Information:**
+ - Overview, goals, and objectives
+ - Onboarding guides for new members
+- **Team Information:**
+ - Team members and their roles
+ - Trimester objectives and goals
+- **Company-Wide Information:**
+ - Communication and contribution guidelines
+ - Best practice policies and learning resources (e.g., Markdown usage)
+ - Onboarding and offboarding processes
+ - Company reports, charter, and structure
+ - Leadership information, data strategies, and quality assurance practices
+
+### Documentation Repository
+
+The [Documentation Repository](https://github.com/thoth-tech/documentation) houses documents that do
+not fit into the Company Handbook but are important for transparency and tracking team progress.
+Each team has a dedicated folder within the repository for storing:
+
+- Research notes and findings
+- Planning documents
+- Diagrams
+- Meeting notes
+- Collaborative documents
+- Testing processes and results
+
+This centralised repository helps document the work of individuals and teams.
+
+### Microsoft Teams Channels
+
+Microsoft Teams channels are essential for effective communication and collaboration within Thoth
+Tech. They provide a centralised space for team discussions, real-time messaging, and document
+sharing, which are critical for maintaining coordination and engagement among team members.
+
+Channels are primarily used for:
+
+- **Communication:** Engage in discussions, share updates, and provide feedback in a structured
+ manner. Channels facilitate clear and organised conversations among team members, ensuring that
+ information is easily accessible and traceable.
+- **Collaboration:** Collaborate on projects and tasks through integrated tools and shared files.
+ Channels support collaborative document editing and real-time interaction, enabling teams to work
+ together efficiently.
+
+- **Meeting Coordination:** Schedule and conduct team meetings directly within channels. This
+ practice helps in keeping all relevant information and discussions in one place, making it easier
+ to track and reference meeting outcomes.
+
+While Microsoft Teams channels are not intended for storing finalised work or extensive
+documentation, they play a crucial role in supporting ongoing communication and collaborative
+efforts. For such documents, refer to the Documentation Repository or the Documentation Website.
+
+#### File & Folder Naming Conventions
+
+For any documents or notes shared in Microsoft Teams channels, use the following naming convention
+for folders: **Trimester-Year-TeamName** (e.g., "T2-2022-CompanyLeadership"). File names should be
+descriptive and concise to aid in quick identification and retrieval (e.g., "Team-Meeting-Notes"
+rather than "Untitled1"). This practice helps maintain organisation and ensures that all members can
+easily locate relevant files.
+
+## Conducting Team Meetings
+
+Regular team meetings, held at least weekly, are essential for team engagement, collaboration, and
+management. These meetings are opportunities to discuss team direction, tasks, and member progress.
+
+Try to record all impromptu meetings so that they can be referred to at a later date, as well as be
+used as evidence towards your portfolio.
+
+### Location of Team Meetings
+
+Each Thoth Tech team is assigned a private channel in Microsoft Teams for communication and
+collaboration. **Team meetings should be conducted in these private channels** to maintain
+consistency and transparency. This practice also enables company directors to monitor team
+engagement and attend meetings when necessary.
+
+#### Scheduling Meetings in Private Channels
+
+To schedule a recurring meeting in a private Microsoft Teams channel:
+
+1. In Microsoft Teams, click the three dots next to the relevant team channel's name.
+2. Select "Get email address" from the drop-down menu.
+3. Copy the channel's email address (found in angle brackets) from the resulting window.
+4. Go to the "Calendar" section in Teams and click "New meeting."
+5. Paste the channel email address into the "Add required attendees" field.
+6. Complete the meeting details (name, date, recurrence, description) and save.
+
+This setup will send a meeting invite to all channel members and add the event to the calendar.
+
+### Meeting Recordings
+
+Recording meetings is crucial for documenting engagement and collaboration. Recordings also allow
+members who couldn't attend to catch up on discussions. **All team meetings must be recorded** using
+the MS Teams recording feature. Recordings should be stored in an appropriately named folder within
+the "Files" tab of the team's private channel, accessible to relevant team members, leadership, and
+directors.
diff --git a/src/content/docs/Resources/privacy-policy.mdx b/src/content/docs/Resources/privacy-policy.mdx
new file mode 100644
index 00000000..7024c4f3
--- /dev/null
+++ b/src/content/docs/Resources/privacy-policy.mdx
@@ -0,0 +1,137 @@
+---
+title: Privacy Policy
+sidebar:
+ label: Privacy Policy
+---
+
+- **Effective Date:** 10 Dec 24
+- **Owner:** Thoth Tech
+- **Contact Details:** thoth.tech.deakin@gmail.com
+
+At Thoth Tech, we are committed to protecting your privacy and managing your personal information
+transparently and responsibly. This Privacy Policy outlines how we collect, use, disclose, and
+manage personal information in compliance with the Australian Privacy Principles (APPs).
+
+---
+
+## 1. Information We Collect
+
+We may collect the following types of personal information:
+
+- **Analytics Data:** Non-identifiable information about your interaction with our website, such as
+ pages visited, time spent, and clickstream data.
+- **Contact Information:** If you reach out to us directly, we may collect your name, email address,
+ or other contact details.
+
+We do not collect sensitive information as defined by the Privacy Act 1988 (Cth), such as health
+information, racial or ethnic origin, or religious beliefs, unless explicitly provided by you with
+your consent.
+
+---
+
+## 2. How We Collect Information
+
+We collect information using:
+
+- **Cookies:** Small text files placed on your device to gather analytics data.
+- **Direct Communication:** Information provided by you through forms, emails, or other methods.
+
+---
+
+## 3. Why We Collect Information
+
+We collect personal information for the following purposes:
+
+- To understand how users interact with our website.
+- To improve the content and features we offer to our community.
+- To ensure our resources meet the needs of our user base.
+
+**Note:** We are a non-profit organisation, and your data will not be used for advertising purposes
+or sold to third parties.
+
+---
+
+## 4. Storage and Security of Information
+
+Your data is stored securely on servers compliant with modern security standards. We implement
+reasonable safeguards to protect your information from misuse, interference, loss, unauthorised
+access, modification, or disclosure. Data processed through Google Analytics is transmitted securely
+using HTTPS encryption and stored on servers adhering to robust privacy and security standards,
+including compliance with the General Data Protection Regulation (GDPR) and other relevant privacy
+laws. While Google Analytics implements stringent security measures, it is important to note that
+data stored on its platform is subject to Googleβs data policies and may be accessible to Google
+under certain circumstances. We are committed to ensuring that our use of Google Analytics complies
+with applicable data protection laws and prioritises the security and privacy of your data.
+
+---
+
+## 5. Disclosure of Information
+
+We do not disclose personal information to third parties unless required to do so under Australian
+law, such as in response to a legal obligation or regulatory requirement, or unless you have
+explicitly authorised such disclosure. If it becomes necessary to disclose personal information to
+recipients located outside Australia, we will ensure that the disclosure complies with the
+Australian Privacy Principles (APPs). This includes taking reasonable steps to ensure that the
+overseas recipient handles your personal information in a way that is consistent with Australian
+privacy standards. Where practical, we will notify you of the countries in which these recipients
+are likely to be located and the nature of the data being disclosed. Our priority is to maintain the
+integrity and security of your personal information, regardless of where it is processed or stored.
+
+---
+
+## 6. Access and Correction of Information
+
+You have the right to access and correct any personal information we hold about you. To request
+access or a correction, please contact us at thoth.tech.deakin@gmail.com. We will respond to your
+request within a reasonable timeframe.
+
+---
+
+## 7. Complaints
+
+If you believe we have breached the APPs, you can lodge a complaint by contacting us at
+thoth.tech.deakin@gmail.com. We take privacy concerns seriously and will respond promptly to address
+your complaint.
+
+---
+
+## 8. Cross-Border Disclosure
+
+While we primarily store data within Australia, there may be circumstances where data needs to be
+disclosed to recipients in other countries, such as when using international cloud storage
+providers, analytics tools like Google Analytics, or engaging overseas-based technical support. If
+such disclosure is necessary, we will inform you where practical and take all reasonable steps to
+ensure that your personal information is handled securely and in accordance with the Australian
+Privacy Principles (APPs), including ensuring that overseas recipients provide similar privacy
+protections.
+
+---
+
+## 9. Security Disclaimer
+
+While we strive to protect your data using robust security measures, it is important to note that
+transmissions over the internet are not entirely secure and may be subject to risks beyond our
+control. Although we take all reasonable steps to safeguard your information, we cannot guarantee
+absolute security during transmission and disclaim liability for any data breaches caused by factors
+such as cyberattacks, technical failures, or other circumstances beyond our direct control.
+
+---
+
+## 10. Childrenβs Privacy
+
+We do not knowingly collect personal data from children under 13 without verifiable parental
+consent. If we become aware that we have inadvertently collected personal information from a child
+under 13 without such consent, we will take immediate steps to delete the information from our
+records. Parents or guardians who believe their child has provided us with personal information
+without their consent are encouraged to contact us so we can promptly address the issue
+
+---
+
+## 11. Updates to This Policy
+
+This Privacy Policy may be updated periodically to reflect changes in our practices or Australian
+legal requirements. The latest version will always be available on our website.
+
+---
+
+For further information or inquiries, please contact us at thoth.tech.deakin@gmail.com.
diff --git a/src/content/docs/Resources/remote-working-guide.md b/src/content/docs/Resources/remote-working-guide.md
new file mode 100644
index 00000000..5d1c3bca
--- /dev/null
+++ b/src/content/docs/Resources/remote-working-guide.md
@@ -0,0 +1,101 @@
+---
+title: Remote Working Guide
+sidebar:
+ label: Remote Working Guide
+---
+
+As remote working becomes the norm at Thoth Tech, itβs crucial to be aware of the cyber risks
+associated with it. This guide provides an overview of these risks and offers strategies to create a
+secure remote working environment. By following these best practices, Thoth Tech members can enhance
+their cyber security posture and stay vigilant against potential threats.
+
+## Table of Contents
+
+- [Associated Risks](#associated-risks)
+ - [Reduced Cyber Security Protections](#reduced-cyber-security-protections)
+ - [Accessing Insecure Networks](#accessing-insecure-networks)
+ - [Shared Computers](#shared-computers)
+ - [Reduced Cyber Security Resilience](#reduced-cyber-security-resilience)
+- [Mitigation Strategies](#mitigation-strategies)
+- [Useful Cyber Security Resources](#useful-cyber-security-resources)
+
+---
+
+## Associated Risks
+
+Remote working often involves using personal devices and home networks, which can introduce various
+cyber risks. Understanding these risks is the first step towards mitigating them.
+
+### Reduced Cyber Security Protections
+
+Office environments typically have robust security measures such as antivirus software, intrusion
+detection systems, and file encryption. In contrast, remote setups may lack these protections unless
+individually implemented. This disparity can increase vulnerability to cyber threats.
+
+### Accessing Insecure Networks
+
+Unlike office networks, which are secure and controlled, remote workers often connect through home
+or public Wi-Fi networks. These networks may have minimal security, especially free public Wi-Fi,
+increasing the risk of data breaches and cyber attacks.
+
+### Shared Computers
+
+Using a shared computer for work poses risks such as unauthorised access to data, accidental file
+deletion, or malicious tampering. This risk is heightened if multiple users share the same account
+on a single device.
+
+### Reduced Cyber Security Resilience
+
+Remote work environments can reduce vigilance against cyber threats. Without the immediate oversight
+of an office setting, individuals might be less cautious, making them more susceptible to attacks.
+Additionally, remote workers might lack clear escalation procedures in the event of a security
+incident.
+
+## Mitigation Strategies
+
+Implementing effective practices can significantly reduce cyber risks associated with remote
+working. Here are key strategies:
+
+- **Regular Data Backups:** Regularly back up your data to restore it in case of a security incident
+ or data breach.
+
+- **Up-to-Date Antivirus Software:** Install and maintain active antivirus software to protect
+ against various cyber threats. Some antivirus programs also offer file encryption.
+
+- **Automatic Software Updates:** Ensure that all software and device firmware are kept up-to-date
+ to benefit from the latest security patches and improvements.
+
+- **Strong Password Practices:** Use strong, unique passwords for all accounts, including cloud
+ services and third-party applications. Consider using a password manager.
+
+- **Secure Internet Connections:** Avoid using public or unsecured networks. Always connect through
+ a secure, private network.
+
+- **Sign Out of Shared Devices:** Always log out of your accounts on shared devices to prevent
+ unauthorised access or data manipulation.
+
+- **Cyber Security Awareness:** Continuously educate yourself about cyber threats and security
+ practices through reputable sources and training resources.
+
+These practices not only protect company data but also safeguard your personal information from
+cyber threats.
+
+## Useful Cyber Security Resources
+
+The Australian Cyber Security Centre (ACSC) provides valuable resources to enhance your cyber
+security knowledge and readiness. Visit the [ACSC website](https://www.cyber.gov.au/) for
+comprehensive information on cyber threats and protective measures. Key resources include:
+
+- **Learning Resources:** Explore the [ACSC learning resources](https://www.cyber.gov.au/learn) to
+ improve your cyber awareness and learn about effective protection strategies.
+
+- **Phishing Quiz:** Test your ability to identify phishing emails with the
+ [ACSC phishing quiz](https://www.cyber.gov.au/protect-yourself/spotting-scams#sts--container),
+ which offers insights into recognising scams.
+
+- **Cyber Security Reports:** Review the
+ [ACSC Cyber Security Reports](https://www.cyber.gov.au/about-us/view-all-content/reports-and-statistics)
+ for an overview of Australia's cyber threat landscape and annual security insights.
+
+By staying informed and proactive, Thoth Tech members can effectively manage remote work risks and
+maintain a secure working environment.
diff --git a/src/content/docs/Resources/thoth-tech-technology-stack.md b/src/content/docs/Resources/thoth-tech-technology-stack.md
new file mode 100644
index 00000000..8380205b
--- /dev/null
+++ b/src/content/docs/Resources/thoth-tech-technology-stack.md
@@ -0,0 +1,181 @@
+---
+title: Thoth Tech Technology Stack
+---
+
+This document outlines the technology stack used across all products at Thoth Tech Company. It
+highlights the various technologies employed, as well as the skills required for those interested in
+joining a product team.
+
+---
+
+## Company Leadership
+
+### Tools
+
+- **GitHub**: A platform for hosting and collaborating on code, offering version control and source
+ code management.
+- **Planner**: A task management tool used for organising and tracking team tasks, projects, and
+ deadlines.
+
+### Languages
+
+- **Markdown**: A lightweight markup language used for formatting text and creating structured
+ documents.
+- **TypeScript**: A typed superset of JavaScript that enhances code reliability and scalability in
+ frontend development.
+- **Tailwind CSS**: A utility-first CSS framework for building custom designs without leaving the
+ HTML.
+- **Python**: A versatile programming language used for scripting, automation, and data analysis.
+- **Astro**: A modern static site generator that offers a fast and optimised way to build websites.
+
+### Software
+
+- **Microsoft Teams**: A comprehensive communication and collaboration platform that integrates
+ chat, video conferencing, file storage, and application integration.
+- **Visual Studio Code**: A powerful code editor that supports multiple programming languages,
+ debugging, and extensions.
+- **Astro Starlight**: A documentation site framework that provides a customisable and performant
+ way to create and manage documentation.
+- **Netlify**: A cloud-based platform for hosting web projects, offering continuous deployment and
+ serverless backend services.
+
+### Skills Required
+
+- **Leadership and Collaboration**: Essential for guiding teams, fostering a collaborative
+ environment, and ensuring effective communication.
+- **Creativity and Innovation**: Important for generating new ideas and improving existing products
+ and processes.
+- **Proficiency in TypeScript, Tailwind CSS, and Python**: Key technical skills for frontend
+ development and scripting tasks.
+- **Strong Project Management**: Crucial for planning, organising, and managing resources to achieve
+ project goals efficiently.
+- **Data Science Knowledge**: Valuable for analysing data, extracting insights, and supporting
+ data-driven decision-making.
+
+---
+
+## OnTrack
+
+### Tools
+
+- **GitHub**: Source code management and version control platform, facilitating collaboration on
+ projects.
+- **Git**: A distributed version control system that tracks changes in source code during software
+ development.
+- **Planner**: Used for planning, tracking progress, and managing tasks and projects within teams.
+
+### Languages
+
+- **Markdown**: Used for documentation and creating formatted text files.
+- **AngularJS** and **Angular 17**: JavaScript frameworks for building dynamic web applications,
+ with Angular 17 being the latest version using modern TypeScript features.
+- **CoffeeScript**: A language that compiles into JavaScript, used with AngularJS for concise code.
+- **TypeScript**: Enhances JavaScript with static typing, making code more predictable and easier to
+ debug.
+- **HTML** and **SCSS**: Core web technologies for structuring content and styling web pages.
+- **Ruby on Rails Grape**: A Ruby framework for building REST-like APIs, offering a lightweight and
+ flexible approach.
+- **Tailwind CSS**: A utility-first CSS framework for creating responsive and custom designs
+ efficiently.
+
+### Software
+
+- **Microsoft Teams**: Facilitates communication and collaboration among team members.
+- **Visual Studio Code**: A versatile code editor with extensive language support and integrated
+ development features.
+- **Docker Desktop**: An application that allows developers to create, deploy, and manage
+ containerised applications.
+- **MariaDB Database**: An open-source relational database management system, used for storing and
+ managing data.
+
+### Skills Required
+
+- **Frontend and Backend Understanding**: Knowledge of both frontend and backend technologies for
+ full-stack development.
+- **Familiarity with GitHub and Visual Studio Code**: Essential for source control and coding.
+- **Proficiency in Angular and TypeScript**: Important for developing robust and maintainable web
+ applications.
+- **Knowledge of HTML, SCSS, and Ruby on Rails Grape**: Necessary for building and styling web
+ interfaces and APIs.
+- **MariaDB Database Experience**: Useful for database design and management.
+- **Adaptability to New Technologies**: Ability to learn and integrate new tools and technologies as
+ needed.
+
+---
+
+## SplashKit
+
+### Tools
+
+- **GitHub**: Platform for hosting and collaborating on SplashKit's source code.
+- **Git**: Version control system for tracking changes in the SplashKit codebase.
+- **GitHub Actions**: CI/CD tool for automating workflows, including testing and deployment.
+- **Planner**: Tool for managing tasks, organising projects, and coordinating work among team
+ members.
+- **Raspberry Pi**: A low-cost, credit-card-sized computer used for running applications and
+ experiments, especially in educational and hobbyist contexts.
+
+### Languages
+
+- **Markdown**: Used for writing documentation and formatting content.
+- **C++** and **C#**: Programming languages used for developing the core components of SplashKit.
+- **Bash Scripts**: Shell scripts used for automating tasks in Linux environments.
+
+### Software
+
+- **Microsoft Teams**: Used for team communication and collaboration.
+- **Visual Studio Code**: The primary code editor for developing SplashKit, offering rich language
+ support and debugging features.
+- **Docker Desktop**: Enables containerisation and easy deployment of applications.
+- **WSL (Windows Subsystem for Linux)**: Provides a Linux environment on Windows, useful for
+ development and testing.
+- **Clockify**: A time tracking tool used for monitoring and reporting work hours.
+- **Astro Starlight**: Used for creating and managing the SplashKit documentation website.
+
+### Skills Required
+
+- **Proficiency in C++ and C#**: Essential for developing and maintaining the SplashKit framework.
+- **Understanding of Linux-based Systems**: Important for working with Raspberry Pi and other
+ Linux-based environments.
+- **Basic Web Development and Design Knowledge**: Useful for contributing to the SplashKit.io
+ website and Starlight documentation.
+- **Ability to Update and Expand SplashKit Library**: Capability to enhance and extend the
+ functionality of the SplashKit library.
+
+---
+
+## CourseFlow
+
+### Tools
+
+- **GitHub**: Repository hosting service for version control and collaboration.
+- **Planner**: Tool for organising tasks, tracking progress, and managing project timelines.
+- **Figma**: A web-based design tool used for creating UI/UX designs and prototypes.
+- **Draw.io (diagrams.net)**: A diagramming tool for creating flowcharts, network diagrams, and
+ other visual content.
+
+### Languages
+
+- **Markdown**: Used for documentation and notes.
+- **Ruby on Rails**: A web application framework that provides structures for a database, web
+ service, and web pages.
+- **TypeScript**: Used for building frontend applications with Angular, providing type safety and
+ code clarity.
+
+### Software
+
+- **Microsoft Teams**: Central hub for team communication and file sharing.
+- **Visual Studio Code**: The code editor of choice for developing CourseFlow applications.
+- **Docker**: Used for containerising applications, ensuring consistency across different
+ development and production environments.
+
+### Skills Required
+
+- **Knowledge of Angular for Frontend Development**: Critical for building and maintaining the user
+ interface of CourseFlow.
+- **Experience in Backend API Creation**: Valuable for developing the backend infrastructure,
+ particularly if familiar with frameworks like Ruby on Rails.
+- **Machine Learning Skills**: Beneficial for implementing features such as course categorisation
+ and personalised learning paths.
+- **Strong Self-Management and Willingness to Learn**: Key attributes for continuous personal and
+ professional growth, especially in a rapidly evolving tech landscape.
diff --git a/src/content/docs/Resources/writing-style-guide.md b/src/content/docs/Resources/writing-style-guide.md
new file mode 100644
index 00000000..6769c489
--- /dev/null
+++ b/src/content/docs/Resources/writing-style-guide.md
@@ -0,0 +1,310 @@
+---
+title: Writing Style Guide
+sidebar:
+ label: Writing Style Guide
+---
+
+This writing style guide is designed to inform decisions when writing on behalf of Thoth Tech. It is
+a live document and ensures consistency across all Thoth Tech communications.
+
+## Key Principles
+
+1. **Know Your Audience**: Tailor your writing to the intended audience's knowledge level and
+ expectations.
+2. **Know Your Purpose**: Understand the intention behind your writing.
+3. **Structure Your Writing**: Organise content logically and coherently.
+4. **Keep It Simple**: Use clear and straightforward language.
+5. **Review and Edit**: Always proofread for clarity, accuracy, and consistency.
+
+## Table of Contents
+
+- [Formatting](#formatting)
+ - [Headings](#headings)
+ - [Subheadings](#subheadings)
+ - [Notes](#notes)
+ - [Hyperlinks](#hyperlinks)
+ - [Lists](#lists)
+ - [Unordered/Bullet List](#unorderedbullet-list)
+ - [Ordered/Numbered List](#orderednumbered-list)
+ - [Text Formatting](#text-formatting)
+ - [Numbers](#numbers)
+ - [Sentences](#sentences)
+- [Writing](#writing)
+ - [Acronyms](#acronyms)
+ - [Capitalisation](#capitalisation)
+ - [Verbs](#verbs)
+ - [Active Voice](#active-voice)
+ - [Avoid Nominalisation](#avoid-nominalisation)
+ - [Punctuation](#punctuation)
+ - [Avoid Using Contractions](#avoid-using-contractions)
+ - [Tone](#tone)
+ - [Voice](#voice)
+- [Types of Writing](#types-of-writing)
+ - [Technical Content](#technical-content)
+ - [Code Examples](#code-examples)
+
+---
+
+## Formatting
+
+### Headings
+
+Headings should be clear and concise, with all content relating to the heading or linking to
+relevant information. Avoid using question formats for article headings. Use `h1` (#) for main
+headings.
+
+#### Example
+
+> **Creating a New Project**
+
+---
+
+### Subheadings
+
+Subheadings highlight specific sections and should not exceed three hierarchical layers. Use `h2`
+(##) or `h3` (###) depending on the level.
+
+#### Example
+
+> **Setting Up Your Environment**
+
+---
+
+### Notes
+
+Use notes for supplementary information necessary for understanding but outside the main content
+scope. Keep them brief and to the point, with optional links for further reading.
+
+#### Example
+
+> **Note:** Remember to save your work frequently to avoid data loss.
+
+---
+
+### Hyperlinks
+
+Use hyperlinks to connect readers to additional relevant information when content is beyond the
+scope of the current article. For example:
+
+#### Example
+
+> One reference for Australian spelling is the
+> [Macquarie Dictionary](https://www.macquariedictionary.com.au/).
+
+---
+
+### Lists
+
+Begin lists with a colon (:) and follow specific punctuation rules based on whether items are full
+sentences or fragments.
+
+#### Example
+
+> Essential features include:
+>
+> - Flexibility
+> - Reliability
+> - User-friendliness
+
+#### Unordered/Bullet List
+
+Use unordered lists for items without a specific order. Begin with a dash (-) and avoid punctuation
+unless the items are full sentences.
+
+#### Example
+
+> - Flexible
+> - Reliable
+> - User-friendly
+
+#### Ordered/Numbered List
+
+Use ordered lists for steps or items that follow a specific sequence. Number each item and ensure
+proper punctuation for complete sentences.
+
+#### Example
+
+> 1. Open the application.
+> 2. Select 'File' from the menu.
+> 3. Click 'Save As'.
+
+---
+
+### Text Formatting
+
+- _Italics_: Titles, legislation, or user input.
+- **Bold**: Emphasis.
+- **_Bold and Italics_**: Combined emphasis.
+
+#### Example
+
+> This feature is **essential** for a positive _SplashKit_ user experience.
+
+---
+
+### Numbers
+
+- Write out numbers one through nine; use numerals for 10 and above.
+- Use commas for clarity in large numbers (e.g., 25,000).
+
+#### Example
+
+> The system processes three datasets daily and can handle up to 15,000 requests per second.
+
+---
+
+### Sentences
+
+Keep sentences concise, with an average length of 15-20 words, and a maximum of 25 words. Avoid
+redundancy and ensure clarity.
+
+#### Example (too long)
+
+> The application, which was developed over a period of three years by a team of skilled developers
+> and designers, incorporates a wide range of features that are intended to enhance user experience
+> and improve overall functionality, making it one of the most comprehensive and user-friendly tools
+> available on the market today.
+
+**Explanation:** This sentence is too long, making it difficult to follow.
+
+#### Revised Example
+
+> The application was developed over three years by a skilled team. It includes features to enhance
+> user experience and improve functionality, making it one of the most comprehensive and
+> user-friendly tools available.
+
+---
+
+## Writing
+
+### Acronyms
+
+Spell out terms on first use, followed by the acronym in parentheses. Use the acronym alone
+thereafter.
+
+#### Example
+
+> This is the Quality Assurance (QA) process. For all QA-related tasks, refer to the following
+> guidelines.
+
+---
+
+### Capitalisation
+
+Use capital letters for proper nouns. Follow sentence case for all writing, including headings.
+
+#### Example
+
+> The team will visit Melbourne next month.
+
+---
+
+### Verbs
+
+Write verbs in the present tense and maintain consistency throughout.
+
+#### Example
+
+> The system processes data efficiently.
+
+---
+
+### Active Voice
+
+Prefer active voice for clarity and simplicity. Use passive voice only when necessary, such as for
+feedback or preserving relationships.
+
+#### Example (Active)
+
+> The developer fixed the bug.
+
+#### Example (Passive)
+
+> The bug was fixed by the developer.
+
+---
+
+### Avoid Nominalisation
+
+Avoid converting verbs into nouns, as this can make writing cumbersome.
+
+#### Example
+
+> Instead of "The implementation of the feature was successful," use "The team successfully
+> implemented the feature."
+
+---
+
+### Punctuation
+
+| Symbol Name | Symbol | Main Use |
+| ---------------- | ------ | ---------------------------------------------------- |
+| Full Stop | . | End a statement or command |
+| Question Mark | ? | End a direct question |
+| Exclamation Mark | ! | Express emotion |
+| Comma | , | Separate words and groups of words |
+| Colon | : | Introduce more information |
+| Dash | β | Informal colon or additional information |
+| Parentheses | () | Enclose supplementary information |
+| Brackets | [] | Enclose words added by someone other than the author |
+| Apostrophe | ' | Show possession or contraction |
+| Hyphen | - | Join words |
+| Quotation Marks | "" | Enclose spoken words |
+
+---
+
+### Avoid Using Contractions
+
+Write out full words to maintain a formal tone. Avoid contractions to ensure clarity.
+
+#### Example
+
+> **Incorrect:** The user's guide can't be accessed online. **Correct:** The user's guide cannot be
+> accessed online.
+
+---
+
+### Tone
+
+Use a conversational tone, be brief, and direct. Avoid unnecessary words and contractions. Use the
+Oxford comma.
+
+#### Example
+
+> You can find the instructions in the user manual.
+
+---
+
+### Voice
+
+Use the second person (e.g., "You go to the library").
+
+#### Example
+
+> You should update the software regularly.
+
+---
+
+## Types of Writing
+
+### Technical Content
+
+Technical content should include a table of contents, revision date, and version ID. Tailor it to
+the reader's skill level, and define technical terms clearly.
+
+#### Example
+
+> **Revision Date:** July 2024 **Version ID:** 1.0.0
+
+---
+
+### Code Examples
+
+Provide clear and concise examples for key development tasks. Ensure code is easy to replicate and
+follows best practices.
+
+#### Example
+
+```python
+print("Hello, world!")
+```
diff --git a/src/content/docs/Teams and Contributions/2023 Trimester 2/company-structure-and-objectives-t2-2023.md b/src/content/docs/Teams and Contributions/2023 Trimester 2/company-structure-and-objectives-t2-2023.md
new file mode 100644
index 00000000..3231d617
--- /dev/null
+++ b/src/content/docs/Teams and Contributions/2023 Trimester 2/company-structure-and-objectives-t2-2023.md
@@ -0,0 +1,75 @@
+---
+title: Company Structure and Objectives for 2023 TRIMESTER 2
+description: 2.1P Task, T2 2023
+---
+
+## Executive Summary
+
+Thoth Tech is a software development company currently building from the ground up in Melbourne,
+Australia. Thoth Techβs mission is to build, operate, and deploy education technologies creating
+tools that enhance education outcomes by empowering students, connecting them with tutors, and
+facilitating personalised learning experiences.
+
+We value our people, and we value excellence. We are people-focused, aiming to produce sustainable
+products of excellent quality, and provide frameworks that supply a safe environment for learning
+and support of our team. This report is for stakeholders and investors, and will outline the company
+structure, charter, objectivesβboth short and long term, and explore each productβs goals.
+
+Thoth Tech has recruited approximately 63 employees with 5 product leads. Thoth Tech currently runs
+with five products OnTrack, Courseflow, Splash Kit Courseflow, and Company Operations. The
+additional projects give a bit more variety to the technology stacks currently in use and ties in
+nicely with some existing units that students are working on.
+
+Company Operations oversees the entire affairs of Thoth Tech and strives to make things easier.
+Effective operations are important for maintaining a successful business. As other product teams
+focus to develop new features and upgrade existing products, we would be working to ensure that
+appropriate industry guidelines and standards are followed to produce world class products. We
+document the tools and processes that Thoth tech uses in its daily operations and research new
+options that could serve the company better.
+
+OnTrack is one of the bigger projects in the company and is a live production system that is in use
+at Deakin University, it has been consistently improved and built upon to provide an exceptional
+learning tool for students and staff at Deakin. Its technology stack consists of a Ruby on Rails
+back end and an Angular JS / Angular 15 front end. There are a variety of projects to enhance and
+upgrade this product that students can work on.
+
+CourseFlow is a Thoth Tech product that was founded in T1 2023. It aims to assist students and
+course directors in course planning and in comprehending the requirements of certain courses. It
+does this by giving users a way to generate a personalized course map that meets the requirements of
+their course and by providing a tool that allows users to view the requirements of all units (such
+as prerequisite units) visually.
+
+SplashKit is currently a 2D game development Software Development Kit used to teach object-oriented
+coding to beginners. It has been identified that SplashKit can be expanded to explore other areas
+and languages.
+
+The Art Gallery Project is a new project that has been added in T1 2023, it is a web-based API back
+end written in .NET 7 and C# on a PostgreSQL database and a Vue front end that was developed by
+several students and a lecturer. The aim is to provide a system to track and sell Art works in
+smaller communities.
+
+## Leadership Team
+
+### Company Directors
+
+- Andrew Cain, Managing Director
+- Glory Lee, Managing Director
+
+### Student Leadership
+
+- Daniel Maddern β Product Lead for OnTrack
+- Daniel Maddern & Chloe Hulme β Product Lead for Art Gallery
+- Mel David Bugay & Kieron Anthony Boyle β Product Leads for Courseflow
+- Phil Williams β Product Lead for Splash Kit
+- Onyedikachi Okorie - Product Lead for Company Operations
+
+## Roles and Responsibilities
+
+
+
+| Roles | Description | Responsibilities | Skills |
+| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Managing Director | The role of the managing director is to oversee the Thoth Tech company executive leadership team to ensure they are running the company effectively and value is being added to the Thoth Tech products by the projects they are supporting. |
- Provide guidance to executive leadership team.
- Provide high-level vision for the ongoing goals of the company
- Provide a consistent company strategy due to low retention
|
- Leadership
- Communication
- Mentor
- Decision-making
|
+| Product Lead | The role of the Product lead is to lead and support delivery leads in projects related to their product to ensure ongoing success. |
- Drive the product in the direction determined by the Managing Directors and Area Leads.
- Strong drive towards toward objectives with bias for action
- Proactively identify blockers and opportunities
- Support delivery leads where needed
- Make thoughtful decisions motivated by data and research
- Be transparent and accountable by visualising objectives
|
- Leadership
- Communication
- Empathy
- Interpersonal-Savvy
- Collaborative
- Stakeholder Management
|
+
+
+
| Roles | Description | Responsibilities | Skills |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Managing Director | The role of the managing director is to oversee the Thoth Tech company executive leadership team to ensure they are running the company effectively and value is being added to the Thoth Tech products by the projects they are supporting. |
- Provide guidance to executive leadership team.
- Provide high-level vision for the ongoing goals of the company
- Provide a consistent company strategy due to low retention
|
- Leadership
- Communication
- Mentor
- Decision-making
|
| Product Lead | The role of the Product lead is to lead and support delivery leads in projects related to their product to ensure ongoing success. |
- Drive the product in the direction determined by the Managing Directors and Area Leads.
- Strong drive towards toward objectives with bias for action
- Proactively identify blockers and opportunities
- Support delivery leads where needed
- Make thoughtful decisions motivated by data and research
- Be transparent and accountable by visualising objectives
|
- Leadership
- Communication
- Empathy
- Interpersonal-Savvy
- Collaborative
- Stakeholder Management
|
| Delivery Lead/Senior Student | The role of the Delivery lead is to lead, organise and support their project teams to ensure ongoing success. |
- Establish a team cadence
- Build rapport with all team members to foster a cohesive and collaborative environment
- Strong drive towards objectives with bias for action.
- Proactively identify blockers and opportunities
|
- Leadership
- Communication
- Empathy
- Interpersonal-Savvy
- Collaborative
- Stakeholder Management
|
| Team Member | The role of all team members is to contribute to their respective products/projects. Take the initiative in finding work and solving problems, as well as to communicate with the Seniors about their progress and issues. |
- Work with the project leads to meet the goals for this trimester.
- Attend to assigned tasks in a timely manner.
- Work in collaboration with other team members to produce a viable product.
|
- Technical skills as per project
- Team collaboration
- Competence in GitHub
- Time Management
- Knowledge of Agile model
|
+
+
QUINN CURTIS
| create blog page for the documentation website
| [https://github.com/thoth-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/17) [tech/ThothTech-Documentation-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/17)
[Website/pull/17](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/17)
|
+| QUINN CURTIS
| create written tutorial for the blog
| [https://github.com/thoth-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/17) [tech/ThothTech-Documentation-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/17)
[Website/pull/17](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/17)
|
+| QUINN CURTIS
| created video tutorial for the blog
| [https://github.com/thoth-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/17) [tech/ThothTech-Documentation-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/17)
[Website/pull/17](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/17)
|
+| Karl Ivan Aquino
| Create a Documentation on How to
Publish an Astro Website to Netlify
| |
+| Karl Ivan Aquino
| Testing the Documentation on How
to Publish an Astro Website to Netlify
| |
+| Karl Ivan Aquino
| Create a Netlify Account Using
Andrews Details
| |
+| Karl Ivan Aquino
| Create a Worklog to be adopted by the Company
| [https://github.com/thoth-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/16) [tech/ThothTech-Documentation-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/16)
[Website/pull/16](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/16)
|
+| Onyedikachi
Okorie
| Populate Trello board with tasks to
be done in Sprint 1
| [https://github.com/thoth-tech/Company-](https://github.com/thoth-tech/Company-Operations/pull/26)
[Operations/pull/26](https://github.com/thoth-tech/Company-Operations/pull/26)
|
+| Onyedikachi Okorie
| Help Hub Session to answer questions and direct teammates on
how to Contribute effectively
| [https://github.com/thoth-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/15) [tech/ThothTech-Documentation-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/15)
[Website/pull/15](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/15)
|
+| Onyedikachi Okorie
| Create a Spike Plan for the Thoth Website
| [https://github.com/thoth-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/9)
[tech/ThothTech-Documentation-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/9) [Website/pull/9](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/9)
|
+| Onyedikachi Okorie
| Create "Contributing to Thoth Tech in T3" document.
| [https://github.com/thoth-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/8) [tech/ThothTech-Documentation-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/8)
[Website/pull/8](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/8)
|
+| Onyedikachi Okorie | Company Wide Meeting to Inform Students of our Processes, Policies, etc. | Recording Link: https://deakin365- my.sharepoint.com/:v:/g/personal/s22146 0489_deakin_edu_au/EcIf- j14U_tEoNb7gBdoeKsBBSB_tAY2HNTFSjQ
NkIi5mQ
|
+| Onyedikachi Okorie | Create a Welcome Message for the start of Trimester 3 | Message link: ONYEDIKACHI OKORIE: Welcome to Thoth tech |
+| Onyedikachi Okorie
| Create a Commitment Participant Contract for Thoth Tech
| [https://github.com/thoth-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/10) [tech/ThothTech-Documentation-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/10)
[Website/pull/10](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/10)
|
+| Onyedikachi Okorie
| Compile and Submit 2.1P Task for Company Wide Submission
| Teams link: Thoth Tech Company
Objectives and Structure T32023 -Task 2.1P.pdf
|
+| Onyedikachi
Okorie
| Build the Company Website Home
Page, Nav Bar and Footer
| [https://github.com/thoth-tech/Company-](https://github.com/thoth-tech/Company-Website/pull/1)
[Website/pull/1](https://github.com/thoth-tech/Company-Website/pull/1)
|
+| Onyedikachi
Okorie
| Build the Blog Pages of the
Company Website
| [https://github.com/thoth-tech/Company-](https://github.com/thoth-tech/Company-Website/pull/2)
[Website/pull/2](https://github.com/thoth-tech/Company-Website/pull/2)
|
+| Onyedikachi
Okorie
| Build the OnTrack Page of the
Company Website
| [https://github.com/thoth-tech/Company-](https://github.com/thoth-tech/Company-Website/pull/2)
[Website/pull/2](https://github.com/thoth-tech/Company-Website/pull/2)
|
+| Onyedikachi
Okorie
| Generate an astro template for the
creation of the company website
| [https://github.com/thoth-tech/Company-](https://github.com/thoth-tech/Company-Website/pull/1)
[Website/pull/1](https://github.com/thoth-tech/Company-Website/pull/1)
|
+| Onyedikachi Okorie
| Create a Low-level Prototype Design for Thoth Tech Website
| [https://github.com/thoth-](https://github.com/thoth-tech/ThothTech-Documentation-Website/commit/b392f554a2780c786f111b7b93313a7c9b297619) [tech/ThothTech-Documentation-](https://github.com/thoth-tech/ThothTech-Documentation-Website/commit/b392f554a2780c786f111b7b93313a7c9b297619)
[Website/commit/b392f554a2780c786f111](https://github.com/thoth-tech/ThothTech-Documentation-Website/commit/b392f554a2780c786f111b7b93313a7c9b297619) [b7b93313a7c9b297619](https://github.com/thoth-tech/ThothTech-Documentation-Website/commit/b392f554a2780c786f111b7b93313a7c9b297619)
|
+| Devanshi Patel
| Compile a list all Technology Stacks for Thoth Tech
| [https://github.com/thoth-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/21) [tech/ThothTech-Documentation-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/21)
[Website/pull/21](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/21)
|
+| SHIYU CHEN
| Create an Org Chart for T3
| [https://github.com/thoth-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/11) [tech/ThothTech-Documentation-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/11)
[Website/pull/11](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/11)
|
+| SHIYU CHEN
| Migrate all Coursefow documentation to the
Documentation Website
| [https://github.com/thoth-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/11) [tech/ThothTech-Documentation-](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/11)
[Website/pull/11](https://github.com/thoth-tech/ThothTech-Documentation-Website/pull/11)
|
+| SHIYU CHEN
| Review the folders in Courseflow determine which folder they fall under (Projects, Documentation,
Issues and Resolution)
| |
+| ZHENJIE LAI
| Migrate all Art Gallery documentation to the Documentation Website
| [https://github.com/Eisen666/ThothTech-](https://github.com/Eisen666/ThothTech-Documentation-Website/tree/upstream/Eisen-new-artgallery) [Documentation-](https://github.com/Eisen666/ThothTech-Documentation-Website/tree/upstream/Eisen-new-artgallery) [Website/tree/upstream/Eisen-new-](https://github.com/Eisen666/ThothTech-Documentation-Website/tree/upstream/Eisen-new-artgallery)
[artgallery](https://github.com/Eisen666/ThothTech-Documentation-Website/tree/upstream/Eisen-new-artgallery)
|
+| ZHENJIE LAI
| Review the folders in Art Gallery determine which folder they fall under (Projects, Documentation,
Issues and Resolution)
| [https://github.com/Eisen666/ThothTech-](https://github.com/Eisen666/ThothTech-Documentation-Website/tree/upstream/Eisen-new-artgallery) [Documentation-](https://github.com/Eisen666/ThothTech-Documentation-Website/tree/upstream/Eisen-new-artgallery) [Website/tree/upstream/Eisen-new-](https://github.com/Eisen666/ThothTech-Documentation-Website/tree/upstream/Eisen-new-artgallery)
[artgallery](https://github.com/Eisen666/ThothTech-Documentation-Website/tree/upstream/Eisen-new-artgallery)
|
+
+### OnTrack
+
+#### Ontrack Overview, Goals, and Objectives
+
+This trimester Ontrack will be working dynamically across a variety of projects. We will be working
+based on a priority system to get as many useful changes implemented as possible in the trimester.
+
+We will be breaking each project into smaller subcomponents to allow people to work across projects
+in areas that are strong at or interested in. Everything should be completable in a 2- week sprint.
+
+#### OnTrack Aims for Trimester
+
+The Key projects we would like to see movement on this trimester would be:
+
+1. Improvements Backlog β This backlog has core improvements to the system we want to see.
+2. Ontrack Bugs Backlog β These are bugs that are found and added to this backlog.
+3. New Feature β Incorporate Content β Ideally, we have an additional 2 designs of how this would
+ work. It's not ready to code just yet.
+4. New Feature β Staff Grant Extensions β Ideally, we have an additional 2 designs of how this would
+ work. It's not ready to code just yet.
+
+5. New Feature β Tutor Times β Ideally, we have 2 additional designs on how this would work. It's
+ not ready to code just yet.
+6. Backlog Urgent Enhancements β These are important changes we are looking to get done as soon as
+ possible.
+7. Documentation β We want to focus on updating the Front and Backend Documentation and testing in
+ this trimester. This will help students and other users better understand the system and how it
+ works.
+
+#### OnTrack Deliverables
+
+Our main deliverables will be based on story points completed in the Trello tasks; we are aiming for
+students to complete between 5-6 Story points every 2-week sprint.
+
+### OnTrack Description of Progress
+
+#### Front end migration
+
+- 2 migrations in final review
+- 6 in first stage review
+- 1 major component being migrated
+
+#### Urgent Enhancements
+
+- codespace investgiation complete
+- Sidekick investigation
+
+#### Numbas
+
+- group formed to progress Numbas
+- Meeting to plan remaining work
+
+#### OnTrack Team Members and Contributions
+
+| Full Name | Trello Card Name | Evidence |
+| :-------------------------------------- | :--------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Brian Caldera
| Replace fx-layout with tailwind equivalent -
hero-sidebar
|
|
+| Brian Caldera
| Replace fx-layout with tailwind equivalent -
welcome
|
|
+| William Lowe
| Replace fx-layout with tailwind equivalent - hero-sidebar |
|
+| William Lowe
| Replace fx-layout with
tailwind equivalent - welcome
|
|
+| William Lowe
| Replace fx-layout with tailwind equivalent -
unit-dropdown
|
|
+| MINH THO DUONG
| Replace fx-layout with tailwind equivalent -
footer
| [https://github.com/thoth-tech/doubtfire-web/pull/107](https://github.com/thoth-tech/doubtfire-web/pull/107)
|
+| MINH THO DUONG
| Replace fx-layout with tailwind equivalent -
inbox-comment
| [https://github.com/s223749059/doubtfire-](https://github.com/s223749059/doubtfire-web/commit/f0c132a9b416e8b04f4573740190e5f47b9bd6c5) [web/commit/f0c132a9b416e8b04f4573740190e5f47b9bd6c5](https://github.com/s223749059/doubtfire-web/commit/f0c132a9b416e8b04f4573740190e5f47b9bd6c5)
|
+| MINH THO DUONG
| Replace fx-layout with tailwind equivalent -
user-badge
| [https://github.com/thoth-tech/doubtfire-web/pull/109](https://github.com/thoth-tech/doubtfire-web/pull/109)
|
+| MINH THO DUONG
| Replace fx-layout with tailwind equivalent -
staff-task-list
| [https://github.com/s223749059/doubtfire-](https://github.com/s223749059/doubtfire-web/commit/0c1ad0e7a5321c078f5ef44c32908d2363d08df8) [web/commit/0c1ad0e7a5321c078f5ef44c32908d2363d08df8](https://github.com/s223749059/doubtfire-web/commit/0c1ad0e7a5321c078f5ef44c32908d2363d08df8)
|
+| Satika Jayawardena
| Replace fx-layout with tailwind equivalent -
footer
| [https://github.com/thoth-tech/doubtfire-web/pull/107](https://github.com/thoth-tech/doubtfire-web/pull/107)
|
+| Satika Jayawardena
| Replace fx-layout with tailwind equivalent -
unit-dropdown
| [https://github.com/thoth-tech/doubtfire-web/pull/108](https://github.com/thoth-tech/doubtfire-web/pull/108)
|
+| Satika Jayawardena
| Replace fx-layout with tailwind equivalent -
task-comment- composer
| [https://github.com/thoth-tech/doubtfire-web/pull/120](https://github.com/thoth-tech/doubtfire-web/pull/120)
|
+| Satika Jayawardena
| Replace fx-layout with tailwind equivalent -
user-badge
| [https://github.com/thoth-tech/doubtfire-web/pull/109](https://github.com/thoth-tech/doubtfire-web/pull/109)
|
+| Katrine Chan
| Update Contract for
doing more
| [https://github.com/Katrine-Chan/ThothTech-Documentation-](https://github.com/Katrine-Chan/ThothTech-Documentation-Website/commit/03b6d791d4dac3943167d4dc5fbace4fe43eba90)
[Website/commit/03b6d791d4dac3943167d4dc5fbace4fe43eba90](https://github.com/Katrine-Chan/ThothTech-Documentation-Website/commit/03b6d791d4dac3943167d4dc5fbace4fe43eba90)
|
+| Syed Yahyya Hashmi
| Replace fx-layout with tailwind equivalent - task-comment-
composer
| [https://github.com/thoth-tech/doubtfire-web/pull/120](https://github.com/thoth-tech/doubtfire-web/pull/120)
|
+| YUHENG WANG
| Replace fx-layout with tailwind equivalent -
calendar-modal
| [https://github.com/AusBruce/doubtfire-](https://github.com/AusBruce/doubtfire-web/commit/6cb60744135dda3d5deda9ee159a6348adfc001a) [web/commit/6cb60744135dda3d5deda9ee159a6348adfc001a](https://github.com/AusBruce/doubtfire-web/commit/6cb60744135dda3d5deda9ee159a6348adfc001a)
|
+| Aidan Debernardi
| Replace fx-layout with tailwind equivalent - task-assessment-
comment
| [https://github.com/thoth-tech/doubtfire-web/pull/119](https://github.com/thoth-tech/doubtfire-web/pull/119)
|
+
+### Courseflow
+
+#### Courseflow Overview, Goals, and Objectives
+
+CourseFlow aims to assist students in planning and comprehending the requirements and structuring of
+university courses. Users can generate and adjust their CourseMap to account for changes. For
+instance, a student will be able to see their expected graduation date or complications that may
+arise if they complete units in a particular order or study load.
+
+#### Courseflow Aims for Trimester
+
+- Create a detailed design for the project.
+- Create a document that justifies the need for the Courseflow product.
+- Generate a project roadmap
+- Begin implementation on approved designs.
+
+#### Courseflow Deliverables
+
+The main deliverable is to produce a detailed design and structured roadmap for Courseflow by the
+end of trimester 3.
+
+#### Courseflow Description of Progress
+
+1. **CourseFlow Software Design Document**
+ - Analysed previous work done for CourseFlow.
+ - Re-designed CourseFlow based on analysis and re-established requirements and created a software
+ design document.
+ - After first review, updated software design document to treat CourseFlow as a new feature of
+ OnTrack.
+ - Added an ERD to model the data and their relationships with each other and OnTrack as part of
+ this new update.
+
+2. **University of Melbourne Course Planner Research Document**
+ - Explored the UoM course planner to look at their features.
+ - Analysed data retrieved to see how it is structured for inspiration in CourseFlow's data
+ modelling.
+
+3. Enhancement of the current ERD with further breakdown of the data models.
+
+#### Courseflow Team Members and Contributions
+
+| **Full Name** | **Trello Card Name** | **Evidence** |
+| :------------ | :----------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Mark Enriquez | Create Software Design Documentation Draft | [cmarktopher/ThothTech-Documentation-](https://github.com/cmarktopher/ThothTech-Documentation-Website/tree/CourseFlow-Software-Design-Documentation)
[Website at CourseFlow-Software-Design-](https://github.com/cmarktopher/ThothTech-Documentation-Website/tree/CourseFlow-Software-Design-Documentation) [Documentation (github.com)](https://github.com/cmarktopher/ThothTech-Documentation-Website/tree/CourseFlow-Software-Design-Documentation)
|
+
+### Splash Kit
+
+#### Splash Kit Overview, Goals, and Objectives
+
+Splashkit is an all-purpose toolkit for beginners built in C++ and can be used with C++ and C#.
+Deakin University uses it to introduce students to programming through its easy-to-use functions.
+
+As part of the Splashkit team, you will be responsible for expanding the toolkit functions,
+developing improved and innovative ways of working with Splashkit and creating educational documents
+and videos for students.
+
+#### Splash Kit Aims for Trimester
+
+See Card Status in Backlog for Additional details and Completed Research Cards. The following
+projects and tasks stated below are what we aim to work on this trimester.
+
+#### SplashKit Arcade
+
+- Create an automated game download system for Arcade Machines
+ - The proposed system will use the Arcade-games Repo to check for updates in the game version and
+ download the latest version
+ - Games should have a Publish tag or similar to be loaded to the main menu.
+ - Have a secondary game menu for test games/non-published.
+
+- Updates to Arcade Menu
+ - Presently the Arcade machine uses Emulation Station forked from the RetorPI project version.
+
+ - Create a new system for test games
+ - See if we can modify the EM menu for the following
+ - Trigger Game download scripts
+ - Additional modes
+ - Kiosk β Only show Published Games (for Events)
+ - Normal β Has Published and Test Systems
+ - Via script or other method have games exit after 10 min's if there's been no key Input
+
+- Stretch Goals/Interesting ideas
+ - Consider a local Test Mode β Arcade Switches to AP mode displays connection info (random
+ password) and has a web server student can drop new game build on and tests. The machine Would
+ delete the game and reset after a period of time.
+ - Security would be a big consideration on this idea as it would be easy to abuse and not much
+ in the way of logging vs official upload via Git Hub.
+ - Implement a voting system on the Arcade Machine to give meaning to the star ranking.
+
+ - Arcade Games β GitHub Actions
+ - Correct C# for Arm (this should be done; see [trello card](https://trello.com/c/qeYlMImY) for
+ Status)
+ - Dotnet does not run correctly in the Emulated PI environment used for C++ games. New Action
+ was created for compiling dotnet vs Arm games small bug in checking logic to be fixed before
+ merge.
+ - Update Arcade β Games Readme
+ - Updated Controle to correctly reflect the Arcade machine
+ - Updated on new Compiling Process
+ - Instruct that All Game Assets must go into the Resources Folder (Action does try to capture
+ root directories like images, sound, etc.) This includes level maps etc., or they won't
+ upload to Arcade Machines
+ - Implement Versioning for compiled games.
+ - A simple version file in the games directory receives an incremental bump every time the
+ game is updated so the Arcade knows to get the latest version.
+ - This file can also contain additional information for the Arcade Menu. (Author, Publisher,
+ other)
+ - Retrieve and Compile Games from SubModules
+ - Formalise Process with Deakin Staff on how Students from Classes like SIT102 or SIT771 can
+ upload games to the Arcade Machine
+ - Barrier will be using GitHub for new students, especially as this will use submodules.
+ - Consider creating scripts to automate the linking of sub-modules
+
+ - Move All games to Sub-Modules
+ - Games made by Toth-Tech should be moved to their own repo, (or we can consider a separate
+ Company if we don't want to crowd the Githubn too Much)
+ - This will potentially allow Linking to Other Student Repos.
+
+#### Splashkit Expansion
+
+- Priority Items Deployment Packages
+ - Debian Package.
+ - Nuget Package.
+ - Brew Package.
+
+- Check for Further Functions from [Swin games](https://github.com/macite/swingame)to port into
+ splashkit.
+- Fix Python Compatibility
+ - Python can no longer be used to code games with SplashKit. Previous research indicates a change
+ with v3.8; see
+ [here](https://github.com/thoth-tech/documentation/blob/main/docs/Splashkit/Extensions/Python%20Compatibality/Research%20%26%20Findings/Python%20Changelog.md).
+
+- Look at Adding AI function to SplashKit
+ - Can look at LLMs like ChatGPT
+ - Similar Functions to
+
+- Dev Container Mac
+ - As most SplashKit Programs have a visual component and not browser-based based, we need a way to
+ view the program's window output. This is normally accomplished by xserver forwarding and sound
+ via pulse audio.
+ - Mac xquartz is a xserver compatible with Mac Instaitl Tests container that can be setup and run
+ x based programs e.g. xeyes but there is a compatibility issue with the graphics system in
+ SplashKit. Further investigation is needed.
+
+- SplashKit.io
+ - Publish Astro Starlight site
+ - The Aim will be to convert Splashkit.io to our new webpage platform.
+ - Advise getting a subdomain like new.splashkit.io (or similar) setup for testing, and
+ Transition will just be a DNS change then
+ - Thorough documentation of the new site is needed
+ - The Existing SplashKit.io may have a function to auto-update the API pages based on functions
+ added to SplashKit. This should be investigated and replicated in the new site.
+
+- Game Engine
+ - Project Setup: Create a streamlined project setup process for easier onboarding and development.
+ - Camera System: Implement a flexible and efficient camera system to handle different views and
+ perspectives.
+ - Transforms: Develop a system for handling object transformations like translation, rotation, and
+ scaling.
+ - Event System: Design an event system for handling game events in an extensible manner.
+ - Input Handling System: Implement a robust input handling system to manage user interactions.
+
+- Documentation Migration
+ - As the company is moving to a new documentation repository a data Migration will need to occur
+ between the existing documentation repo and the new one.
+ - Work with company operations to plan the migration, but the SplashKit team needs to move the
+ existing document over (also consider it a good opportunity to clean house and archive older
+ information)
+
+#### SplashKit Tutorials
+
+#### Backlog
+
+- Game Development
+ - High Level Design
+ - Complete Demo Game
+ - 8. Creating a 2D "Metroidvania" Game - Enemies and Combat
+ - 10. Creating a 2D "Metroidvania" Game - Level Design and Progression
+ - 13. Creating a 2D "Metroidvania" Game - Polishing and Finalization
+ - 7. Creating a 2D "Metroidvania" Game - Camera Movement, Parallax and Depth
+
+- Tutorials and Documentation
+ - Understanding SplashKit Manager - (SKM) Shell Commands - Tutorial
+ - Project Structure and Initialization
+
+- Roadmap (Future Plans)
+ - Integrate different stages of "Creating a 2D 'Metroidvania' Game" for cohesiveness and
+ consistency.
+ - Complete remaining tutorials
+ - Plans for new tutorials, ensuring total Splashkit Functionality
+
+#### SplashKit Deliverables
+
+Our main deliverables will be based on story points completed in the Trello tasks; we are aiming for
+students to complete between 5-6 Story points every 2-week sprint.
+
+#### SplashKit Description of Progress
+
+##### Arcade
+
+- New game "Single Combat" (tetris style game) started with completed Design Proposal.
+- Current arcade games being tested for bugs and potential improvements.
+- Changes in progress for Runner Dash and Asteroids.
+- Video created for a tutorial on setting up environment for contributing (SplashKit specific) -
+ currently awaiting mentor review.
+
+##### Tutorials
+
+- Master list of tutorials (created/proposed/needed) created.
+- 1 tutorial awaiting mentor review.
+- 4 tutorials currently in peer review.
+- 3 tutorials in progress.
+
+##### Starlight SplashKit Website
+
+- Emoji's removed (although this was made redundant from upstream changes later on)
+- 3 updates to graphics/functionality/layout awaiting mentor review.
+- Backlog tasks created from pdf provided by upstream development team
+- 3 updates to graphics/functionality/layout in progress.
+
+##### SplashKit Online IDE
+
+- Spike reports on Viability of continuing this project have been completed and approved.
+- 9 updates currently in peer review.
+- 5 updates in progress.
+
+#### **Team Members and Contributions**
+
+| **Full Name** | **Trello Card Name** | **Evidence** |
+| :----------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| BRYAN
TAING
| Create an video ( or series of gifs) to make a tutorial of how to set up git environment for students wishing to contribute to Splash Kit. | |
+| BRYAN
TAING
| Create backlog tasks
| |
+| BRYAN TAING
| Create Design Proposal for Single Combat (tetris
style game)
|
|
+| BRYAN TAING
| Asteroids: Add a sound effect when the ship
crashed into the Asteroid
| |
+| BRYAN TAING
| 7\. Creating a 2D "Metroidvania" Game - Camera Movement,
Parallax and Depth
|
|
+| BRYAN
TAING
| Build an initial list of
tutorials
|
|
+| BRYAN TAING
| Move Installation Guides
section to just above Troubleshooting
|
|
+| BRYAN TAING
| Update Landing Page
Footer and Add Facebook Icon
|
|
+| BRYAN
TAING
| Update some graphics
on the landing page
|
|
+| BRYAN
TAING
| Remove Emoji's from all
parts that have them
|
|
+| Frankie Veri
| Create an video (or series of gifs) to make a tutorial of how to set up git environment for
students wishing to contribute to Splash Kit.
| |
+| Frankie Veri
| Asteroids: Add a sound effect when the ship
crashed into the Asteroid
| |
+| Frankie Veri
| Move Installation Guides
section to just above Troubleshooting
|
|
+| Frankie Veri | Create Backlog tasks | |
+| CASTIEL
MORDRED MCINTOSH
| Develop basic art for Single Combat Game
|
|
+| CASTIEL
MORDRED MCINTOSH
| Create Design Proposal
for Single Combat (tetris style game)
|
|
+| Jaron Chen
| Adding Difficulty settings
to Runner Dash
|
|
+| Jaron Chen
| Test the arcade games for bugs/issues and
potential improvements
|
|
+| Georgie
O'Malley
| Sprite Animation -
Tutorial
|
|
+| Wenzong Xuan
| 2\. Creating a 2D "Metroidvania" Game - Project Structure and
Initialization
|
|
+| Wenzong
Xuan
| Using JSON Files -
Tutorial Proposal
|
|
+| Wenzong Xuan
| 10\. Creating a 2D "Metroidvania" Game - Level Design and
Progression
|
|
+| Wenzong Xuan
| 7\. Creating a 2D "Metroidvania" Game - Camera Movement,
Parallax and Depth
|
|
+| Sean Boettger
| 2\. Creating a 2D "Metroidvania" Game - Project Structure and
Initialization
|
|
+| Sean
Boettger
| Build an initial list of
tutorials
|
|
+| Sean
Boettger
| Add full project
download/upload
|
|
+| Sean
Boettger
| Update SplashKitOnline
Repository Readme
|
|
+| Sean
Boettger
| Fix polling based input
| [https://github.com/WhyPenguins/splashkit-core/tree/fix-](https://github.com/WhyPenguins/splashkit-core/tree/fix-initialization-and-input)
[initialization-and-input](https://github.com/WhyPenguins/splashkit-core/tree/fix-initialization-and-input)
|
+| Sean Boettger
| Add file management/browser
for internal FS
|
|
+| Sean
Boettger
| Formalize make process
for Emscripten port
| [https://github.com/WhyPenguins/splashkit-](https://github.com/WhyPenguins/splashkit-core/tree/emscripten-cmake)
[core/tree/emscripten-cmake](https://github.com/WhyPenguins/splashkit-core/tree/emscripten-cmake)
|
+| Sean
Boettger
| Setup WebIDL binding
| [https://github.com/WhyPenguins/splashkit-](https://github.com/WhyPenguins/splashkit-core/tree/emscripten-webidllibrary)
[core/tree/emscripten-webidllibrary](https://github.com/WhyPenguins/splashkit-core/tree/emscripten-webidllibrary)
|
+| Sean Boettger
| Automate WebIDL binding generation
(prototype level)
| [https://github.com/WhyPenguins/splashkit-](https://github.com/WhyPenguins/splashkit-core/tree/webidlbinding-generation) [core/tree/webidlbinding-generation](https://github.com/WhyPenguins/splashkit-core/tree/webidlbinding-generation)
|
+| Sean Boettger
| Incorporate SplashKit WASM build into
SplashKitOnline
|
|
+| Sean
Boettger
| Add Javascript execution
to SplashKitOnline
|
|
+| Sean Boettger
| Spike Report - Viability of continuing with SplashKit
Online
|
|
+| TAIMING XU
| Update Landing Page Footer and Add
Facebook Icon
|
|
+| TED WANG
| Update some graphics
on the landing page
|
|
+| Ayan
Masood
| Remove Emoji's from all
parts that have them
|
|
diff --git a/src/content/docs/Teams and Contributions/2023 Trimester 3/company-structure-and-objectives-t3-2023.md b/src/content/docs/Teams and Contributions/2023 Trimester 3/company-structure-and-objectives-t3-2023.md
new file mode 100644
index 00000000..a0d821d2
--- /dev/null
+++ b/src/content/docs/Teams and Contributions/2023 Trimester 3/company-structure-and-objectives-t3-2023.md
@@ -0,0 +1,412 @@
+---
+title: Thoth Tech - Company Structure and Objectives for 2023 TRIMESTER 3
+description: 2.1P Task, T3 2023
+---
+
+## Executive Summary
+
+Thoth Tech is a software development company currently building from the ground up in Melbourne,
+Australia.
+
+Thoth Techβs mission is to build, operate, and deploy education technologies, creating tools that
+enhance education outcomes by empowering students, connecting them with tutors, and facilitating
+personalised learning experiences.
+
+We value our people, and we value excellence. We are people-focused, aiming to produce sustainable
+products of excellent quality, and provide frameworks that supply a safe environment for learning
+and support of our team.
+
+This report will outline the company structure, charter, objectivesβboth short and long term, and
+explore each productβs goals.
+
+In trimester 3, Thoth Tech would be running three products namely: OnTrack, Splash Kit, and Company
+Operations. In addition to the three main products, the Courseflow project would undergo a rigorous
+planning phase were the benefits, aims, and solution design would be generated to create a structure
+for the project in subsequent trimesters. Students would be allocated to any of the three products
+and would be required to contribute to achieve the objectives of the product.
+
+Company Operations oversees the entire affairs of Thoth Tech and strives to make things easier.
+Effective operations are important for maintaining a successful business. As other product teams
+focus to develop new features and upgrade existing products, we would be working to ensure that
+appropriate industry guidelines and standards are followed to produce world class products. We
+document the tools and processes that Thoth tech uses in its daily operations and research new
+options that could serve the company better.
+
+OnTrack is one of the bigger projects in the company and is a live production system that is in use
+at Deakin University, it has been consistently improved and built upon to provide an exceptional
+learning tool for students and staff at Deakin. Its technology stack consists of a Ruby on Rails
+back end and an Angular JS / Angular 15 front end. There are a variety of projects to enhance and
+upgrade this product that students can work on.
+
+SplashKit is currently a 2D game development Software Development Kit used to teach object-oriented
+coding to beginners. It has been identified that SplashKit can be expanded to explore other areas
+and languages.
+
+## Leadership Team
+
+### Company Directors
+
+- Andrew Cain, Managing Director
+
+### Mentors
+
+- OnTrack & Courseflow - Daniel Maddern
+- SplashKit β Olivia McKeon
+- Company Operations β Amin Abken
+
+## Trimester Goals and Objectives
+
+Thoth Tech will aim to achieve the goals listed below:
+
+### Goal 1: Foster employees' growth in a safe and supportive environment to equip them with the soft and technical skills needed upon graduation
+
+- Create an environment where the amount of work is distrusted evenly amongst roles and
+ contributors.
+- Utilise processes and tools that require collaboration and fosters growth such as Google Suite or
+ Pull Reviews.
+- Educate and Empower skill growth and knowledge sharing.
+- Enhance onboarding experience for future employees.
+- Ensure a supportive environment is provided for all employees regardless of race, gender or other
+ differences to allow every employee to thrive.
+
+### Goal 2: Extend the Existing Thoth Tech Applications based on the Directorβs Visions
+
+- Improve existing features of the Thoth Tech applications and extend the platforms.
+- Have a mentality of self-improvement and find/squash bugs related to non-technical and technical
+ issues.
+- Maintain security guidelines and industry best standards.
+- Embrace an ethic of communicating with non-technical stakeholders through diagrams and other
+ methods of documentation to help future employees and investors.
+
+### Goal 3: Revise and Maintain Company Operations
+
+- Improve existing company policies based on employee feedback and director advice
+- Educate future employees and develop a process to consider the bus factory
+- Allow company operations to be a smooth process for nurturing new company operation members.
+- Establish documentation and guidelines to allow anyone to understand the company operation.
+
+### Company Charter
+
+The Thoth Tech charter is a crucial tool for guiding our team, navigating decisions, establishing
+boundaries, and aligning the team on how we work together. It defines how as a company we work
+together to achieve success.
+
+Our charter comprises of the following:
+
+1. Mission: As a team, what are we trying to achieve?
+2. Values: What do we care about?
+3. Team Culture: How will we work together, what do we expect?
+4. Roles: What roles do we need and what are the responsibilities of each role?
+5. Metrics of Success: What does success look like to us?
+6. Standards of Quality: What are our standards for high quality work? Mission To build, operate and
+ deploy world class education technologies.
+
+This is achieved by creating tools that enhance education outcomes by empowering students,
+connecting them with tutors and facilitating personalised learning experiences. Values Our values
+describe how we work, what we represent, and guide us to be the kind of company and team members we
+want to be.
+
+When we live up to these values we will: Be people-focused We expect the best from each other, give
+each other the benefit of the doubt, encourage each other to take initiative to improve ourselves
+and the company, and provide direct and constructive help to each other. We collaborate with
+kindness while being respectful of each other. Uphold sustainable excellence We create working,
+maintainable, and understandable software that is enjoyable and easy to use.
+
+We strive to do it in a way that is sustainable for our team members and for our environment. Be
+inclusive and supportive We celebrate diverse perspectives and embrace uncomfortable ideas and
+conversations. We facilitate an environment in which all team members feel psychologically safe
+enough to make requests for what they need to do their job. We learn through failures while
+continually working to make things better.
+
+## Company Structure and Projects Overview
+
+### Company Structure
+
+
+
+### Projects Overview
+
+#### Company Operations
+
+#### Overview, Goals, and Objectives
+
+This team oversees the entire operations of Thoth Tech and strives to make things easier. We aim to
+make the onboarding process as smooth and clear as possible, as well as increase the knowledge of
+our seniors in meaningful ways while creating policies to improve the wellbeing of all company
+employees. In the short term, we would like to create documentations, policies, workflows, and
+processes that are relevant to improve the companyβs outlook and overall productivity. In the long
+term, we aim to ensure that all policies created are being adhered to and the Documentation website
+is being utilized to store all project documentation.
+
+#### Aims for Trimester
+
+- Enforce created policies.
+- Migrate all project documentation to the Documentation website.
+- Dockerize the Documentation website
+- Create a website to showcase Thoth Tech products and projects.
+- Oversee the entire operations of the company.
+
+#### Deliverables
+
+- Design document for Thoth Tech company website.
+- Published company website
+- Docker image for documentation website published to GitHub.
+- Students completely adhere to created policies and guidelines
+
+#### Team Members
+
+| Student Name | Role |
+| -------------------- | ----------- |
+| Jason Galleti | Team Member |
+| Chinonyerem Victoria | Team Member |
+| Shiyu Chen | Team Member |
+| Eisen Lai | Team Member |
+| Frankie Veri | Team Member |
+| Onyedikachi Okorie | Team Member |
+| Quinn Curtis | Team Member |
+| Ivan Aquino | Team Member |
+| Devanshi Patel | Team Member |
+| Ted Wang | Team Member |
+
+### OnTrack
+
+#### Ontrack Overview, Goals, and Objectives
+
+This trimester Ontrack will be working dynamically across a variety of projects. We will be working
+based on a priority system to get as many useful changes implemented as possible in the trimester.
+
+We will be breaking each project into smaller subcomponents to allow people to work across projects
+in areas that are strong at or interested in. Everything should be completable in a 2- week sprint.
+
+#### OnTrack Aims for Trimester
+
+The Key projects we would like to see movement on this trimester would be:
+
+1. Improvements Backlog β This backlog has core improvements to the system we want to see.
+2. Ontrack Bugs Backlog β These are bugs that are found and added to this backlog.
+3. New Feature β Incorporate Content β Ideally, we have an additional 2 designs of how this would
+ work. It's not ready to code just yet.
+4. New Feature β Staff Grant Extensions β Ideally, we have an additional 2 designs of how this would
+ work. It's not ready to code just yet.
+
+5. New Feature β Tutor Times β Ideally, we have 2 additional designs on how this would work. It's
+ not ready to code just yet.
+6. Backlog Urgent Enhancements β These are important changes we are looking to get done as soon as
+ possible.
+7. Documentation β We want to focus on updating the Front and Backend Documentation and testing in
+ this trimester. This will help students and other users better understand the system and how it
+ works.
+
+#### OnTrack Deliverables
+
+Our main deliverables will be based on story points completed in the Trello tasks; we are aiming for
+students to complete between 5-6 Story points every 2-week sprint.
+
+#### OnTrack Team Members
+
+| Student Name | Role |
+| --------------------------- | ----------- |
+| Aidan Debernardi | Team Member |
+| Katrine Kit Chan | Team Member |
+| Minh Tho Duong (Minh Tho) | Team Member |
+| Samadhi Weerasingha (Sam) | Team Member |
+| Brian Caldera | Team Member |
+| Mark Enriquez | Team Member |
+| Syed Yahyya Hashmi (HASHMI) | Team Member |
+| William Lowe (Will) | Team Member |
+| Satika Jayawardena | Team Member |
+| Jayani Vimukthaika | Team Member |
+| Bruce Wang | Team Member |
+
+### Courseflow
+
+#### Courseflow Overview, Goals, and Objectives
+
+CourseFlow aims to assist students in planning and comprehending the requirements and structuring of
+university courses. Users can generate and adjust their CourseMap to account for changes. For
+instance, a student will be able to see their expected graduation date or complications that may
+arise if they complete units in a particular order or study load.
+
+#### Courseflow Aims for Trimester
+
+- Create a detailed design for the project.
+- Create a document that justifies the need for the Courseflow product.
+- Generate a project roadmap
+- Begin implementation on approved designs.
+
+#### Courseflow Deliverables
+
+The main deliverable is to produce a detailed design and structured roadmap for Courseflow by the
+end of trimester 3.
+
+#### Courseflow Team Members
+
+| Student Name | Role |
+| ------------- | ----------- |
+| Mark Enriquez | Team Member |
+
+### Splash Kit
+
+#### Splash Kit Overview, Goals, and Objectives
+
+Splashkit is an all-purpose toolkit for beginners built in C++ and can be used with C++ and C#.
+Deakin University uses it to introduce students to programming through its easy-to-use functions.
+
+As part of the Splashkit team, you will be responsible for expanding the toolkit functions,
+developing improved and innovative ways of working with Splashkit and creating educational documents
+and videos for students.
+
+#### Splash Kit Aims for Trimester
+
+See Card Status in Backlog for Additional details and Completed Research Cards. The following
+projects and tasks stated below are what we aim to work on this trimester.
+
+#### SplashKit Arcade
+
+- Create an automated game download system for Arcade Machines
+ - The proposed system will use the Arcade-games Repo to check for updates in the game version and
+ download the latest version
+ - Games should have a Publish tag or similar to be loaded to the main menu.
+ - Have a secondary game menu for test games/non-published.
+
+- Updates to Arcade Menu
+ - Presently the Arcade machine uses Emulation Station forked from the RetorPI project version.
+
+ - Create a new system for test games
+ - See if we can modify the EM menu for the following
+ - Trigger Game download scripts
+ - Additional modes
+ - Kiosk β Only show Published Games (for Events)
+ - Normal β Has Published and Test Systems
+ - Via script or other method have games exit after 10 min's if there's been no key Input
+
+- Stretch Goals/Interesting ideas
+ - Consider a local Test Mode β Arcade Switches to AP mode displays connection info (random
+ password) and has a web server student can drop new game build on and tests. The machine Would
+ delete the game and reset after a period of time.
+ - Security would be a big consideration on this idea as it would be easy to abuse and not much
+ in the way of logging vs official upload via Git Hub.
+ - Implement a voting system on the Arcade Machine to give meaning to the star ranking.
+
+ - Arcade Games β GitHub Actions
+ - Correct C# for Arm (this should be done; see [trello card](https://trello.com/c/qeYlMImY) for
+ Status)
+ - Dotnet does not run correctly in the Emulated PI environment used for C++ games. New Action
+ was created for compiling dotnet vs Arm games small bug in checking logic to be fixed before
+ merge.
+ - Update Arcade β Games Readme
+ - Updated Controle to correctly reflect the Arcade machine
+ - Updated on new Compiling Process
+ - Instruct that All Game Assets must go into the Resources Folder (Action does try to capture
+ root directories like images, sound, etc.) This includes level maps etc., or they won't
+ upload to Arcade Machines
+ - Implement Versioning for compiled games.
+ - A simple version file in the games directory receives an incremental bump every time the
+ game is updated so the Arcade knows to get the latest version.
+ - This file can also contain additional information for the Arcade Menu. (Author, Publisher,
+ other)
+ - Retrieve and Compile Games from SubModules
+ - Formalise Process with Deakin Staff on how Students from Classes like SIT102 or SIT771 can
+ upload games to the Arcade Machine
+ - Barrier will be using GitHub for new students, especially as this will use submodules.
+ - Consider creating scripts to automate the linking of sub-modules
+
+ - Move All games to Sub-Modules
+ - Games made by Toth-Tech should be moved to their own repo, (or we can consider a separate
+ Company if we don't want to crowd the Githubn too Much)
+ - This will potentially allow Linking to Other Student Repos.
+
+#### Splashkit Expansion
+
+- Priority Items Deployment Packages
+ - Debian Package.
+ - Nuget Package.
+ - Brew Package.
+
+- Check for Further Functions from [Swin games](https://github.com/macite/swingame)to port into
+ splashkit.
+- Fix Python Compatibility
+ - Python can no longer be used to code games with SplashKit. Previous research indicates a change
+ with v3.8; see
+ [here](https://github.com/thoth-tech/documentation/blob/main/docs/Splashkit/Extensions/Python%20Compatibality/Research%20%26%20Findings/Python%20Changelog.md).
+
+- Look at Adding AI function to SplashKit
+ - Can look at LLMs like ChatGPT
+ - Similar Functions to
+
+- Dev Container Mac
+ - As most SplashKit Programs have a visual component and not browser-based based, we need a way to
+ view the program's window output. This is normally accomplished by xserver forwarding and sound
+ via pulse audio.
+ - Mac xquartz is a xserver compatible with Mac Instaitl Tests container that can be setup and run
+ x based programs e.g. xeyes but there is a compatibility issue with the graphics system in
+ SplashKit. Further investigation is needed.
+
+- SplashKit.io
+ - Publish Astro Starlight site
+ - The Aim will be to convert Splashkit.io to our new webpage platform.
+ - Advise getting a subdomain like new.splashkit.io (or similar) setup for testing, and
+ Transition will just be a DNS change then
+ - Thorough documentation of the new site is needed
+ - The Existing SplashKit.io may have a function to auto-update the API pages based on functions
+ added to SplashKit. This should be investigated and replicated in the new site.
+
+- Game Engine
+ - Project Setup: Create a streamlined project setup process for easier onboarding and development.
+ - Camera System: Implement a flexible and efficient camera system to handle different views and
+ perspectives.
+ - Transforms: Develop a system for handling object transformations like translation, rotation, and
+ scaling.
+ - Event System: Design an event system for handling game events in an extensible manner.
+ - Input Handling System: Implement a robust input handling system to manage user interactions.
+
+- Documentation Migration
+ - As the company is moving to a new documentation repository a data Migration will need to occur
+ between the existing documentation repo and the new one.
+ - Work with company operations to plan the migration, but the SplashKit team needs to move the
+ existing document over (also consider it a good opportunity to clean house and archive older
+ information)
+
+#### SplashKit Tutorials
+
+#### Backlog
+
+- Game Development
+ - High Level Design
+ - Complete Demo Game
+ - 8. Creating a 2D "Metroidvania" Game - Enemies and Combat
+ - 10. Creating a 2D "Metroidvania" Game - Level Design and Progression
+ - 13. Creating a 2D "Metroidvania" Game - Polishing and Finalization
+ - 7. Creating a 2D "Metroidvania" Game - Camera Movement, Parallax and Depth
+
+- Tutorials and Documentation
+ - Understanding SplashKit Manager - (SKM) Shell Commands - Tutorial
+ - Project Structure and Initialization
+
+- Roadmap (Future Plans)
+ - Integrate different stages of "Creating a 2D 'Metroidvania' Game" for cohesiveness and
+ consistency.
+ - Complete remaining tutorials
+ - Plans for new tutorials, ensuring total Splashkit Functionality
+
+#### SplashKit Deliverables
+
+Our main deliverables will be based on story points completed in the Trello tasks; we are aiming for
+students to complete between 5-6 Story points every 2-week sprint.
+
+#### SplashKit Team Members
+
+| Student Name | Role |
+| -------------------------- | ----------- |
+| Ayan Masood | Team Member |
+| Georgie O'Malley | Team Member |
+| Jaron Chen | Team Member |
+| Pratham Gupta | Team Member |
+| Samnang (Bryan) Taking | Team Member |
+| Castiel Mcintosh | Team Member |
+| Franco John (Frankie) Veri | Team Member |
+| Jinwen (Leo) Liu | Team Member |
+| Sean Boettger | Team Member |
+| Taiming Xu | Team Member |
+| Wenzong Xuan | Team Member |
+| Yuheng (Bruce) Wang | |
diff --git a/src/content/docs/policies/Contributing Effectively in T3 2023.md b/src/content/docs/Teams and Contributions/2023 Trimester 3/contributing-effectively-in-t3-2023.md
similarity index 100%
rename from src/content/docs/policies/Contributing Effectively in T3 2023.md
rename to src/content/docs/Teams and Contributions/2023 Trimester 3/contributing-effectively-in-t3-2023.md
diff --git a/src/content/docs/Teams and Contributions/2023 Trimester 3/organizational-structure-t3-2023.md b/src/content/docs/Teams and Contributions/2023 Trimester 3/organizational-structure-t3-2023.md
new file mode 100644
index 00000000..cc2e50b8
--- /dev/null
+++ b/src/content/docs/Teams and Contributions/2023 Trimester 3/organizational-structure-t3-2023.md
@@ -0,0 +1,5 @@
+---
+title: Organizational Structure T3 2023
+---
+
+
diff --git a/src/content/docs/Teams and Contributions/2024 Trimester 1/contributing-effectively-in-t1-2024.md b/src/content/docs/Teams and Contributions/2024 Trimester 1/contributing-effectively-in-t1-2024.md
new file mode 100644
index 00000000..82bd842d
--- /dev/null
+++ b/src/content/docs/Teams and Contributions/2024 Trimester 1/contributing-effectively-in-t1-2024.md
@@ -0,0 +1,77 @@
+---
+title: Contributing Effectively in T1 2024
+---
+
+Welcome to T1 2024, we are eager to see the excellent work that would be produced at the end of this
+trimester. This document provides information to guide every member of Thoth Tech in contributing
+effectively to their various products.
+
+## T1 2024 Calendar
+
+This trimester comprises of 12 weeks of exciting work and we hope you are looking forward to
+learning and contributing in your various products. We advise that every student gets up to speed
+quickly so they can start making valuable contributions to the company.
+
+| Sprint | Start Date | End Date |
+| ---------------------------- | --------------- | --------------- |
+| Sprint 1 | 04 β Mar - 2024 | 17 - Mar 2024 |
+| Sprint 2 | 18 β Mar - 2024 | 28 β Mar - 2024 |
+| Easter/Intra-Trimester Break | 29 β Mar - 2024 | 07 β Apr - 2024 |
+| Sprint 3 | 08 β Apr - 2024 | 21 β Apr - 2024 |
+| Sprint 4 | 22 β Apr - 2024 | 05 - May 2024 |
+| Sprint 5 | 06 β May - 2024 | 19 β May - 2024 |
+| Sprint 6 | 20 β May - 2024 | 02 β Jun - 2024 |
+
+
+
+## Thoth Tech Products and Mentors
+
+By the end of week 1, it is expected that everyone has been assigned to a team and has engaged with
+the product leads and mentors. In any product/team you find yourself ensure that you follow the
+rules and guidelines of the team. Only 3 Thoth Tech products would be worked on this trimester. The
+products and respective mentors are listed below.
+
+1. Ontrack: Daniel Maddern
+2. SplashKit: Olivia McKeon
+3. Company Operations: Amin Abken
+
+For every product, the mentors would hold at least 2 weekly meetings, and this would also serve as
+the products weekly meetings where every member of the team converges to discuss the product
+objective, populate Trello board, assign tasks, and discuss any roadblocks or impediments.
+
+## Contributing and Producing Acceptable Evidence
+
+Useful tips to contributing in your assigned teams
+
+- The outcome of every task assigned to you would be required to be published to your teams GitHub
+ repo. The GitHub link for every product can be found by clicking the product
+ [here](https://main--strong-fairy-c1bde1.netlify.app/products/products/).
+- To ensure you are accurately publishing to GitHub, review the GitHub policy
+ [here](https://main--strong-fairy-c1bde1.netlify.app/policies/github-management-policy/).
+- All documents are written in Markdown.
+- Tasks would be assigned to you via the Trello board.
+
+**Important!!**
+
+- When you raise a Pull request, it needs to be reviewed by another student after which the student
+ who reviewed would leave a comment on the PR stating if it can be progressed to be approved by the
+ mentor.
+- Watch the video provided in this
+ [link](https://deakin365.sharepoint.com/sites/ThothTech2/_layouts/15/stream.aspx?id=%2Fsites%2FThothTech2%2FShared%20Documents%2FOnTrack%2Fpull%2Drequest%2Ddemo%2Emov&nav=eyJwbGF5YmFja09wdGlvbnMiOnsic3RhcnRUaW1lSW5TZWNvbmRzIjo1LjQyNzM2OH19&referrer=StreamWebApp%2EWeb&referrerScenario=AddressBarCopied%2Eview)
+ to make Pull Requests and Peer Review fellow students work
+
+## Providing acceptable evidence
+
+This trimester every evidence provided must have an associated Pull Request. Some ways to ensure you
+can produce acceptable evidence are.
+
+1. Any research work should be documented using our Spike template and published to your products
+ GitHub repo. The Spike Plan Template can be found
+ [here](https://github.com/thoth-tech/documentation/blob/main/docs/Templates/SpikePlan-Template.md)
+2. Any solution testing performed (whether successful or not) should be documented using our Spike
+ template. The Spike Outcome Template can be found
+ [here](https://github.com/thoth-tech/documentation/blob/main/docs/Templates/SpikeOutcome-Template.md)
+3. Any change to a product in development or production stage should be pushed to the relevant
+ GitHub repo.
+4. Document all hours in your personal/team worklog. Every student must complete a minimum of 120
+ hours to pass the unit.
diff --git a/src/content/docs/Teams and Contributions/2024 Trimester 1/leadership-t1-2024.md b/src/content/docs/Teams and Contributions/2024 Trimester 1/leadership-t1-2024.md
new file mode 100644
index 00000000..9e70a848
--- /dev/null
+++ b/src/content/docs/Teams and Contributions/2024 Trimester 1/leadership-t1-2024.md
@@ -0,0 +1,36 @@
+---
+title: Leadership T1 2024
+---
+
+### Company Directors
+
+- Glory Lee - Acting Director, Product Owner (Company Operation)
+- Andrew Cain - Productor Owner (OnTrack & SplashKit)
+
+### Product Mentors
+
+- OnTrack: Daniel Maddern & Nebula Alam
+- SplashKit: Olivia McKeon & Quoc Tien Pham
+- Company Operations: Quoc Tien Pham
+
+### Student Leadership
+
+- Satika Jayawardena - Student Lead (OnTrack), Communications Lead
+- Josh Kilinc - Student Lead (OnTrack), Code Lea (OnTrack)
+- Sean Boettger - Student Lead (SplashKit), Code Lead (SplashKit)
+- Aditya Parmar - Student Lead (SplashKit)
+- Eisen Lai - Student Lead (Company Operations), Coordination Lead
+
+## Roles and Responsibilities
+
+
+
+| Roles | Description | Responsibilities | Skills |
+| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Acting Director | The role of the acting director is to oversee the Thoth Tech company executive leadership team to ensure they are running the company effectively and value is being added to the Thoth Tech products by the projects they are supporting. |
- Provide guidance to executive leadership team.
- Provide high-level vision for the ongoing goals of the company
- Provide a consistent company strategy due to low retention
|
- Leadership
- Communication
- Mentor
- Decision-making
|
+| Product Owner | The role of the product owner at Thoth Tech serves as the vital link between the development team and stakeholders, ensuring that the product meets customer needs and aligns with company objectives. |
- Define and communicated the product vision to development team.
- Work with mentors to make informed decisions considering technical feasibility and goals.
- Provide leadership to the development team, fostering collaboration and innovation.
|
- Leadership
- Communication
- Product Visioning
- Stakeholder Management
- Prioritization
- Continuous Improvement
- Decision-making
|
+| Product Mentor | The role of the Product Mentor is to lead and support delivery leads in projects related to their product to ensure ongoing success. |
- Drive the product in the direction determined by the Managing Directors and Area Leads.
- Strong drive towards toward objectives with bias for action
- Proactively identify blockers and opportunities
- Support delivery leads where needed
- Make thoughtful decisions motivated by data and research
- Be transparent and accountable by visualising objectives
|
- Leadership
- Communication
- Empathy
- Interpersonal-Savvy
- Collaborative
- Stakeholder Management
|
+| Student Lead | The role of the Delivery lead is to lead, organise and support their project teams to ensure ongoing success. |
- Establish a team cadence
- Build rapport with all team members to foster a cohesive and collaborative environment
- Strong drive towards objectives with bias for action.
- Proactively identify blockers and opportunities
|
- Leadership
- Communication
- Empathy
- Interpersonal-Savvy
- Collaborative
- Stakeholder Management
|
+| Team Member | The role of all team members is to contribute to their respective products/projects. Take the initiative in finding work and solving problems, as well as to communicate with the Seniors about their progress and issues. |
- Work with the project leads to meet the goals for this trimester.
- Attend to assigned tasks in a timely manner.
- Work in collaboration with other team members to produce a viable product.
|
- Technical skills as per project
- Team collaboration
- Competence in GitHub
- Time Management
- Knowledge of Agile model
|
+
+
|
+| Amrith Jayadeep | Migration: group set selector |
|
+| Anirudh Nellippilli Joshi | Documentation: grade-task-modal component review | |
+| Anirudh Nellippilli Joshi | migrate file-uploader.coffee |
|
+| Anirudh Nellippilli Joshi | Migration: group set selector |
|
+| Anirudh Nellippilli Joshi | Migration: group set manager |
|
+| Anirudh Nellippilli Joshi | Migration: csv-result-modal.coffee |
|
+| Anirudh Nellippilli Joshi | Onboarding Juniors Guidence | |
+| Atharv Sandip Bhandare | Migration: comments-modal |
|
+| Atharv Sandip Bhandare | Write documentation for JPLAG |
|
+| Atharv Sandip Bhandare | Migration: Component task-ilo-alignment-modal.coffee | |
+| Atharv Sandip Bhandare | Add user UI does not allow user creation |
|
+| Atharv Sandip Bhandare | Migration: unit-staff-editor.coffee |
|
+| Atharv Sandip Bhandare | JPLAG UI documentation | |
+| Bruce Wang | Migration: comments-modal |
|
+| Bruce Wang | Documentation: grade-task-modal component review | |
+| Bruce Wang | migrate file-uploader.coffee |
|
+| Bruce Wang | Migration: grade-icon.coffee | |
+| Bruce Wang | Migrate analytics.coffee | |
+| Bruce Wang | Migrate viewer.coffee | |
+| Bruce Wang | Migration: timeout.coffee |
|
+| Bruce Wang | Migration: unauthorised.coffee | |
+| Bruce Wang | Migration: unit-staff-editor.coffee |
|
+| Bruce Wang | Migration: csv-result-modal.coffee |
|
+| Bruce Wang | Onboarding Juniors Guidence | |
+| Eliya Geerlings | Migration: comments-modal |
|
+| Eliya Geerlings | Autoload PDFs on page 2 when viewing student submissions | |
+| Eliya Geerlings | Fix jupyter notebook latex rake test | |
+| Eliya Geerlings | Fix up existing confirmation-modal migration | |
+| Eliya Geerlings | Latex docker downsizing: Creation of feasibility document | |
+| Eliya Geerlings | Latex docker downsizing: Implementation |
|
+| Eliya Geerlings | Persistent PDF zoom levels when selecting between different task submissions | |
+| Eliya Geerlings | Migration: unit-staff-editor.coffee |
|
+| Ivan Justin | Latex docker downsizing: Creation of feasibility document | |
+| Ivan Justin | Chat markdown not rendering properly bug | |
+| Ivan Justin | Migration: Unit-ilo-edit-modal.coffee |
|
+| Jack Shinners Carroll | Write documentation for JPLAG |
|
+| Jack Shinners Carroll | Documentation: grade-task-modal component review | |
+| Jack Shinners Carroll | Latex docker downsizing: Creation of feasibility document | |
+| Jack Shinners Carroll | Latex docker downsizing: Implementation |
|
+| Jack Shinners Carroll | Migrate analytics.coffee | |
+| Jack Shinners Carroll | Migration: unit-staff-editor.coffee |
|
+| Jack Shinners Carroll | Add JPLAG frontend | |
+| Jack Shinners Carroll | Alter JPLAG api code | |
+| Jack Shinners Carroll | Create JPLAG Container | |
+| Jack Shinners Carroll | JPLAG UI documentation | |
+| Jake Mansfield | Document the below API pages in detail within the website - set 5 | |
+| Jake Mansfield | Implement the backend requirements for the course entity. | |
+| Jake Mansfield | Implement the backend requirements for the course map entity. | |
+| Jake Mansfield | Implement the backend requirements for the course map unit entity. | |
+| Jake Mansfield | Implement the backend requirements for the requirement set entity. | |
+| Jake Mansfield | Implement the backend requirements for the specialization entity. | |
+| Jake Mansfield | Add detailed operations for units API (task_definitions -tii_group_attachments ) on Ontrack documentation website | |
+| Jake Mansfield | Add Authentication to the Courseflow endpoints | |
+| Jake Mansfield | Add button to Courseflow main component | |
+| Jake Mansfield | Created coursemap base page | |
+| Jake Mansfield | Add detailed operations for units API (task_definitions) on Ontrack documentation website | |
+| Jake Mansfield | Add detailed operations for units API (group set - group ID) on Ontrack documentation website | |
+| Jake Mansfield | Add detailed operations for units API (group set - group csv) on Ontrack documentation website | |
+| Jake Mansfield | Add detailed operations for units API (task_definitions - task_assessment_resources ) on Ontrack documentation website | |
+| Jake Mansfield | Document the operations units API - Tutorial Streams | |
+| Jake Mansfield | Ensure Unit Definition model satisfies all requirements (Phase 2) | |
+| Jake Mansfield | Create appropriate testing files for the Unit Definition entity (Phase 1) | |
+| Jake Mansfield | Create dummy data for a specific course for the front end to use (Phase 3) | |
+| Jake Mansfield | Implement the backend requirements for the Unit Definition entity (phase 1) | |
+| Jake Mansfield | Make a Plan for Courseflow for T2 | |
+| Jake Mansfield | Migrate analytics.coffee | |
+| Jake Mansfield | Migrate the existing Unit table to be compatible with Unit Definition (Phase 4) | |
+| Jake Mansfield | Migration: timeout.coffee | 
+