Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Information (please complete the following information):

• Node version [e.g. 18.15.0]
• Pnpm version [e.g. 8.6.6]

Additional context
Add any other context about the problem here.

The Greeting header is the first component that will be added to the dashboard content section, it should say good morning, afternoon or evening based on the current time as well as the user's name. It should also fetch a random quote from an API and display that quote underneath the heading.

Is your feature request related to a problem? Please describe.
Is there a roadmap / board, where we can find the future tasks to be done?

Describe the solution you'd like
It could be a board or something similar using Github

Describe alternatives you've considered

Additional context
This is helpful to everyone that is willing to contribute somehow with the project

Is your feature request related to a problem? Please describe.
A plugging system for extending the functionality and customization of the platform

Describe the solution you'd like
It would be great to be able to add plugins like one drive or nextcloud sync without having to add them directly to the project or waiting for the feature release. It can be tricky, at least with UI plugins, but it can be done.

Describe alternatives you've considered

Additional context
I want to have everything stored on my NAS as markdown or atleast HTML, this could make it so anyone can implement that feature with out the burden on the main devs

Now that tRPC v10 entered beta version, we should update to it.

I would like to suggest option that would enable for user to try to explain topic that user is studying to AI. And AI would give the user questions , about that topic along the way.This would be really helpful for studying calculus for example.

The first feature that we should look at implementing is for the user to see their avatar, their name, name of the course they are doing and a button to go to the user edit page.

Describe the bug

• Survery should be survey

To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Information (please complete the following information):

• Node version [e.g. 18.15.0]
• Pnpm version [e.g. 8.6.6]

Additional context
Add any other context about the problem here.

test

Currently on shorter displays (height) the preview image completely goes underneath the header text, this should be fixed and the layout of the landing page should be consistent across all device sizes.

Is your feature request related to a problem? Please describe.
As a student I'd like to upload documents/videos and other files to noodles to have my learning material in one place. Similar to moodle.

Describe the solution you'd like
I'd like to have something like a fileupload and the possibility to name and sort files for topics.

As an offtopic question: Is there already a possibility to deploy and try out noodles?

I want to try noodle and if possible can contribute.

What commands do I need to setup Noodle properly?

@all-contributors add @jrysana for code

I wanted to reach out and suggest an awesome addition to the js-draw application. How about integrating a drawing feature into the app?

The current js-draw application is fantastic for note-taking with its canvas-based platform, but it would be even more amazing if users could draw directly on the canvas. Imagine being able to create sketches, diagrams, and annotations effortlessly within the app!

By incorporating drawing tools like different brush sizes, colors, and an eraser, users would have the freedom to express their ideas visually. This would greatly benefit students, professionals, and anyone who relies on visual aids to enhance their note-taking experience.

here is a link to the repo i thought would e useful for this thing
https://github.com/personalizedrefrigerator/js-draw

I don't know if it is possible to add some high-quality course links for different subjects, or set up a problem-solving discussion area

Currently, the sidebar logic is defined in the Dashboard template, this should be moved to it's own component which then get used in the Dashboard template.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

To display notebooks of the user, we will use a list of notebooks, each list should be a component that renders the notebook's title, the last time the user has edited the notebook, a button to pin the notebook to their favourites and a tag with which module the notebook belongs to.

Describe the bug
Typo in the paragraph talking about joining the waiting list.

To Reproduce
Steps to reproduce the behavior:
https://noodle.run/waitlist

Expected behavior
Should say getting and not geting.

Screenshots

Information (please complete the following information):

• Node version [e.g. 18.15.0]
• Pnpm version [e.g. 8.6.6]

Hi, I just discovered this project and was trying to join the waitlist when I encountered this error

source: Homepage

I am willing to work on this issue but I think this may be a problem with the deployment rather than the source code. Let me know if there is something I can do

The Progress bar atom will be used in the module card and other areas to display statuses of success.

Describe the bug
There is no contact method yet listed in the code of conduct - https://github.com/ixahmedxi/noodle/blob/main/CODE_OF_CONDUCT.md#enforcement

