Add professional frontend public page sections#212
Add professional frontend public page sections#212Pushpindersingh-2027 wants to merge 2 commits 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: 49028c3b91
ℹ️ 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".
| </div> | ||
| </section> | ||
|
|
||
| <footer className="autoaudit-footer"> |
There was a problem hiding this comment.
The new global footer inside App is rendered whenever showPublicEnhancements is true, but the /, /about, and /contact route components already include LandingFooter (LandingPage.tsx, AboutUs.tsx, ContactPage.tsx). As a result, those pages now render two footers back-to-back, which adds duplicated content/landmarks and degrades the public-page UX. This should be consolidated to a single footer source per page.
Useful? React with 👍 / 👎.
|
Thanks for the review. I have fixed the duplicate footer issue by removing the global footer from App.tsx. The public pages now use only the existing LandingFooter component, so /, /about, and /contact no longer render two footers. |
| ============================================================================ */ | ||
|
|
||
| /* Audit Readiness Section */ | ||
| .autoaudit-readiness-section { |
There was a problem hiding this comment.
This seems to be countering the migration from vanilla CSS to TailwindCSS
| password: string; | ||
| }; | ||
|
|
||
| const LoadingScreen = (): JSX.Element => ( |
There was a problem hiding this comment.
I like the Loading screen change, keep this
| /> | ||
| </Routes> | ||
|
|
||
| {showPublicEnhancements && ( |
There was a problem hiding this comment.
What's the motivation? Do you have a screenshot of how this looks like?
2 participants
This PR improves the public-facing AutoAudit frontend by adding professional sections that better communicate the platform’s audit and compliance value.
Changes made:
Testing: