Project Overview
We are commissioning a simple, calm, institutional website for a large-scale MMORPG project.
The website serves as an official, informational presence (game overview, systems, lore, updates, policies).
It is not a marketing site and not a creative exercise.
This is an execution-only project.
We are not looking for:
We will provide:
Official game logo (PNG/SVG)
All website texts (final, approved copy)
Full website structure (pages, hierarchy, content blocks)
A visual mockup (for orientation only)
An official Brand & Design Manual (binding)
Your role is to implement exactly what is provided — not to invent.
B. Binding Design Governance (CRITICAL)
A formal Brand & Design Manual will be provided.
This manual is:
binding
authoritative
non-optional
You must:
✔ follow all rules defined in the manual
✔ respect spacing, hierarchy, tone, restraint, and visual discipline
✔ implement typography, color logic, and layout philosophy exactly as specified
Any deviation, reinterpretation, or “practical adjustment” without explicit written approval will result in non-acceptance of delivery.
C. Mockup Usage (Clarification)
A visual mockup may be provided for orientation only.
The Brand & Design Manual overrides the mockup at all times.
D. Scope of Work (Detailed)
1) Implement the Provided Structure
Pages and navigation exactly as provided
Correct internal linking
Consistent global elements (header, footer, navigation)
2) Implement Provided Text Content
Text placed exactly as delivered
No rewriting, shortening, rewriting for tone, or optimization
Correct semantic hierarchy (H1–H3, paragraphs, lists, tables where applicable)
3) Content-Resilient Layout (CRITICAL REQUIREMENT)
The website must remain visually stable under future content changes.
This means:
Texts may be shortened or extended
Lore sections may expand
Patch notes may grow or shrink
Headings may change length
Paragraph counts may vary
Without causing:
layout breakage
overflow
overlap
spacing collapse
manual CSS fixes
Strict requirements:
No hard-coded text heights
No fixed containers that assume copy length
No layouts that require developer intervention after content edits
The layout must adapt automatically without redesign, re-spacing, or developer assistance.
This requirement is non-negotiable.
E. Mandatory Delivery Format (ZIP – Upload & Run)
Final delivery must be:
After extraction and upload via:
…the website must:
Static or server-ready output only.
F. Technical Requirements (Must-Pass)
1. Responsiveness
Fully functional and visually correct on:
2. Cross-Browser Compatibility
Tested and consistent on:
3. Quality Standards
G. What This Project Is NOT
No copywriting or lore writing
No SEO or discoverability work
No analytics, tracking, or telemetry
No CTAs, funnels, or engagement mechanics
No redesign, modernization, or “improvements”
No animations or visual effects unless explicitly specified
No visible templates, builders, or theme artifacts
H. Deliverables
You must deliver:
One ZIP archive (complete website)
Upload-and-run functionality
Fully content-resilient layout
Optional README.txt (deployment notes only)
I. Acceptance Tests
We will verify:
Immediate functionality after upload
Correct rendering on all target devices
Cross-browser consistency
Ability to freely edit texts without layout breakage
Strict adherence to the Brand & Design Manual
J. Non-Compliance & Penalty Clause
Material Non-Compliance Conditions
The following are material conditions of this project:
ZIP “upload & run” delivery
Full responsiveness and cross-browser compatibility
Content-resilient layout
Strict adherence to the Brand & Design Manual
Failure to meet any of the above results in:
Non-acceptance of delivery
Required corrections at no additional cost
Payment conditional upon successful acceptance after retesting
Repeated failure constitutes material breach and may result in termination.
K. Confidentiality & NDA (Mandatory)
All materials, texts, structures, mockups, manuals, and information related to this MMORPG website are strictly confidential.
You may not:
Share materials
Publish or reference the project
Use screenshots or URLs in portfolios
Disclose the existence of the engagement
This obligation survives project completion or termination.
L. Pre-Screening Questions (Required)
Offers without answers to the following questions will not be considered.
Q1. ZIP Delivery
Can you deliver a single ZIP that runs immediately after upload?
YES / NO
Q2. Content-Resilient Layout
Explain how you build layouts that do not break when texts are shortened or extended.
Q3. Responsiveness
Describe your approach to multi-device testing.
Q4. Cross-Browser
How do you ensure consistent behavior across Chrome, Firefox, Safari, and Edge?
Q5. Design Governance
Confirm that you will follow a binding Brand & Design Manual without deviation.
YES / NO
Q6. Templates
Do you rely on templates or builders? If yes, explain how you avoid template artifacts.
Q7. Confidentiality
Confirm full confidentiality and no portfolio use.
YES / NO
Q8. Execution-Only Mindset
Explain how you work on execution-only projects where creativity and reinterpretation are explicitly excluded.
...
Show more