To Reproduce
Go here https://github.com/ixahmedxi/noodle/blob/main/CODE_OF_CONDUCT.md#enforcement

Expected behavior
Have an email address so someone can reach out if needed

Screenshots

Information (please complete the following information):
NA
Additional context
NA

Is your feature request related to a problem? Please describe.
At this time, it does not appear to be available in any language other than English at this time.

Describe the solution you'd like
multilingual support

Describe alternatives you've considered

Additional context

Relation

R(subject_ID, subject_name, user_ID, user_name, user_surname, user_email, user_role, module_ID, module_name, module_code, module_year, module_term, module_group, module_timetable, task_ID, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, subtask_ID,subtask_name, subtask_completion)

Functional Dependencies

FD = {
subject_ID → subject_name,
user_ID → user_name, user_surname, user_email, user_role,
module_ID → module_name, module_code, subject_ID,
module_ID, module_year, module_term, module_group → module_timetable,
task_ID → task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_year, module_term, module_group,
subtask_ID → subtask_name, subtask_completion, task_ID,
}

• Because each module can take place in multiple years, in multiple terms and can potentially have different student groups, each timetable is unique to these 3 attributes.

Normalization

Closures

• (subject_ID) = {subject_ID, subject_name}
• (user_ID) = {user_ID, user_name, user_surname, user_email, user_role}
• (module_ID) = {module_ID, module_name, module_code, subject_ID, subject_name}
• (module_ID, module_year, module_term) = {module_ID, module_name, module_code, subject_ID, subject_name, module_year, module_term, module_timetable}
• (task_ID) = {task_ID, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_name, module_code, module_year, module_term, module_group, module_timetable, subject_ID, subject_name}
• (subtask_ID) = {subtask_ID, subtask_name, subtask_completion, task_ID, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_name, module_code, module_year, module_term, module_group, module_timetable, subject_ID, subject_name}

Key

((user_ID) + (subtask_ID)):

(user_ID, module_ID, module_year, module_term, subtask_ID) = {user_ID, user_name, user_surname, user_email, user_role, subtask_ID, subtask_name, subtask_completion, task_ID, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_name, module_code, module_year, module_term, module_timetable, subject_ID, subject_name}

Second Normal Form (2NF)

Every non-primary-key attribute is fully functionally dependent on the primary key.

R(user_ID, user_name, user_surname, user_email, user_role, subtask_ID, subtask_name, subtask_completion, task_ID, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_name, module_code, module_year, module_term, module_timetable, subject_ID, subject_name)

• user_ID → user_name, user_surname, user_email, user_role Partial Functional Dependency
• subtask_ID → subtask_name, subtask_completion, task_ID, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_name, module_code, module_year, module_term, module_timetable, subject_ID, subject_name Partial Functional Dependency

R(user_ID, subtask_ID)
R1(user_ID, user_name, user_surname, user_email, user_role)
R2(subtask_ID, subtask_name, subtask_completion, task_ID, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_name, module_code, module_year, module_term, module_group, module_timetable, subject_ID, subject_name)

Relations

• R(user_ID, subtask_ID)
• R1(user_ID, user_name, user_surname, user_email, user_role)
• R2(subtask_ID, subtask_name, subtask_completion, task_ID, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_name, module_code, module_year, module_term, module_group, module_timetable, subject_ID, subject_name)

Third Normal Form (3NF)

There is no transitive dependency for non-prime attributes.

R(subtask_ID, subtask_name, subtask_completion, task_ID, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_name, module_code, module_year, module_term, module_group, module_timetable, subject_ID, subject_name)

• subtask_ID → task_ID → task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_year, module_term, module_group, subject_ID
  R(subtask_ID, subtask_name, subtask_completion, task_ID)
  R1(task_ID, task_ID*, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_name, module_code, module_year, module_term, module_group, module_timetable, subject_ID, subject_name)

R(task_ID, task_ID*, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_name, module_code, module_year, module_term, module_group, module_timetable, subject_ID, subject_name)

