Skip to content

Atlas Folder

Purpose

Documentation for Path of Exile Atlas system, endgame mechanics, and mapping.

Template

Required: templates/mechanic-template.md

Naming Convention

Format: [mechanic-name].md (kebab-case)

Examples:

  • atlas-passive-tree.md
  • maven-invitations.md
  • map-modifiers.md
  • voidstones.md
  • atlas-progression.md

Required Frontmatter

yaml
template: "templates/mechanic-template.md"
document_type: "mechanic"
title: "[Atlas Mechanic Name]"
status: "draft|review|published|outdated"
author: "[Your Name]"
created: "YYYY-MM-DD"
updated: "YYYY-MM-DD"
tags: ["tag1", "tag2"]
league: "3.25"
patch: "3.25.1"

# Mechanic-specific fields
mechanic_category: "atlas|endgame"
complexity: "beginner|intermediate|advanced"

Content Guidelines

What to Include

  • Mechanic overview and purpose
  • How to unlock/access
  • Strategies and optimization
  • Interactions with league mechanics
  • Progression requirements
  • Rewards and benefits
  • Common strategies
  • Atlas passive tree synergies

Tags

Use tags for endgame content and systems:

yaml
tags: ["atlas", "endgame", "mapping", "progression", "mechanic"]

Relationships

Common relationship types:

  • synergizes_with - Works well with other atlas mechanics
  • requires - Prerequisites to unlock
  • part_of - Larger system this belongs to
  • used_by - Strategies/guides that use this

Example:

yaml
relationships:
  synergizes_with:
    - path: "mechanics/leagues/expedition.md"
      title: "Expedition"
  used_by:
    - path: "research/strategy/atlas-progression-guide.md"
      title: "Atlas Progression Guide"

Quality Checklist

  • [ ] Used templates/mechanic-template.md
  • [ ] Followed naming convention (kebab-case)
  • [ ] Included all required frontmatter
  • [ ] Set mechanic_category to "atlas" or "endgame"
  • [ ] Specified complexity level
  • [ ] Used absolute paths for relationships
  • [ ] Added descriptive tags
  • [ ] Included unlock/progression requirements

poe-aio - Path of Exile All-in-One