This is the design for the login page. Update the login page, which was built before, to be identical to the above picture. No functionality is needed.

For the email and password input fields, use the CustomTextField component (you can find it inside the lib/components folder).

Don't add the "Continue with Apple" button.

Notes:

• Update your local project before working on the issue
• File names should use the CamelCase convention
• Variable names should use the lowerCamelCase convention
• Frequently used components should be placed inside the lib/components folder
• Pages should be placed inside the lib/pages folder
• Format your code before creating a PR
• Remove any unused imports

The popup window should include the following:

• Text showing the affirmation
• Close button

Notes:

• Each component should be in a separate file located in the 'components' folder in the 'lib' folder.
• Place the popup window in the 'components' folder

Make a simple guide on Google Docs on how to use the "Aureus" library.

This is the library:
https://pub.dev/packages/aureus

This is their documentation:
https://github.com/Astra-Labs/Aureus/tree/main/Documentation

Our guide:
https://docs.google.com/document/d/1lBSYkKQN8jBO6IS7wtSnUo-cKhvCCw8rfB4bHpIa_qw/edit?usp=sharing

Prerequisites:

• Google Account
• "Code Blocks" add-on installed in Google Docs (It might be already installed. You can check by clicking on "Extensions". If it is installed, you can see "Code Block" at the end of the menu dropdown. To use it, click on "Code Blocks" then click "Start".)

The format of the guide should be like this:
Header [name of the component or view] (Bold and underlined)

• Small image of it
• Short example showing the line of code to initialize the component (use the add-on "Code Block" to format the code)
• Subheader [for each property of the component such as Colors...] (Underlined)
  • Short example showing the line of code how to customize the component [for each subheader] (formatted).

Note:

• It is required to test every component and page.
• Don't copy-paste their code. The examples used in the guide should be real.
• This issue requires more than one assignee. So feel free to comment if you want to work on it.
• Document only the "Widgets" and "Objects" folders

After issue #6 is closed.

Use the following package to add a Carousel Slider in the home page:
https://pub.dev/packages/carousel_slider

The carousel slider needs to be horizontal and it consists of cards. Each card will show the thumbnail and the name of the challenge.

Notes:

• Don't add any functionality.
• Each component should be in a separate file located in the 'components' folder in the 'lib' folder.

This is the design for the fourth page of the signup process. Create a new page identical to the above picture. No functionality is needed.

Use the chips_choice_null_safety library to build the chips.

The progress bar, which is located at the top, is excluded from the page.
The Next button, which is located at the bottom, is excluded from the page.

Use SingleChildScrollView as a parent widget to avoid overflow.

Notes:

• Update your local project before working on the issue
• File names should use the CamelCase convention
• Variable names should use the lowerCamelCase convention
• Frequently used components should be placed inside the lib/components folder
• Pages should be placed inside the lib/pages folder
• Format your code before creating a PR
• Remove any unused imports

Inside the 'lib\models' folder, create a new file called 'Challenge.dart'.

The path of the file should be: lib\models\Challenge.dart

It should include the following variables:

• Name
• Description
• Difficulty
• Category
• Thumbnail

Note: All of the variables are strings except for the difficulty. The thumbnail will store a reference to a picture that is uploaded to firebase.

Create a base Button that can be customized upon initialization.

For example, we have a base TextField with a color attribute that is red.
We should be able to change its color and any other attribute, especially its text.

This issue is similar to #25

Notes:

• Update your local project before working on the issue
• File names should use the CamelCase convention
• Variable names should use the lowerCamelCase convention
• Frequently used components should be placed inside the lib/components folder
• Pages should be placed inside the lib/pages folder
• Format your code before creating a PR
• Remove any unused imports

This is the design for the second page of the signup process. Create a new page identical to the above picture. No functionality is needed.

Use the chips_choice_null_safety library to build the chips.

Don't build/add the progress bar and the Next button.

Use SingleChildScrollView as a parent widget to avoid overflow.

Notes:

• Update your local project before working on the issue
• File names should use the CamelCase convention
• Variable names should use the lowerCamelCase convention
• Frequently used components should be placed inside the lib/components folder
• Pages should be placed inside the lib/pages folder
• Format your code before creating a PR
• Remove any unused imports

After issue #5 is closed.

Add a hamburger icon to the topbar to the left which toggles a side menu.

