westfarn
fa91c4969f
## Summary - Logged-out `/` is a public landing page. Signed-in `/` still opens chat. - Adds `/pricing/`, `/privacy/`, and `/changelog/`, plus header and footer links. - Primary path is **Create account** when registration is on, and an email **waitlist** when it is off. - Titles, canonicals, Organization and Product JSON-LD, `sitemap.xml`, `robots.txt`, and `llms.txt`. - Usage counts render only from `GET /api/public/usage/`. No avatars. No founder block. No testimonials. - Closes #113, #114, #115, and #116. Needs [chat_backend#75](https://git.aimloperations.com/ai_ml_operations/chat_backend/pulls) for the waitlist and usage API, and the server-infra crawler-file change so those root files are not the SPA shell. The account and document numbers in the screenshots come from a local mock of the usage API, not production. ## Screenshots ### Landing, registration off  ### Landing, mobile  ### Landing, registration on  ### Pricing  ### Privacy  ### Changelog  ### Sign in unchanged  ## Test plan - [x] `react-scripts test` — 234 passed - [ ] Incognito `/` shows the landing page, not Sign In - [ ] Signed-in `/` still opens chat - [ ] `/account/` still redirects to `/signin/` when logged out - [ ] Waitlist POST and usage GET against the new API - [ ] `/robots.txt`, `/sitemap.xml`, and `/llms.txt` return plain text, not HTML Reviewed-on: #117
Getting Started with Create React App
This project was bootstrapped with Create React App.
Available Scripts
In the project directory, you can run:
npm start
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
npm test
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
npm run build
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
npm run eject
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
Learn More
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.