Repository navigation
#8 Implement About page structure and update to new design layouts - #41
Merged
Merged
Conversation
iamfrogribbit
approved these changes
Aug 10, 2026
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.
Change Summary
Implemented the frontend structure for EEWA's About page. The layout features an updated background gradient blending into a soft cream base, a widened and centered accent divider line, and a dynamic cascading color scheme across the Vision, Values, and Mission informational components. A dedicated history placeholder section and the team showcase layout were also established to align the application with the figma design.
Change Form
[x] The pull request title has an issue number
[x] The change works by "Smoke testing" or quick testing
[ ] The change has tests
Reason: This PR focuses strictly on the visual frontend layout, design structure, and static components. Automated unit tests are not applicable at this stage but can be introduced once interactive features or dynamic state management are added.
[x] The change has documentation
Reason: Clean code structure, inline comments detailing layout choices, and a descriptive PR overview have been provided.
Other Information
Please note that the History Section currently uses standard Lorem Ipsum placeholder text as the real copy is still pending. For images of the team members these will need to be dropped into the project's public/images/ directory to display the actual images on the websites.
Related issue