The side menu should contain the following items:

• Home Page with a home icon
• Leaderboards with a random icon (for now)

Notes:

• Don't add any functionality.
• Each component should be in a separate file located in the 'components' folder in the 'lib' folder.

Inside the 'lib\models' folder, create a new file called 'User.dart'.

The path of the file should be: lib\models\User.dart

The user model should include the following variables:

1. First Name
2. Last Name
3. Email
4. Password
5. Difficulty Level

Only some files in the lib folder are following similar order, some files are named in camelCase, some are in Uppercase, some are in snake_case, it should all named in a similar naming convention.

After issue #5 is closed.

Add a rounded profile picture widget in the top bar to the right.

Notes:

• Don't add any functionality.
• Each component should be in a separate file located in the 'components' folder in the 'lib' folder.

Notes:

• Don't add any functionality.
• Each component should be in a separate file located in the 'components' folder in the 'lib' folder.

This is the design for the third page of the signup process. Create a new page identical to the above picture. No functionality is needed.

Use the chips_choice_null_safety library to build the chips.

The progress bar, which is located at the top, is excluded from the page.
The Next button, which is located at the bottom, is excluded from the page.

Use SingleChildScrollView as a parent widget to avoid overflow.

Notes:

• Update your local project before working on the issue
• File names should use the CamelCase convention
• Variable names should use the lowerCamelCase convention
• Frequently used components should be placed inside the lib/components folder
• Pages should be placed inside the lib/pages folder
• Format your code before creating a PR
• Remove any unused imports

Create a base TextField that can be customized upon initialization.

For example, we have a base TextField with a color attribute that is red.
Usage 1: We should be able to change its color
Usage 2: We should be able to change the value of its 'keyboardType' attribute and such.

The login page should include the following:

• Email input bar
• Password input bar
• Reset password button
• Login button

Notes:

• Don't add any functionality.
• Each component should be in a separate file located in the 'components' folder in the 'lib' folder.
• Place the login page in the 'pages' folder.

The popup window should include the following:

• The following text: "How are you feeling right now?"
• A slider with 5 values: Awful (1), Not Good (2), Fine (3), Very Good (4), Great (5)
• A button to close the popup window (the functionality of the button should be in a separate function since background work will be added later)

Nice to have:

• The slider would change color depending on the value selected
• Represent the values with emojis instead of text
• The emojis animate a little once the selected value changes.

Notes:

• Don't add any functionality.
• Each component should be in a separate file located in the 'components' folder in the 'lib' folder.
• Place the popup window in the 'components' folder.
• The code should include comments where necessary
• Set the maximum value of the slider to 5 and the step to 1

The sign-up should include the following:

• First Name Input Bar
• Last Name Input Bar
• Email Input Bar
• Password Input Bar
• Confirmation Password Input Bar
• Sign up button

Leave some space after each input bar to show errors.

Notes:

• Don't add any functionality.
• Each component should be in a separate file located in the 'components' folder in the 'lib' folder.
• Place the sign up page in the 'pages' folder.

This is the design for the first page of the signup process. Create a new page identical to the above picture. No functionality is needed.

For the Occupation and Location sections, use the component being developed in issue #33
For the other sections, use the chips_choice_null_safety library to build the chips.

Don't build/add the Next button.

Use SingleChildScrollView as a parent widget to avoid overflow.

Notes:

• Update your local project before working on the issue
• File names should use the CamelCase convention
• Variable names should use the lowerCamelCase convention
• Frequently used components should be placed inside the lib/components folder
• Pages should be placed inside the lib/pages folder
• Format your code before creating a PR
• Remove any unused imports

The home page should have the following:

• A red Topbar
• The name of the app "AnxietyGo" in the middle

Notes:

• Don't add any functionality.
• Each component should be in a separate file located in the 'components' folder in the 'lib' folder.
• Place the home page in the 'pages' folder.

Create two topics:

• Affirmations
• Mood

Use the searchfield library to build this component.

We need this component to change the styling of the original widget only. The way we initialize the widget should stay the same.

Notes:

• Update your local project before working on the issue
• File names should use the CamelCase convention
• Variable names should use the lowerCamelCase convention
• Frequently used components should be placed inside the lib/components folder
• Pages should be placed inside the lib/pages folder
• Format your code before creating a PR
• Remove any unused imports