Add audit readiness section and professional footer#203
Add audit readiness section and professional footer#203Pushpindersingh-2027 wants to merge 1 commit into
Conversation
Pushpindersingh-2027
requested review from
6igby,
du-dhartley and
liyunze-coding
as code owners
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0ebeb1716c
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| /> | ||
| </Routes> | ||
|
|
||
| {showMarketingFooter && ( |
There was a problem hiding this comment.
This conditional renders an additional footer for /, /about, and /contact, but each of those route components already includes LandingFooter (frontend/src/pages/Landing/LandingPage.tsx, frontend/src/pages/Landing/AboutUs.tsx, and frontend/src/pages/Contact/ContactPage.tsx). As a result, users on public pages get duplicate footer sections and the new readiness block appears after an existing footer, which breaks page structure and creates conflicting footer landmarks.
Useful? React with 👍 / 👎.
|
|
This is also from a fork - why wasn't this on a feature branch in this repository? |
liyunze-coding
left a comment
liyunze-coding
left a comment
There was a problem hiding this comment.
Can you update your changes with the TailwindCSS migrations?
|
You may close this pull request and start from scratch |
| --color-surface-1: 15 23 42; /* #0f172a Oxford Blue */ | ||
| --color-surface-2: 30 41 59; /* #1e293b Prussian Blue (Muted) */ | ||
| --color-subtle: 51 65 85;/* #334155 Charcoal (Grey) */ | ||
| --color-surface-2: 30 41 59; /* #1e293b Prussian Blue */ |
There was a problem hiding this comment.
To be honest I'm just confused about styles/global.css, it has been removed since the TailwindCSS migration and we should be using index.css and the main point of CSS
|
|
||
| /* AutoAudit Audit Readiness Section */ | ||
| .autoaudit-readiness-section { | ||
| width: 100%; |
There was a problem hiding this comment.
Please use TailwindCSS instead
4 participants
This PR improves the AutoAudit frontend by adding a professional Audit Readiness section and a refined footer for public pages.
Changes made:
Role:
Frontend Developer