ERPNext Game Server Hosting Storefront
Budget: ₹18,000 – ₹20,000 INR
Scope of Work (SOW): Modular Premium Storefront Website on Frappe/ERPNext
1) Project Overview
Develop a premium storefront website for a game server hosting company using the Frappe Framework, compatible with ERPNext, with a focus on modular architecture, dynamic content, and template-driven pages.
The website must allow the client to manage products, pricing, locations, and marketing content from ERPNext, and have the storefront update dynamically. The client will implement and maintain WEMX API calls; the freelancer must provide the backend structure and integration hooks to support that workflow.
2) Goals
• Premium UI/UX for a modern hosting provider storefront.
• ERPNext-managed catalog: games, plans, pricing options, locations, “Why Us” sections.
• Dynamic product pages generated from templates (no one-off coding for each server/game).
• Fully modular section system so the client can create new pages using prebuilt components.
• Clean architecture and documentation so the client can extend and maintain independently.
⸻
3) Platform and Architecture Requirements
3.1 Framework
• Must be built on Frappe Framework (latest stable compatible with client environment).
• Must remain compatible with ERPNext (prefer delivery as a custom Frappe app to preserve modularity and upgrade safety).
• Use Frappe Website features (Web Templates, Web Pages, Jinja templates, etc.) appropriately.
3.2 Separation of Concerns
• Storefront logic must be contained in a dedicated Frappe app/module.
• No direct edits to core ERPNext code.
• Configuration should be in site config / environment variables; no secrets hardcoded.
3.3 WEMX Handling (Explicit Boundary)
• Freelancer is not responsible for implementing WEMX API calls.
• Freelancer must provide:
• Clean service layer interfaces / hooks where the client can add WEMX logic
• Data mapping fields (e.g., storing WEMX plan IDs)
• Optional stub/mock methods to demonstrate the flow without real WEMX calls
• The storefront must be built so that the “Order/Deploy” flow can be attached cleanly (redirect/session handoff pattern).
⸻
4) Functional Requirements
4.1 Core Pages (Required)
1. Home Page
• Premium hero, featured products, trust signals, CTA
2. Why Us Page
• Fully modular marketing sections editable in ERPNext
3. Locations Page
• Locations list + interactive map
• Locations managed in ERPNext and reflected on site
4. Game/Server Catalog Page
• Lists available games/server offerings from ERPNext
5. Game/Server Detail Page (Dynamic Template Page)
• Clicking a game creates/opens a templated page
• Shows multiple pricing options (plans/variants/billing cycles)
• CTA to “Deploy/Order” (calls a placeholder/hook provided for client WEMX logic)
6. FAQ Page
7. Contact Page
8. Legal Pages
• Terms/Privacy placeholders acceptable
4.2 Dynamic Pricing and Updates (Required)
• Pricing edited in ERPNext must reflect on storefront pages without code changes.
• Define and implement a documented approach for:
• Live read from ERPNext DocTypes (preferred), and
• Optional caching with documented invalidation behavior
4.3 Product Selection & Plan Options (Required)
• Each game/server has:
• A set of plan options (variants)
• Attributes (RAM/CPU/Storage/Slots, etc.)
• Optional billing cycles
• The UI must display plan cards or a pricing table from ERPNext data.
• “Order” action must call a backend hook function (stubbed) that the client can extend to integrate WEMX.
⸻
5) Modularity and Templating Requirements (Non-Negotiable)
5.1 Reusable Section Library
Deliver a minimum of 10–14 reusable page sections/components, configurable via ERPNext, such as:
• Hero (2 variants)
• Feature grid
• Feature comparison
• Pricing table
• Testimonials
• Stats strip (uptime, network, etc.)
• FAQ accordion
• CTA banners
• Icon/text rows
• Locations/map embed section
• “How it works” steps
• Trust badges/partners strip
5.2 Page Creation Workflow (Client Self-Service)
• Client must be able to create a new page using:
• A predefined template structure, and
• Reusable sections with ERPNext-managed content
• No developer involvement required for standard page creation.
5.3 Dynamic Route Templates
• Game/server detail pages must be template-driven using slugs (e.g., /games/rust, /games/minecraft).
• Adding a new “Game” record creates a working page automatically.
⸻
6) Data Model Requirements (ERPNext / Frappe DocTypes)
Freelancer must implement DocTypes (or leverage ERPNext website item patterns) to support:
6.1 Game/Server Offering (DocType)
• Name, slug, status (active/coming soon)
• Short/long description
• Feature highlights
• Hero/banner image
• Available locations (relationship)
• Plan list (relationship)
• Optional: SEO metadata
6.2 Plan / Package (DocType)
• Plan name, display order
• Attributes: RAM/CPU/Storage/Slots/etc.
• Price fields and billing cycle fields (or a child table for variants)
• WEMX mapping fields (e.g., wemx_product_id, wemx_plan_id) for client use
6.3 Location (DocType)
• Name, region/city
• Latitude/longitude
• Status (Active/Coming Soon/Maintenance)
• Optional: notes (latency/network)
6.4 Page Sections (DocType)
• Section type (hero/features/pricing/etc.)
• Content fields per section type
• Sort ordering and enable/disable
• Page assignment
⸻
7) Design Requirements (Premium Look)
• Must look premium and comparable to leading hosting providers.
• Freelancer must research competitor game server hosting websites and align UI patterns (hero, plan cards, trust signals, etc.).
• Responsive (mobile/tablet/desktop).
• Consistent typography, spacing, buttons, cards.
Note: Freelancer does not design a logo. Client will provide branding or use a temporary placeholder.
⸻
8) Deliverables
1. Custom Frappe app containing storefront implementation
2. All required pages + templates
3. DocTypes and configuration for dynamic content (Games, Plans, Locations, Page Sections)
4. Reusable section library (10–14 components)
5. “Order/Deploy” integration hook points (stubbed; client will add WEMX calls)
6. Admin documentation:
• How to add a new game/server
• How to edit pricing and plan attributes
• How to manage locations and map
• How to build a new page using sections/templates
7. Deployment documentation:
• Bench install steps
• Any required site configs
• Caching behavior (if implemented)
⸻
9) Acceptance Criteria (Pass/Fail)
• Updating a plan price in ERPNext updates storefront pricing correctly.
• Adding a new game/server record generates a functioning detail page via template route.
• Locations managed in ERPNext render on Locations page + map.
• Client can create a new marketing page using templates/sections without code changes.
• “Order” button calls a documented backend hook/stub suitable for client WEMX integration.
• Code is modular, documented, and upgrade-safe (no core edits).
⸻
10) Budget
• Fixed budget: ₹20,000 INR
• Freelancer must propose the best achievable implementation within this budget and explicitly list any exclusions.
⸻
11) Freelancer Requirements
• Proven Frappe/ERPNext website experience (templates, DocTypes, routing)
• Can produce modular, maintainable code and documentation
• Portfolio links preferred
1) Project Overview
Develop a premium storefront website for a game server hosting company using the Frappe Framework, compatible with ERPNext, with a focus on modular architecture, dynamic content, and template-driven pages.
The website must allow the client to manage products, pricing, locations, and marketing content from ERPNext, and have the storefront update dynamically. The client will implement and maintain WEMX API calls; the freelancer must provide the backend structure and integration hooks to support that workflow.
2) Goals
• Premium UI/UX for a modern hosting provider storefront.
• ERPNext-managed catalog: games, plans, pricing options, locations, “Why Us” sections.
• Dynamic product pages generated from templates (no one-off coding for each server/game).
• Fully modular section system so the client can create new pages using prebuilt components.
• Clean architecture and documentation so the client can extend and maintain independently.
⸻
3) Platform and Architecture Requirements
3.1 Framework
• Must be built on Frappe Framework (latest stable compatible with client environment).
• Must remain compatible with ERPNext (prefer delivery as a custom Frappe app to preserve modularity and upgrade safety).
• Use Frappe Website features (Web Templates, Web Pages, Jinja templates, etc.) appropriately.
3.2 Separation of Concerns
• Storefront logic must be contained in a dedicated Frappe app/module.
• No direct edits to core ERPNext code.
• Configuration should be in site config / environment variables; no secrets hardcoded.
3.3 WEMX Handling (Explicit Boundary)
• Freelancer is not responsible for implementing WEMX API calls.
• Freelancer must provide:
• Clean service layer interfaces / hooks where the client can add WEMX logic
• Data mapping fields (e.g., storing WEMX plan IDs)
• Optional stub/mock methods to demonstrate the flow without real WEMX calls
• The storefront must be built so that the “Order/Deploy” flow can be attached cleanly (redirect/session handoff pattern).
⸻
4) Functional Requirements
4.1 Core Pages (Required)
1. Home Page
• Premium hero, featured products, trust signals, CTA
2. Why Us Page
• Fully modular marketing sections editable in ERPNext
3. Locations Page
• Locations list + interactive map
• Locations managed in ERPNext and reflected on site
4. Game/Server Catalog Page
• Lists available games/server offerings from ERPNext
5. Game/Server Detail Page (Dynamic Template Page)
• Clicking a game creates/opens a templated page
• Shows multiple pricing options (plans/variants/billing cycles)
• CTA to “Deploy/Order” (calls a placeholder/hook provided for client WEMX logic)
6. FAQ Page
7. Contact Page
8. Legal Pages
• Terms/Privacy placeholders acceptable
4.2 Dynamic Pricing and Updates (Required)
• Pricing edited in ERPNext must reflect on storefront pages without code changes.
• Define and implement a documented approach for:
• Live read from ERPNext DocTypes (preferred), and
• Optional caching with documented invalidation behavior
4.3 Product Selection & Plan Options (Required)
• Each game/server has:
• A set of plan options (variants)
• Attributes (RAM/CPU/Storage/Slots, etc.)
• Optional billing cycles
• The UI must display plan cards or a pricing table from ERPNext data.
• “Order” action must call a backend hook function (stubbed) that the client can extend to integrate WEMX.
⸻
5) Modularity and Templating Requirements (Non-Negotiable)
5.1 Reusable Section Library
Deliver a minimum of 10–14 reusable page sections/components, configurable via ERPNext, such as:
• Hero (2 variants)
• Feature grid
• Feature comparison
• Pricing table
• Testimonials
• Stats strip (uptime, network, etc.)
• FAQ accordion
• CTA banners
• Icon/text rows
• Locations/map embed section
• “How it works” steps
• Trust badges/partners strip
5.2 Page Creation Workflow (Client Self-Service)
• Client must be able to create a new page using:
• A predefined template structure, and
• Reusable sections with ERPNext-managed content
• No developer involvement required for standard page creation.
5.3 Dynamic Route Templates
• Game/server detail pages must be template-driven using slugs (e.g., /games/rust, /games/minecraft).
• Adding a new “Game” record creates a working page automatically.
⸻
6) Data Model Requirements (ERPNext / Frappe DocTypes)
Freelancer must implement DocTypes (or leverage ERPNext website item patterns) to support:
6.1 Game/Server Offering (DocType)
• Name, slug, status (active/coming soon)
• Short/long description
• Feature highlights
• Hero/banner image
• Available locations (relationship)
• Plan list (relationship)
• Optional: SEO metadata
6.2 Plan / Package (DocType)
• Plan name, display order
• Attributes: RAM/CPU/Storage/Slots/etc.
• Price fields and billing cycle fields (or a child table for variants)
• WEMX mapping fields (e.g., wemx_product_id, wemx_plan_id) for client use
6.3 Location (DocType)
• Name, region/city
• Latitude/longitude
• Status (Active/Coming Soon/Maintenance)
• Optional: notes (latency/network)
6.4 Page Sections (DocType)
• Section type (hero/features/pricing/etc.)
• Content fields per section type
• Sort ordering and enable/disable
• Page assignment
⸻
7) Design Requirements (Premium Look)
• Must look premium and comparable to leading hosting providers.
• Freelancer must research competitor game server hosting websites and align UI patterns (hero, plan cards, trust signals, etc.).
• Responsive (mobile/tablet/desktop).
• Consistent typography, spacing, buttons, cards.
Note: Freelancer does not design a logo. Client will provide branding or use a temporary placeholder.
⸻
8) Deliverables
1. Custom Frappe app containing storefront implementation
2. All required pages + templates
3. DocTypes and configuration for dynamic content (Games, Plans, Locations, Page Sections)
4. Reusable section library (10–14 components)
5. “Order/Deploy” integration hook points (stubbed; client will add WEMX calls)
6. Admin documentation:
• How to add a new game/server
• How to edit pricing and plan attributes
• How to manage locations and map
• How to build a new page using sections/templates
7. Deployment documentation:
• Bench install steps
• Any required site configs
• Caching behavior (if implemented)
⸻
9) Acceptance Criteria (Pass/Fail)
• Updating a plan price in ERPNext updates storefront pricing correctly.
• Adding a new game/server record generates a functioning detail page via template route.
• Locations managed in ERPNext render on Locations page + map.
• Client can create a new marketing page using templates/sections without code changes.
• “Order” button calls a documented backend hook/stub suitable for client WEMX integration.
• Code is modular, documented, and upgrade-safe (no core edits).
⸻
10) Budget
• Fixed budget: ₹20,000 INR
• Freelancer must propose the best achievable implementation within this budget and explicitly list any exclusions.
⸻
11) Freelancer Requirements
• Proven Frappe/ERPNext website experience (templates, DocTypes, routing)
• Can produce modular, maintainable code and documentation
• Portfolio links preferred