Refactor frontend layout, enhance landing content, and improve documentation - #1
Merged
Conversation
- Added a shared frontend shell with consistent header, footer, and backend health status across the landing, about, license, and verification routes. - Moved the verification workflow to the direct /app route while preserving upload, queue, verification, export, and backend API behavior. - Replaced the root route with a compact resizable landing page that uses stronger product copy, evidence-backed performance notes, and clear actions for verification and source review. - Added static About and License pages with exact Vercel rewrites so direct refresh works for /about, /app, and /license. - Updated frontend route tests and project documentation to reflect the new public routes, static-page behavior, deployment links, and prototype boundaries. - Kept backend code, API contracts, OpenAI extraction logic, verification logic, authentication, database behavior, and persistent upload storage unchanged.
* Updated the landing page overview with clearer product purpose, verification capability, review audience, scope, performance, and documentation sections. * Replaced the landing eyebrow with a page subtitle that mirrors the header brand treatment. * Refined landing page title, subtitle, divider, section heading, link, and paragraph-to-bullet spacing styles. * Updated route coverage for the revised landing content and About page inline link. * Preserved existing backend API contracts and verification behavior. * Verified repository hygiene checks and the frontend production build.
* Reduced the landing info-card paragraph-to-bullet spacing from 1.65rem to 0.825rem. * Left landing page copy, structure, and application behavior unchanged. * Preserved existing backend API contracts and verification behavior. * Verified repository hygiene checks and the frontend production build.
- Updates `frontend/src/components/shared/AppFooter.jsx` to render a structured shared footer with the CLA logo, product name, prototype version, persistent independent prototype disclaimer, footer navigation, and Apache License copyright text. - Updates `frontend/src/styles/index.css` to use a dark navy footer layout, a subtle top divider, responsive link alignment, mobile stacking, and additional bottom spacing below the copyright row. - Updates `frontend/src/App.test.jsx` with focused app shell assertions for the footer identity, disclaimer, navigation links, and licensing text. - Updates `README.md`, `docs/frontend/components.md`, and `docs/reference/frontend-file-reference.md` to document the persistent independent prototype footer disclosure and expanded shared footer role. - Preserves existing footer link targets for Source Code, License, About, and Verification Tool without changing header, routing, verification, export, or backend behavior.
- Adds the same subtle white divider treatment used by the footer to the bottom edge of the header. - Preserves the existing header layout, navigation alignment, spacing, colors, and responsive behavior. - Leaves the existing footer styling unchanged while keeping the page shell visually consistent.
- Updated inline landing documentation card links to use a muted navy-blue color that fits the existing visual system. - Refined link underline styling with improved thickness, offset, and softer decoration color. - Changed hover styling to darken the blue text and keep the underline blue without increasing underline thickness. - Added an accessible focus-visible outline for keyboard navigation. - Added visited-link styling that keeps visited links muted gray and avoids default purple browser link behavior.
- Expanded the About page into a reviewer-focused architecture and implementation summary with data-driven content, structured cards, and scoped styling. - Updated About page section and card titles for cleaner hierarchy, consistent title casing, and repository documentation links. - Reworked the prototype notice to clarify the independent prototype status and human review boundary. - Added documented sample-file speed results, benchmark result context, provider usage notes, and benchmark method guidance to the About performance section. - Documented performance target placeholders and the latest local validation snapshot in adjacent repository documentation. - Updated About route assertions to cover the expanded content, disclaimer placement, documentation links, and performance sections.
- Removed the visible grouped container styling from the primary header navigation. - Converted primary navigation links to flat text with transparent inactive, hover, and active states. - Preserved the active route indicator with a thin gold underline and visible keyboard focus styling.
- Wrapped the header status label so the dot and text can animate independently. - Reserved a fixed badge width and height to prevent layout shifts across checking, online, and offline states. - Added a lightweight dot-then-text fade with reduced-motion handling while keeping the checking state visually hidden. - Centered the online and offline labels within the badge while keeping the status dot anchored on the left.
- Split the previous combined CI workflow into backend, frontend, and repo hygiene checks. - Added backend coverage reporting and expanded API, CORS, config, batch, and file-validation contract tests. - Added frontend coverage reporting and expanded API-client, route, export, and validation tests. - Added repo hygiene checks for whitespace, generated artifacts, secret-like values, skipped tests, and internal-reference guards. - Updated documentation to describe the new CI checks, local validation commands, branch protection expectations, and Vercel/Render dashboard gating responsibilities.
- Updated the root README as a concise project entrypoint with setup, architecture, environment, testing, deployment, security, and documentation navigation. - Refreshed the canonical documentation index and aligned repository documentation links with the current docs structure. - Clarified API endpoint documentation, request and response contracts, required fields, batch behavior, and frontend/backend API usage. - Updated frontend documentation for current routing, page structure, components, styling, and file-level references. - Updated backend and reference documentation for current backend files, security headers, CORS tests, configuration, scripts, workflows, and repository structure. - Removed synthetic benchmark and provider-cost targets from authoritative performance documentation and documented the remaining measured-cost gap. - Strengthened testing, troubleshooting, security, deployment, and maintenance documentation with current validation steps and safe operational guidance. - Preserved the take-home documentation exclusion and avoided changes to application code, deployment configuration, CI workflows, package files, scripts, tests, and environment files.
- Added a process-local daily verification unit cap with configurable enablement, unit limit, window length, and OpenAI output token settings. - Enforced the cap before single-label and batch verification work, returning a 429 response with rate-limit headers when the daily pool is exhausted. - Limited OpenAI extraction output tokens and made provider warmup run once per model per process. - Added backend and frontend tests for the limiter, API contract, provider request parameters, warmup behavior, and existing daily-limit error rendering. - Updated environment examples, documentation, and the visible footer version reference from v1.0.0 to v2.0.0.
- Added prototype-safe Privacy Policy and Terms of Use pages with SPA routing and Vercel rewrites. - Added shared static page primitives for shells, headers, sections, cards, callouts, tables, and actions. - Standardized static page typography tokens, spacing, cards, dividers, tables, and mobile layout across informational pages. - Migrated About, Privacy Policy, Terms of Use, License, and landing information content to the shared static page structure. - Grouped footer links into Project and Legal sections while preserving the Home, About, and Verification Tool top navigation. - Added the compact upload AI review notice and kept its frontend test coverage. - Updated focused route, footer, legal page, license page, About page, and upload notice tests. - Updated frontend component, styling, and file reference documentation for the static page system.
- Added shared skeleton primitives, tests, and CSS-only shimmer styles that use existing design tokens and reduced-motion handling. - Replaced the selected-label verifying spinner with a result-shaped skeleton that matches the completed result layout. - Preserved accessible loading feedback with a screen-reader status while leaving the queue item Verifying pill as the visible loading indicator. - Updated verification workflow tests for pending, success, error, and batch visibility states. - Documented the skeleton component, styling partial, and queue-state behavior in the frontend docs.
- Added a keyed page body transition wrapper so route content remounts and animates on navigation. - Added lightweight opacity and translate animations for page body content and top-level panels. - Added a reduced-motion override so users who prefer less motion receive static content. - Added a route shell test that verifies the transition wrapper contains route content while the shared header and footer remain outside it.
- Render modal and page notification overlays through a shared body portal so fixed positioning is relative to the viewport. - Lock background scrolling while dismissible dialogs are open and restore body overflow when they close. - Raise page notification banners below the header while preserving dismissal, tone, and replacement behavior. - Update dialog and notification tests to cover body-mounted overlays, outside-click dismissal, Escape dismissal, and scroll restoration.
- Added Privacy Policy and Terms of Use links to the project README and deployment links so the documented public endpoints include every available legal route. - Expanded frontend architecture and overview documentation to reflect /privacy and /terms as supported application paths. - Updated Vercel deployment documentation and repository references to document SPA rewrites for the new legal routes. - Updated production checklist and known gaps notes to include footer validation and legal-review tasks aligned with privacy, terms, and AI-use disclosures. - Updated documentation that references environment scripts and deployment configuration so verifications against supported paths remain synchronized.
- Reframed the root README and reviewer guide as formal evaluator-facing implementation documentation while preserving setup instructions, deployment URLs, commands, tools, assumptions, trade-offs, limitations, and performance context. - Converted security, deployment, source-control, troubleshooting, and validation notes from directive warnings into descriptive implementation boundaries without changing documented behavior. - Updated architecture, backend, frontend, API, maintenance, take-home, and sample-data documentation for consistent terminology, current develop-branch details, and reviewer-facing tone.
- Added backend comments and docstrings for application setup, route contracts, provider isolation, upload validation, service orchestration, rate limiting, verification rules, response schemas, and backend test intent. - Added frontend comments for routing, API boundaries, queue state, upload handling, object URL cleanup, browser export behavior, shared components, page content modules, and frontend test intent. - Added CSS, workflow, environment example, Vite, ESLint, and local script comments that document layout sections, validation-only CI flows, deployment assumptions, and local setup boundaries. - Preserved runtime behavior, public interfaces, CSS selectors and values, DOM structure, tests, dependencies, generated outputs, and documentation files.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
nicolasgioanni
commented
Jul 1, 2026
nicolasgioanni
left a comment
nicolasgioanni
left a comment
Owner
Author
There was a problem hiding this comment.
Merge conflicts resolved
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
1 participant
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.
This pull request restructures and improves the project's GitHub Actions CI workflows by separating backend, frontend, and repository hygiene checks into dedicated workflow files. It also enhances test coverage reporting and introduces additional repository safety checks.
CI Workflow Restructuring:
.github/workflows/ci.ymlinto two distinct workflows:backend-ci.ymlfor backend validation andfrontend-ci.ymlfor frontend validation, each with their own job definitions and environment setups. [1] [2]Backend CI Improvements:
OPENAI_API_KEYin the backend CI environment to facilitate provider mocking during tests.Frontend CI Enhancements:
frontend-ci.yml) that runs linting, type checking, coverage-enabled tests, and build steps, with coverage output uploaded as an artifact.Repository Hygiene Automation:
repo-hygiene.ymlworkflow to enforce repository safety, including checks for whitespace errors, tracked generated files, secret-looking strings, skipped tests, and internal references, as well as reporting TODOs and FIXMEs.