Contribute to AEO.dev

The field of Answer Engine Optimization is evolving faster than any single team can track. This knowledge base is designed to be a living, community-managed resource where everyone can contribute their insights, research, and practical techniques.

Start Contributing Now

Why Contribute?

Method 1: Visual Content Editor (Decap CMS)

The easiest way to contribute — no coding required. Our built-in content management system provides a visual editor for creating and editing content.

How It Works

1. Open the Editor — Click the "Open Content Editor" button above or go to aeo.dev/admin
2. Sign in with GitHub — You'll be prompted to authenticate with your GitHub account
3. Create or Edit Content — Use the visual editor to write your content with rich text formatting
4. Submit for Review — When you save, your changes automatically create a Pull Request

What You Can Do in the CMS

Editorial Workflow

All contributions go through our editorial workflow:

Draft → In Review → Ready → Published

1. Draft — Your initial submission
2. In Review — Maintainers review your contribution
3. Ready — Approved and queued for publishing
4. Published — Live on the site

Method 2: Edit on GitHub

Every page on AEO.dev can be edited directly on GitHub. This is great for quick fixes, typo corrections, or small updates.

How to Edit a Page

1. Find the Source File

   • Pages are located in src/app/[path]/page.mdx
   • For example, this page is at src/app/contribute/page.mdx

2. Open on GitHub

   • Go to github.com/answer-engine/aeo
   • Navigate to the file you want to edit
   • Click the pencil icon to edit

3. Make Your Changes

   • Edit the Markdown/MDX content
   • Use the Preview tab to check your changes

4. Submit a Pull Request

   • Scroll down and add a commit message
   • Select "Create a new branch"
   • Click "Propose changes"

File Structure

src/app/
├── page.mdx                    # Homepage
├── what-is-aeo/
│   └── page.mdx               # /what-is-aeo
├── ai-search/
│   ├── overview/
│   │   └── page.mdx           # /ai-search/overview
│   ├── chatgpt/
│   │   └── page.mdx           # /ai-search/chatgpt
│   └── ...
├── strategies/
│   ├── overview/
│   │   └── page.mdx           # /strategies/overview
│   └── ...
├── resources/
│   ├── glossary/
│   │   └── page.mdx           # /resources/glossary
│   └── ...
└── contribute/
    └── page.mdx               # This page

MDX Format

Pages use MDX (Markdown + JSX). Here's a quick reference:

export const metadata = {
  title: 'Your Page Title',
  description: 'A brief description for SEO.',
}

# Main Heading

Introduction paragraph with **bold** and *italic* text. {{ className: 'lead' }}

## Section Heading

Regular paragraph content.

### Subsection

- Bullet point one
- Bullet point two

<Note>
  Special callout for important information.
</Note>

<Row>
  <Col>
    ### Column One
    Content for first column.
  </Col>
  <Col>
    ### Column Two
    Content for second column.
  </Col>
</Row>

Method 3: Fork and Pull Request

For larger contributions like new sections, major rewrites, or multiple related changes, fork the repository and work locally.

Setup

# 1. Fork the repo on GitHub first, then clone your fork
git clone https://github.com/YOUR_USERNAME/aeo.git
cd aeo

# 2. Install dependencies
npm install

# 3. Start the development server
npm run dev

# 4. Open http://localhost:3000 in your browser

Creating Content

# 1. Create a feature branch
git checkout -b feature/my-contribution

# 2. Create your content file
mkdir -p src/app/your-section
touch src/app/your-section/page.mdx

# 3. Write your content (see MDX format above)

# 4. Test locally at http://localhost:3000/your-section

Submitting

# 1. Commit your changes
git add .
git commit -m "Add: description of your contribution"

# 2. Push to your fork
git push origin feature/my-contribution

# 3. Open a Pull Request on GitHub
# Go to github.com/answer-engine/aeo and click "New Pull Request"

Contribution Guidelines

Content Standards

What We're Looking For

• Case Studies — Real examples of AEO strategies with measurable results
• Platform Updates — Changes to how AI search engines work (ChatGPT, Perplexity, Google AI, etc.)
• New Techniques — Strategies that have worked for you
• Tool Reviews — Honest assessments of AEO tools and services
• Corrections — Found an error? Please fix it!
• Translations — Help make AEO knowledge accessible globally

Content Types

Community Channels

Recognition

All contributors are recognized in our Contributors list on GitHub.

Major contributors who make significant, ongoing contributions may be invited to become maintainers with direct commit access to the repository.

Questions?