• task_ID → module_ID, module_year, module_term, module_group → module_name, module_code, module_timetable, module_year, module_term, module_group, subject_ID
  R(task_ID, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_year, module_term, module_group)
  R1(module_ID, module_year, module_term, module_group, module_name, module_code, subject_ID, subject_name)

R1(module_ID, module_year, module_term, module_group, module_name, module_code, subject_ID, subject_name)

• module_ID, module_year, module_term, module_group → module_name, module_code, module_timetable, subject_ID, subject_name Full Functional Dependency
• module_ID → module_name, module_code, subject_ID, subject_name Partial Functional Dependency
  R(module_ID, module_year, module_term, module_group, module_timetable)
  R1(module_ID, module_name, module_code, subject_ID, subject_name)

R(module_ID, module_name, module_code, subject_ID, subject_name)

• module_ID → subject_ID → subject_name
  R(module_ID, module_name, module_code, subject_ID)
  R1(subject_ID, subject_name)

Relations

• R(user_ID, user_name, user_surname, user_email, user_role)
• R(subject_ID, subject_name)
• R(module_ID, module_name, module_code, subject_ID)
• R(module_ID, module_year, module_term, module_group, module_timetable)
• R(task_ID, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_year, module_term, module_group)
• R(subtask_ID, subtask_name, subtask_completion, task_ID)

Boyce Codd Normal Form (BCNF)

For every functional dependency X → Y, X must the super key of that relation.

R1(user_ID, user_name, user_surname, user_email, user_role)
R2(subject_ID, subject_name)
R3(module_ID, module_name, module_code, subject_ID)
R4(module_ID, module_year, module_term, module_timetable)
R5(task_ID, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_year, module_term, module_group)
R6(subtask_ID, subtask_name, subtask_completion, task_ID)

R1(user_ID, user_name, user_surname, user_email, user_role)
(user_ID) = {user_ID, user_name, user_surname, user_email, user_role}

R2(subject_ID, subject_name)
(subject_ID) = {subject_ID, subject_name}

R3(module_ID, module_name, module_code, subject_ID)
(module_ID) = {module_ID, modules_name, module_code, subject_ID, subject_name}

R4(module_ID, module_year, module_term, module_timetable)
(module_ID, module_year, module_term) = (module_ID, module_year, module_term, module_timetable, modules_name, module_code, subject_ID, subject_name)

R5(task_ID, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID)
(task_ID) = {task_ID, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_year, module_term, module_group, modules_name, module_code, module_timetable, subject_ID, subject_name}

R6(subtask_ID, subtask_name, subtask_completion, task_ID)
(subtask_ID) = {subtask_ID, subtask_name, subtask_completion, task_ID, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, modules_name, module_code, subject_ID, subject_name}

Relations

• user(user_ID, user_name, user_surname, user_email, user_role)
• subject(subject_ID, subject_name)
• module(module_ID, module_name, module_code, subject_ID)
• module_timetable(module_ID, module_year, module_term, module_timetable)
• task(task_ID, task_name, task_description, task_deadline, task_date_created, task_type, task_importance, task_completion, module_ID, module_year, module_term, module_group)
• subtask(subtask_ID, subtask_name, subtask_completion, task_ID)

Hello, sorry for being a pain but I have no idea how I can install and access Noodle. I am a noob in javascript but I have node version 18 installed. How can I install this @ixahmedxi ? Help appreciated...

Show time management of others in some kind of status or something to be more motivated and productive.
Add some milestones like on studying for some hours and recieving achievement tags to share on social media.

Describe the bug
Per #201, smooth scrolling anchor links on the landing page should actually update the fragment in the URL bar when you click them on the landing page. Currently, they don't, because we prevent the default behavior of the Link (anchor tag wrapper) when on the same page to allow JS to smoothly scroll reliably to the anchor.

To Reproduce
Steps to reproduce the behavior:

• Try clicking around the navbar on the landing page

Expected behavior
A clear and concise description of what you expected to happen.

• Browser URL bar fragment should update to the corresponding id when you click on the navbar links

