How heartleon92-create/profilepublicmain works
The tree suggests a static product and pricing catalog, with separate product-series pages and pages for profiles, talent, orders, and tracking. A plausible user journey is to enter the site, browse a series, inspect product details, and proceed to an order; the dashed links mark this as an inference, not a verified runtime flow. The JSON files suggest business, product, and profile data. With no README or source excerpts, implementation details and relationships among these pages cannot be confirmed.
Main entry points: index.html Home page · Brochure.html Brochure · Basic Price Basic prices · OS Series OS series
Components 20
Product catalog
- Brochure
Brochure.html - Basic prices
Basic Price - OS series
OS Series - Premium series
Premium - Strander prices
Strander Price
User workflow
- Home page
index.html - Product details
details.html - Packages
package.html - Talent profiles
talent.html - Order page
order.html - View tracking
viewTrack.html
Management
- Admin page
adminpage.html - Hub page
hubPage.html - Testing page
testing.html - Alice page
TR,Alice.html - AI workflow notes
Work flow noted/Profile craft AI prompt work flow.txt
Catalog data
- Business functions
json/business_function.json - Product data
json/product.json - Profile functions
json/profile_function.json
Other components
- Visitor
Connections 11
- Visitor → Home page: opens
- Home page → Brochure: offers
- Visitor → Basic prices: browses
- Visitor → OS series: browses
- Visitor → Premium series: browses
- Visitor → Strander prices: browses
- Visitor → Product details: views
- Visitor → Packages: views
- Visitor → Talent profiles: views
- Visitor → Order page: submits
- Visitor → View tracking: checks