PKYDrip Page System v1.0

This document defines the standard page structure for the PKYDrip Hugo website.

Goal:

  • Maintain consistency across all pages
  • Support long-term SEO growth
  • Ensure scalable content production
  • Align engineering-style communication

1. PAGE TYPES OVERVIEW

The website consists of 6 main page types:

  1. Solution Pages
  2. Product Pages
  3. Applications Pages
  4. Docs Pages
  5. Tools Pages
  6. Partner / Landing Pages

Each type has a fixed structure and purpose.

2. SOLUTION PAGE TEMPLATE

Purpose

Explain how to solve a specific irrigation problem or project requirement.

Structure

  1. Title
  2. Summary (2–4 lines)
  3. Problem / Demand
  4. Who This Solution Is For
  5. Typical System Architecture
  6. Core Control Logic
  7. Main Components
  8. Optional Extensions
  9. Suitable Project Types
  10. FAQ (3–5 questions)
  11. CTA

Rules

  • Start from problem, not product
  • Emphasize system logic
  • Link to related applications and products

3. PRODUCT PAGE TEMPLATE

Purpose

Explain a product’s role, capabilities, and system integration.

Structure

  1. Product Title
  2. Short Summary
  3. Key Features
  4. Main Functions
  5. Typical Applications
  6. Technical Highlights
  7. System Integration
  8. Installation / Usage Notes
  9. FAQ
  10. CTA

Rules

  • Avoid sales-heavy language
  • Focus on engineering role
  • Always explain how it fits into a system

4. APPLICATIONS PAGE TEMPLATE

Purpose

Explain how irrigation systems are applied in real-world scenarios.

Structure

  1. Title
  2. Scenario Overview
  3. Typical System Structure
  4. What This Application Includes
  5. Why This Architecture Works
  6. Recommended Equipment Combination
  7. Typical Project Types
  8. FAQ
  9. CTA

Rules

  • Focus on application logic
  • Avoid pushing specific products too early
  • Use diagrams when possible

5. DOCS PAGE TEMPLATE

Purpose

Provide technical explanations, guides, and engineering knowledge.

Structure

  1. Title
  2. What This Document Explains
  3. Core Concept
  4. Detailed Explanation
  5. Practical Guidance
  6. Common Mistakes
  7. Related Pages
  8. CTA

Rules

  • Educational tone
  • Minimal marketing language
  • SEO-focused

6. TOOLS PAGE TEMPLATE

Purpose

Help users structure project requirements and get guidance.

Structure

  1. Tool Title
  2. Tool Purpose
  3. Required Inputs
  4. How It Works
  5. Output Description
  6. Why It’s Useful
  7. CTA

Rules

  • Focus on usability
  • Clear explanation of output value

7. PARTNER / LANDING PAGE TEMPLATE

Purpose

Attract partners, distributors, and project collaborators.

Structure

  1. Title (Region / Program)
  2. Who This Is For
  3. Why Work With PKYDrip
  4. Support We Provide
  5. Use Cases
  6. Cooperation Model
  7. CTA

Rules

  • Direct and clear
  • Still maintain technical credibility

8. GLOBAL RULES (VERY IMPORTANT)

Titles

  • Must be clear and descriptive
  • Avoid marketing exaggeration

Summary

  • Every page must include a short summary (2–4 lines)

Images

  • Use /images/ path
  • Prefer SVG diagrams
  • Include alt text

CTA (Standard)

Use one of:

  • Talk to PKYDrip about your project
  • Request a system recommendation
  • Send your project details

FAQ

  • 3–5 questions per page
  • Focus on real user concerns

Internal Linking

Every page should link to:

  • Related solutions
  • Related products
  • Related docs

9. WRITING STYLE

  • Engineering-focused
  • Practical
  • Clear logic
  • No exaggerated marketing language
  • Explain WHY, not just WHAT

10. FUTURE EXTENSION

  • Multi-language pages must follow same structure
  • English version is the source
  • Other languages replicate structure first