chore(journals): Vivian's Learning Journals#109
Open
vivjd wants to merge 7 commits into
Open
Conversation
There was a problem hiding this comment.
Pull request overview
Adds Vivian’s weekly learning journals to the repository as student documentation, capturing weekly progress and learning objectives across the semester.
Changes:
- Added Week 2–12 journal entries for Vivian under
student_docs/weekly_journal/. - Documented weekly summaries, learning objectives met, and concrete contributions (frontend architecture, testing, documentation, workflow).
Reviewed changes
Copilot reviewed 11 out of 11 changed files in this pull request and generated 7 comments.
Show a summary per file
| File | Description |
|---|---|
| student_docs/weekly_journal/week02/vivian.md | Adds Week 2 journal entry (prototyping + feedback loop). |
| student_docs/weekly_journal/week03/vivian.md | Adds Week 3 journal entry (design refinement + stakeholder feedback). |
| student_docs/weekly_journal/week04/vivian.md | Adds Week 4 journal entry (frontend structure + i18n strategy). |
| student_docs/weekly_journal/week05/vivian.md | Adds Week 5 journal entry (Figma-to-React collaboration work). |
| student_docs/weekly_journal/week06/vivian.md | Adds Week 6 journal entry (MSW integration + workflow tooling). |
| student_docs/weekly_journal/week07/vivian.md | Adds Week 7 journal entry (Monaco + API refactor + CI modularization). |
| student_docs/weekly_journal/week08/vivian.md | Adds Week 8 journal entry (issue-driven governance). |
| student_docs/weekly_journal/week09/vivian.md | Adds Week 9 journal entry (PR template/workflow improvements). |
| student_docs/weekly_journal/week10/vivian.md | Adds Week 10 journal entry (UI standardization + design assets). |
| student_docs/weekly_journal/week11/vivian.md | Adds Week 11 journal entry (full-stack orchestration + testing infra + docs). |
| student_docs/weekly_journal/week12/vivian.md | Adds Week 12 journal entry (navigation refinements + sync fixes + E2E expansion). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ## Learning Objectives Met | ||
|
|
||
| ### 2. Master high-fidelity prototyping and design tooling | ||
| * **Design-to-Code Implementation:** I selected and integrateed icons and Material UI (MUI) components that aligned with our Figma prototypes. I ensured the "Checker" page functionality looked and felt like the visual blueprint we designed as a sample that can be used for future reference. |
There was a problem hiding this comment.
Typo: "integrateed" should be "integrated".
Suggested change
| * **Design-to-Code Implementation:** I selected and integrateed icons and Material UI (MUI) components that aligned with our Figma prototypes. I ensured the "Checker" page functionality looked and felt like the visual blueprint we designed as a sample that can be used for future reference. | |
| * **Design-to-Code Implementation:** I selected and integrated icons and Material UI (MUI) components that aligned with our Figma prototypes. I ensured the "Checker" page functionality looked and felt like the visual blueprint we designed as a sample that can be used for future reference. |
| * **CI/CD Foundation:** I initiated the basic CI setup Pull Request. While troubleshooting the initial pipeline failures, I gained a deeper understanding of how environment-specific configurations impact automated testing, which is crucial for maintaining a stable main branch. | ||
|
|
||
| ### 5. Write technical documentation | ||
| * **Internationalization (i18n) Strategy:** I reserach and documented a roadmap for multilingual support using `i18next`. By establishing the `locales/` JSON structure early, I suggested a template for adding future language support without refactoring the core UI. THis has been intergated into the frontend architecture design accordingly. No newline at end of file |
There was a problem hiding this comment.
Typo/word form: "reserach" should be "researched" in this sentence.
Suggested change
| * **Internationalization (i18n) Strategy:** I reserach and documented a roadmap for multilingual support using `i18next`. By establishing the `locales/` JSON structure early, I suggested a template for adding future language support without refactoring the core UI. THis has been intergated into the frontend architecture design accordingly. | |
| * **Internationalization (i18n) Strategy:** I researched and documented a roadmap for multilingual support using `i18next`. By establishing the `locales/` JSON structure early, I suggested a template for adding future language support without refactoring the core UI. THis has been intergated into the frontend architecture design accordingly. |
| * **CI/CD Foundation:** I initiated the basic CI setup Pull Request. While troubleshooting the initial pipeline failures, I gained a deeper understanding of how environment-specific configurations impact automated testing, which is crucial for maintaining a stable main branch. | ||
|
|
||
| ### 5. Write technical documentation | ||
| * **Internationalization (i18n) Strategy:** I reserach and documented a roadmap for multilingual support using `i18next`. By establishing the `locales/` JSON structure early, I suggested a template for adding future language support without refactoring the core UI. THis has been intergated into the frontend architecture design accordingly. No newline at end of file |
There was a problem hiding this comment.
Capitalization typo: "THis" should be "This".
Suggested change
| * **Internationalization (i18n) Strategy:** I reserach and documented a roadmap for multilingual support using `i18next`. By establishing the `locales/` JSON structure early, I suggested a template for adding future language support without refactoring the core UI. THis has been intergated into the frontend architecture design accordingly. | |
| * **Internationalization (i18n) Strategy:** I reserach and documented a roadmap for multilingual support using `i18next`. By establishing the `locales/` JSON structure early, I suggested a template for adding future language support without refactoring the core UI. This has been intergated into the frontend architecture design accordingly. |
| * **CI/CD Foundation:** I initiated the basic CI setup Pull Request. While troubleshooting the initial pipeline failures, I gained a deeper understanding of how environment-specific configurations impact automated testing, which is crucial for maintaining a stable main branch. | ||
|
|
||
| ### 5. Write technical documentation | ||
| * **Internationalization (i18n) Strategy:** I reserach and documented a roadmap for multilingual support using `i18next`. By establishing the `locales/` JSON structure early, I suggested a template for adding future language support without refactoring the core UI. THis has been intergated into the frontend architecture design accordingly. No newline at end of file |
There was a problem hiding this comment.
Typo: "intergated" should be "integrated".
Suggested change
| * **Internationalization (i18n) Strategy:** I reserach and documented a roadmap for multilingual support using `i18next`. By establishing the `locales/` JSON structure early, I suggested a template for adding future language support without refactoring the core UI. THis has been intergated into the frontend architecture design accordingly. | |
| * **Internationalization (i18n) Strategy:** I reserach and documented a roadmap for multilingual support using `i18next`. By establishing the `locales/` JSON structure early, I suggested a template for adding future language support without refactoring the core UI. THis has been integrated into the frontend architecture design accordingly. |
|
|
||
| ### 2. Master high-fidelity prototyping and design tooling | ||
| * **Complex Component Creation:** I utilized Figma to design more complex, information-dense components required for the technical nature of the tool. | ||
| * **Legend & Visual Guides:** I implemented a betteer legend system. This involved defining specific colors and arrow types to represent different architectural relationships, ensuring that the visual data is self-explanatory for the user. |
There was a problem hiding this comment.
Typo: "betteer" should be "better".
Suggested change
| * **Legend & Visual Guides:** I implemented a betteer legend system. This involved defining specific colors and arrow types to represent different architectural relationships, ensuring that the visual data is self-explanatory for the user. | |
| * **Legend & Visual Guides:** I implemented a better legend system. This involved defining specific colors and arrow types to represent different architectural relationships, ensuring that the visual data is self-explanatory for the user. |
|
|
||
| ### 1. Develop comprehensive full-stack engineering proficiency | ||
|
|
||
| While no code was written this week, this week's work on creating hte mockup was foundational for the client side interfaces of the learning objective and understanding frontend design better. Designing the UI in detail forced me to think through the data requirements for the frontend. I now have a clearer understanding of what the server-side logic needs to provide to support the user interactions we visualized. |
There was a problem hiding this comment.
Typo: "hte" should be "the".
Suggested change
| While no code was written this week, this week's work on creating hte mockup was foundational for the client side interfaces of the learning objective and understanding frontend design better. Designing the UI in detail forced me to think through the data requirements for the frontend. I now have a clearer understanding of what the server-side logic needs to provide to support the user interactions we visualized. | |
| While no code was written this week, this week's work on creating the mockup was foundational for the client side interfaces of the learning objective and understanding frontend design better. Designing the UI in detail forced me to think through the data requirements for the frontend. I now have a clearer understanding of what the server-side logic needs to provide to support the user interactions we visualized. |
| ### 2. Master high-fidelity prototyping and design tooling | ||
| - Skill Acquisition: I actively researched and implemented Figma best practices, teaching myself how to create reusable basic components and organize layout frames effectively. Additionally, I actively researched into color design and icons for our mockup. | ||
|
|
||
| - Implementation: I successfully translated our initial abstract ideas into a concrete visual format. This included setting up specific interactions [e.g., clicking the start button, navigating between views] to simulate the user journey. I developed a color palette to use as well, which includes colors for the clean architecture diagram, functional colros for the wireframe, and basic colors for the background. |
There was a problem hiding this comment.
Typo: "colros" should be "colors".
Suggested change
| - Implementation: I successfully translated our initial abstract ideas into a concrete visual format. This included setting up specific interactions [e.g., clicking the start button, navigating between views] to simulate the user journey. I developed a color palette to use as well, which includes colors for the clean architecture diagram, functional colros for the wireframe, and basic colors for the background. | |
| - Implementation: I successfully translated our initial abstract ideas into a concrete visual format. This included setting up specific interactions [e.g., clicking the start button, navigating between views] to simulate the user journey. I developed a color palette to use as well, which includes colors for the clean architecture diagram, functional colors for the wireframe, and basic colors for the background. |
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
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.
Overview
My journals contain summaries of the work I've completed this semester. For a list of PRs I've made, please see here.
In regards to learning objective 6, please see here for the list of issues I've created.
Please contact me if there's more evidence would be helpful for any of the learning objectives!
Type of Change
(Write an
Xor a brief description next to the type or types that best describe your changes.)Checklist
(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the
[ ]into a[x]in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)Before opening your pull request:
I have performed a self-review of my changes.
I have added tests for my changes, if applicable.
I have updated the project documentation, if applicable.
(Frontend) I have added/updated text in
i18nJSON files for any new user-facing strings to support multilingual features.After opening your pull request:
I have verified that the CI tests have passed.
I have requested a review from a project maintainer, and a fellow student.
Technical Debt: If temporary workarounds or "TODOs" were used, I have opened a tracking issue to address them properly.
Questions and Comments
(Include any questions or comments you have regarding your changes.)