ritikrikm/nimble

Purpose and Runtime

This is a Create React App single-page marketing/landing-site frontend, likely for Nimble and related promotional content. It runs in the browser via React; npm start serves development on port 3000 and npm run build emits a static production bundle. Browser-facing deployment assets include public/index.html, public/manifest.json, and public/_redirects.

Application Entry and Composition

src/index.js mounts the React application and loads global styles from src/index.css. src/App.js is the primary composition/root boundary, with app-level presentation in src/App.css. The application is organized as page-level content assembled from reusable visual components rather than a backend-driven domain layer.

Page-Level Content Areas

The page directory represents the main independently maintainable site sections:

• General and informational pages: src/pages/Home.js, src/pages/About.js, src/pages/Contact.js.

• Legal/account pages: src/pages/PrivacyPolicies.js, src/pages/Terms.js, src/pages/DeleteAccount.js.

• Campaign/product landing experiences: src/pages/NimbleLandingPage.js, src/pages/NimbleLandingPage2.js, src/pages/GoodieBagPage.js.

Navigation and exact routing mechanics are not evident from the supplied tree; integration likely occurs through the root application and header/footer composition.

Shared Experience Components

The reusable component layer defines the landing-page UI system:

• Global chrome: src/component/Header.jsx, src/component/AppFooter.jsx.

• Hero and feature storytelling: src/component/HeroSection.jsx, src/component/Hero2.js, src/component/FeatureBlock.jsx.

• Promotional/catalog interactions: src/component/CarouselComponent.js, src/component/CategorySlider.js, src/component/ProductCard.js.

• Conversion-oriented elements: src/component/Form.js, src/component/StoreButton.jsx, src/component/Countdown.js.

Pages consume these components to produce campaign-specific layouts; components are presentation-oriented and paired with scoped stylesheet files under src/styles/.

Form Submission Boundary

src/component/Form.js is the client-side form boundary. public/submit_form.php is the only server-side endpoint artifact in the repository, indicating form submissions may cross from the static React bundle to a PHP handler deployed alongside public assets. No database, API client, authentication service, or server application is represented in the tree.

Asset and Styling Pipeline

Static browser assets reside in public/, including images, icons, robots directives, and PWA metadata. Source-managed visual assets are under src/images/ and src/font/, including bundled Sweet Sans Pro font files. Styling is layered across global files (src/css/root.css, src/css/style.css) and component/page CSS (src/styles/HeroSection.css, src/styles/GoodieBagPage.css, src/styles/header.css), making CSS and asset imports central dependencies for each UI section.

Delivery and Infrastructure

Create React App provides the JavaScript build, development server, and test runtime. Production is static-host compatible; public/_redirects suggests redirect rules for a hosting platform that supports this convention. The PHP submission handler requires hosting with PHP execution, creating the key deployment constraint: static frontend hosting alone may not support the contact/form workflow.