Positions Contributor Guide

About the Positions Newsletter

Positions is the official pTreks publication dedicated to group exploration, off-grid navigation, and outdoor field safety. Our newsletter shares advanced technical strategies, tactical tutorials, and immersive logs from the rugged frontier. We maintain an authoritative, safety-focused standard to ensure readers receive field-tested guidance.

Our Commitment to Accuracy: Since Positions articles contain spatial navigation guidance and technical field annotations, every submission undergoes thorough factual and safety auditing by our senior navigational engineering staff.

Our newsletter features:

• Engineering Logs - Inside looks at pTreks geospatial telemetry, offline map caches, and peer-to-peer synchronization protocols
• Tactical Guides - Step-by-step navigation tutorials, emergency beacon strategies, and rugged group coordination mechanics
• Expedition Chronicles - In-depth journey logs across demanding, remote backcountry terrain
• Safety Spotlight - Critical field safety methodologies and dynamic hazard-avoidance protocols

Contributor Tiers

We organize our contributors into distinct tiers depending on the technical and tactical depth of the materials:

Tier 1: Engineering & Core Team

• Who: pTreks software engineers, spatial analysts, and product architects
• Content: Architectural breakdowns, alpha software reviews, API integrations
• Badge: "Core Engineering Update"
• Access: Internal direct submission

Tier 2: Expert Field Navigators

• Who: Wilderness search and rescue coordinators, certified overland guides, survival specialists
• Content: Tactical navigation tutorials, radio frequency coordination, survival logs
• Requirements: Verified professional certifications or field credentials
• Badge: "Tactical Field Guide"
• Process: Selective vetting and safety verification

Tier 3: Community Expedition Logs

• Who: Advanced hikers and explorers who execute inspiring expeditions
• Content: Multi-day trek logs, telemetry exports, or real-world coordinating experiences
• Badge: "Expedition Journal"
• Process: Invitation-only or review of submitted GPX/KML datasets

Note: Adventure articles do not necessarily have to deal with pTreks. Just tell us about your adventures and get others out and doing the same!

Important: All contributors must hold a registered, active pTreks account. Sign up for free if you're not yet a member.

How to Submit a Positions Article

Positions utilizes standard local Markdown authoring. You will prepare static Markdown assets and deliver them to our editorial engineers via email for validation and deployment.

Step 1: Prepare Your Content

Draft your technical content in Markdown:

• Format: Markdown folder (Hugo Leaf Bundle containing index.md + raw screenshots) is highly preferred to retain spatial image alignment.
• Title: Engaging, authoritative, technical (aim for 50-60 characters)
• Subtitle: Strategic summary (max 240 characters)
• Content: 800-2500 words with granular, hierarchy-accurate subtitles
• Technical Snippets: Enclose coordinate ranges, telemetry syntax, or equations in standard markdown code backticks
• Categories: Suggest 1-2 (e.g., "Engineering", "Expeditions", "Field Safety")

Step 2: Compose Your Visual Spatial Matrix

Visual clarity is critical for spatial articles. Provide optimized screenshots and map logs:

• Cover/Hero Banner: High-resolution landscape scenery or map overview (1200x630px)
• Mobile/UI Screenshots: Provide high-resolution system captures at portrait ratios for side-by-side rendering in the responsive viewport matrix
• File Compression: Under 400KB per screenshot preferred to optimize low-bandwidth field loading
• Data Sanitization: Ensure you mask or blur any sensitive personal locations or private identifiers in your captures

Step 3: Send or Propose Submission

Submit your article bundle for peer review:

• Email To: positions-submissions@ptreks.com
• Subject: "Positions Submission: [Article Title]"
• Attachments: A compressed ZIP containing your leaf bundle folder (Markdown file + local asset images)

Step 4: Technical Auditing & Revision

Our technical editors will review:

• Factual Check: Verification of geospatial coordinates or system mechanics
• Viewport Test: Testing image layout grids against tablet and mobile responsive widths
• Feedback Cycles: Any coordinate discrepancies or safety concerns will trigger a direct email review cycle

Step 5: Static Deployment

Once approved:

• The technical editor will compile your approved bundle into the production static system
• A compiled update will deploy across our global CDN edge
• The post will index dynamically onto the compiled Positions Table of Contents

Content Guidelines & Standards

Editorial Standards

Positions articles require high informational density and alignment with our field tenets:

• Field Safety First - Zero tolerance for reckless navigation strategies
• Technical Precision - Accurate descriptions of off-grid technologies, frequencies, and signals
• Rugged Accessibility - Tailored to load rapidly over limited satellite or cellular connections
• Leave No Trace - Absolute adherence to environmental preservation in route logs

Writing Tone

• Voice: Precise, analytical, inspiring, authoritative
• POV: Second-person ("you") for procedural guides, first-person plural ("we") for engineering reviews
• Style: Clear, structured technical writing devoid of heavy marketing jargon

Required Validation Elements

• Accurate, verified GPS datum/references (if applicable)
• Proper licensing disclosures for software or mapping utilities
• Optimized, sanitized image payloads

Strictly Prohibited

• ❌ Location coordinates targeting environmentally sensitive or restricted areas
• ❌ Unverified safety guidance or illegal transmissions
• ❌ Promotional endorsements masking as tactical guidance

Responsive Image Matrix Guidelines

Since field logs include multiple UI and map captures, we utilize a responsive grid configuration inside Hugo markdown files:

• Group Captures: Group multiple screenshots inside a fluid Flex-wrap container to ensure they scale automatically from 3-columns on Desktop to 1-column on small phone displays
• Maximum Width: Inline containers should maintain a max-width of 800px and utilize margin: 0 auto for visual balance
• Alt Descriptions: Must contain descriptive functional definitions for readers relying on low-bandwidth screen readers

About Technical Editors

Our editorial engineering team ensures informational safety:

Editorial Environment

Editors use standard offline toolchains and Hugo utilities to:

• Review and approve incoming email submissions and folder attachments
• Preview draft renderings using hugo server
• Audit and optimize image compression
• Manage publication dates via the static site Front Matter
• Deploy updates globally via the automated static build environment