Additional context
Add any other context about the problem here.

• It might make sense to do a custom wrapper around Next's Link component to facilitate automatic smooth scrolling on same-page anchor links.

Describe the bug
No link in readme

To Reproduce
Go to readme

Expected behavior
Thought it may be helpful/convenient to have a link to the license in the readme

Screenshots
na.

Python package version
na

Additional context
na

Create a star shaped icon button

As we start building components for the dashboard, we need the basic skeleton for the shape of the layout done firstly so that we can plug in these components and test them out. The dashboard has a box for the content and a sidemenu that should be toggleable on mobile and hidden.

Ahmed is my god

Describe the bug
Contributor badge number not matching number of contributors to repo

To Reproduce
Go to readme

Expected behavior
Contributor badge number should match number of contributors to repo

Screenshots

Information (please complete the following information):
NA

Additional context
NA

Is your feature request related to a problem? Please describe.
how can I contribute and join the team if you are open? would love to get connected and contribute. this could be a wrong place to connect but i did be keen.

Describe the solution you'd like
how to connect, if you are looking to connect and add a contributor

Describe alternatives you've considered
na

Additional context
na

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Information (please complete the following information):

• Node version [e.g. 18.15.0]
• Pnpm version [e.g. 8.6.6]

Additional context
Add any other context about the problem here.

Is your feature request related to a problem? Please describe.
The contributing.md file is empty

Describe the solution you'd like
As an open-source developer myself, I find this project exciting. hence I want to create the contribution file to guide developers interested in volunteering for this project

Describe alternatives you've considered
na

Additional context
na

Now that we have the template for the Dashboard pages, the module card, greeting and notebook item components, we can assemble the today's activity page UI component and export it from the ui library to then be used in the client application.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency @ianvs/prettier-plugin-sort-imports to ^4.1.1
• chore(deps): update dependency autoprefixer to ^10.4.16
• chore(deps): update dependency prettier-plugin-packagejson to ^2.4.6
• chore(deps): update dependency prettier-plugin-tailwindcss to ^0.5.6
• chore(deps): update dependency tailwindcss to ^3.3.5
• chore(deps): update react monorepo (@types/react, @types/react-dom)
• fix(deps): update dependency @clerk/themes to ^1.7.9
• fix(deps): update dependency @hookform/resolvers to ^3.3.2
• fix(deps): update dependency @radix-ui/react-avatar to ^1.0.4
• fix(deps): update dependency @radix-ui/react-dialog to ^1.0.5
• fix(deps): update dependency @radix-ui/react-scroll-area to ^1.0.5
• fix(deps): update dependency @radix-ui/react-tooltip to ^1.0.7
• fix(deps): update dependency superjson to ^1.13.3
• chore(deps): update commitlint monorepo to ^17.8.1 (@commitlint/cli, @commitlint/config-conventional)
• chore(deps): update dependency @next/eslint-plugin-next to ^13.5.6
• chore(deps): update dependency eslint to ^8.52.0 (eslint, @types/eslint)
• chore(deps): update dependency nx-cloud to v16.5.2
• chore(deps): update dependency prettier-plugin-jsdoc to ^1.1.1
• chore(deps): update dependency tsx to ^3.14.0
• fix(deps): update dependency @t3-oss/env-nextjs to ^0.7.1
• fix(deps): update dependency @vercel/analytics to ^1.1.1
• fix(deps): update dependency postgres to ^3.4.1
• fix(deps): update dependency react-hook-form to ^7.47.0
• fix(deps): update dependency slate to ^0.100.0
• fix(deps): update dependency slate-history to ^0.100.0
• fix(deps): update dependency slate-hyperscript to ^0.100.0
• fix(deps): update tanstack-query monorepo to ^4.36.1 (@tanstack/react-query, @tanstack/react-query-devtools)
• fix(deps): update trpc monorepo to ^10.42.0 (@trpc/client, @trpc/next, @trpc/react-query, @trpc/server)
• chore(deps): update commitlint monorepo to v18 (major) (@commitlint/cli, @commitlint/config-conventional)
• chore(deps): update dependency @radix-ui/colors to v3
• chore(deps): update dependency lint-staged to v15
• chore(deps): update nrwl monorepo (major) (nrwl/nx-set-shas, nx)
• fix(deps): update dependency @radix-ui/react-select to v2
• fix(deps): update dependency @udecode/plate to v24
• fix(deps): update dependency remark-gfm to v4
• fix(deps): update dependency superjson to v2
• fix(deps): update tanstack-query monorepo to v5 (major) (@tanstack/react-query, @tanstack/react-query-devtools)
• 🔐 Create all rate-limited PRs at once 🔐

