Adding wireframes and stuff from last sem #900
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The .txt file is just notes about how to interpret the .json file.
Added about 1500 lines of major data, which totaled to 18 new majors. I also reformatted how you pick classes from a group of options based on discussion with other YACS developers.
Apparently I did not upload this properly last week. But added some more information based on the new data added.
Added about 12 more majors
Made a bunch new majors (estimated 8 or so)
Changed this to reflect how you pick multiple electives from a list of choices.
Included better information about the science core for all students.
Added link for figma wireframes so we can all see it
Will upload png and svg at a later point.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Note which issue number(s) this Pull Request closes. All pull requests should close an issue, if one does not exists, make one. This helps us plan and discuss before we decide on implementation
Example:
Database Changes/Migrations
If you added/modified a table, notify people of schema change here
Example:
Test Modifications
Note added unit/integration tests: (all backend changes should contain unit/integration tests with pytest)
Example:
Test Procedure
Show procedure to test functionality with a clear procedure
Example:
Photos
Show before and after, capture screenshot/gif of finished feature/bug
Additional Info
More info that would help people review your change