mohlomicliffmakhetha/mohlomicliffmakhetha-marketspace

Purpose and Scope

Static front-end prototype for a Facebook Marketplace-style varsity project. It presents a landing experience, category search pages, service/provider pages, user views, and an error state. No backend, build system, API integration, or server runtime is present in the repository.

Entry Points and Navigation Surface

• Primary entry point: index.html

• Supporting page-level entry points: SearchEnginPageAccom.html, SearchEnginPageProds.html, SearchEnginePagesServ.html

• The application is a multi-page static site: navigation is expected to occur through HTML links between independently loaded documents rather than client-side routing.

Marketplace Search Categories

The marketplace is partitioned into distinct search/result experiences:

• Accommodation: SearchEnginPageAccom.html

• Products: SearchEnginPageProds.html

• Services: SearchEnginePagesServ.html

These pages form the core discovery flow: a user enters from index.html, selects a marketplace category, and navigates to the corresponding search page.

Service Provider Experience

Provider-focused content is separated from general marketplace search:

• Provider/service listing or services department page: ProviderServicesPage.html

• Basic provider user guidance/profile-related content: AboutBasicUserProviderManual.html

This boundary suggests service providers have dedicated informational or operational pages rather than being represented only as generic product listings.

User and Error States

• User-facing account/profile view: userViewPage.html

• Failure or unavailable-route state: ErrorPage.html

userViewPage.html is the likely destination for viewing a marketplace participant, while ErrorPage.html supplies a fallback page for invalid navigation or failed user flows.

Control Flow and Boundaries

The primary control flow is document-based:

1. Load index.html.

2. Navigate to a category search page or provider-oriented page.

3. Open a user-oriented view through userViewPage.html.

4. Fall back to ErrorPage.html when a destination cannot be served or found.

Each HTML file is an architectural boundary: pages must carry their own markup, styling references, and navigation links because no shared application runtime, component framework, routing layer, or data service is included.

Runtime and Infrastructure

The repository requires only a browser and static-file hosting. Material infrastructure is limited to an HTTP/static hosting environment if deployed; there are no repository-visible databases, authentication providers, marketplace APIs, payment services, or backend endpoints.