Other Branches

These updates are pending. To force PRs open, click the checkbox below.

• chore(deps): update dependency postcss to v8.4.31 [security]
• fix(deps): update dependency zod to v3.22.3 [security]

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update dependency drizzle-orm to ^0.28.6
• fix(deps): update dependency framer-motion to ^10.16.4
• chore(deps): update dependency nx to v16.10.0
• chore(deps): update node.js to v18.18.2
• chore(deps): update pnpm to v8.9.2
• chore(deps): update typescript-eslint monorepo to ^6.9.0 (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• fix(deps): update dependency @clerk/nextjs to ^4.25.7
• fix(deps): update dependency lucide-react to v0.289.0
• fix(deps): update dependency slate-react to ^0.100.0
• chore(deps): update actions/checkout action to v4
• chore(deps): update node.js to v20 (node, @types/node)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Is your feature request related to a problem? Please describe.
I'm a brazillian student dev, and I'll like so much to have this application in my native language.

Describe the solution you'd like
Some as possible, add a translation for the portuguese language.

Describe alternatives you've considered
If you need, I'll like to try to help you in this translation, I would like to help with the translation of the project as necessary, as I am fluent in Portuguese

Additional context
if it is possible to forward what you want to receive a translation and how should I do it, I would appreciate it

The sidebar in the dashboard has links to pages, the UI for these links should be implemented and used in the Dashboard template.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Information (please complete the following information):

• Node version [e.g. 18.15.0]
• Pnpm version [e.g. 8.6.6]

Additional context
Add any other context about the problem here.

As a first step towards building our design system, we should implement the various typography styles that we will have across the website in terms of components. For example H1, H2, H3, H4 and Paragraph components.

The design system on figma elaborates the different typography styles and it should be done as components 1:1 to the design.

Hey there, amazing work!

This is more of a question than a suggestion.

The already-existing features are really great, but they are focused on an individual-experience, which is good, in some sense.
I would understand if the focus of Noodle is not about collaboration but more about having a set of tools to help you stay focused and organized, in one place. Though, in my opinion, isolated spaces might not be the best in terms of generating value (knowledge).

Are you planning (thinking) of having some sort of Feed where users can share some education-related stuff (material, tips, etc)?

Create a UI label to be used on NotebookListItems

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Information (please complete the following information):

• Node version [e.g. 18.15.0]
• Pnpm version [e.g. 8.6.6]

Additional context
Add any other context about the problem here.

As we build the api that Noodle will be based upon, we need to create a me query endpoint that would return the data of the currently signed in user like their name, email...etc

Our current ESLint config has some unnecessary attributes disabled related to handling promises that should be enabled and the code affecting the change should be dealt with.

In the .eslintrc file there are two attributes that should be changed from "off" to "error", these are:
"@typescript-eslint/no-misused-promises": "off",
"@typescript-eslint/no-floating-promises": "off",

The misused-promises rule can be changed from "off" to "@typescript-eslint/no-misused-promises": ["error", { "checksVoidReturn": false }],

After the change, the "no-void" rule should be turned off.

You will then notice some errors popping up in the signin.tsx page route file. These should be fixed and all eslint errors should be as well. You can run the pnpm nx run-many --target=lint command to check if there are any eslint errors.

test

The module card is used in the module page as well as the primary dashboard page to display all of the user's modules or their recently visited ones, the module card should also display a button that when clicked gives the user the option to edit or delete the module.