Documentation: edits complete.

CODE_OF_CONDUCT.md

@@ -1,132 +1 @@
 # Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual
-identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-- Demonstrating empathy and kindness toward other people
-- Being respectful of differing opinions, viewpoints, and experiences
-- Giving and gracefully accepting constructive feedback
-- Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-- Focusing on what is best not just for us as individuals, but for the overall
-  community
-
-Examples of unacceptable behavior include:
-
-- The use of sexualized language or imagery, and sexual attention or advances of
-  any kind
-- Trolling, insulting or derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or email address,
-  without their explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official email address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-[[email protected]](mailto:[email protected]).
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of
-actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or permanent
-ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the
-community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.1, available at
-[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
-
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
-[https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -36,15 +36,13 @@ Here are some resources to help you get started with open source contributions:
 Our preferred way of providing the opportunity for people to contribute to Noodle is through a process that starts with creating a new issue, the summary of the workflow that you can expect and should adhere to is the following:
 
 - You see an area of improvement in the code base, this could be a fix, feature, refactoring...etc
-- Create an [issue](https://github.com/noodle-run/noodle/issues) on our Github repository.
+- Create an [issue](https://github.com/jonathancaleb/enoflow/issues) on our Github repository.
 - Wait until a team member discusses the issue with you, and if both parties are in agreement, you can start working on the issue.
 - Once work has started, you can create a draft pull request and remember to link your pull request with the issue.
 - Once the work is complete, change the status of the pull request to ready for review.
 - We will review the pull request and if all is good, congratulations! 🥳 you are now a Noodle contributor!
 - If not, we will explain the changes that need to be made for the pull request to be merged or why it can't be merged.
 
-If you would like to be more involved in the development of Noodle, we would like to invite you to our [Discord Server](https://discord.gg/SERySfj8Eg) where we can have a chat together and get you involved in the project!
-
 ### Some simple rules
 
 - Don't work on an issue that is already being worked on by someone else.
@@ -81,10 +79,10 @@ There are a lot of other technologies being used in this project, however these
 
 ### Cloning the repo
 
-To clone the repo, you firstly need to [fork](https://github.com/noodle-run/noodle/fork) it, and then clone your copy of noodle locally.
+To clone the repo, you firstly need to [fork](https://github.com/jonathancaleb/enoflow/fork) it, and then clone your copy of repo locally.
 
 ```bash
-git clone https://github.com/<your-gh-username>/noodle.git
+git clone https://github.com/<your-gh-username>/enoflow.git
 ```
 
 ### Bun
@@ -113,8 +111,8 @@ bun install
 
 Now that Bun & dependencies has been installed, it's time to configure your environment variables so that the project works as expected:
 
-1.  Duplicate the `.env.example` file as just `.env`
-2.  Populate the values with your own, you will need to sign up to some services in the process.
+1. Duplicate the `.env.example` file as just `.env`
+2. Populate the values with your own, you will need to sign up to some services in the process.
 
 You can checkout which variables are needed and which are optional in the `src/env.ts` file.
 
@@ -139,7 +137,3 @@ bun lint
 # Format using Prettier
 bun format
 ```
-
-## Closing notes
-
-Again, thank you so much for your interest in contributing to Noodle, we really appreciate it, and if there is anything we can do to help your journey, make sure to join our [Discord Server](https://discord.gg/SERySfj8Eg).

README.md

@@ -9,7 +9,7 @@
 
 ## Purpose
 
-A productivity app inspired by Notion. Scribe integrates note-taking, task management, databases, and more into one seamless experience. Built with Next.js, GoLang, Python, MongoDB, and Flutter
+A productivity app inspired by Notion. Scribe integrates note-taking, task management, databases, and more into one seamless experience. Built with Next.js, GoLang, Python, Postgres, Clerk and Flutter
 
 ## Planned MVP Features
 
@@ -22,7 +22,6 @@ The flashcards will be generated from the notes that you take, and you will be a
 
 - 📅 Calendar
 - 📝 Task management
-- 📊 Grade tracking
 
 ## Contributing
 

SECURITY.md

@@ -2,6 +2,4 @@
 
 ## Reporting a Vulnerability
 
-To report a security issue, please [open a security advisory](https://github.com/Enoflow-run/Enoflow/security/advisories/new) on GitHub with a detailed description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue.
-
-Please remember to include everything required for us to reproduce the issue, including but not limited to a publicly accessible git repository and/or StackBlitz repository.
+To report a security issue, please [open a security advisory](https://github.com/jonathancaleb/enoflow/security/advisories/new) on GitHub with a detailed description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue.