Repository Overview

The switch-to-eu/content repository contains all the written content for our platform, organized as Markdown files. This includes migration guides, service descriptions, and other documentation.

What You Can Contribute

• Migration guides for switching from non-EU to EU services
• Documentation about EU service alternatives
• Updates or corrections to existing content
• Translations of existing content into other European languages

Contribution Process

1. Fork the Content Repository

• Go to https://github.com/switch-to-eu/content
• Click the "Fork" button in the top right corner
• This creates your personal copy of the content repository

2. Clone Your Fork (Optional)

If you prefer to work locally:

git clone https://github.com/switch-to-eu/content.git cd content

3. Create or Edit Content

Option A: Edit Directly on GitHub

• Navigate to the file you want to edit in your fork
• Click the pencil icon to edit
• Make your changes in the editor

Option B: Edit Locally

• Create a branch: git checkout -b your-branch-name
• Create or edit files using your preferred text editor
• Commit and push your changes

4. Follow Content Structure

Our content is organized as follows:

• /guides/ - Migration guides organized by service category
• /alternatives/ - Information about EU service alternatives
• /templates/ - Templates for creating new content

5. Submit a Pull Request

• Navigate to your fork on GitHub
• Click "Contribute" then "Open pull request"
• Provide a clear title and description of your changes
• Submit the pull request

Content Guidelines

Formatting

• All content should be written in Markdown
• Use headers (# ## ###) to organize content
• Include a title and brief introduction at the top of each guide
• Use screenshots where helpful (place in /images/ directory)

Writing Style

• Use clear, straightforward language
• Aim for step-by-step instructions where applicable
• Be factual and neutral when comparing services
• Focus on practical migration information
• Use inclusive language

Migration Guides Structure

Each migration guide should include:

• An overview of the migration process
• Prerequisites (accounts, tools needed)
• Step-by-step migration instructions
• Verification steps to ensure successful migration
• Troubleshooting common issues (if applicable)

Review Process

After submitting your pull request:

• A maintainer will review your contribution
• You may receive feedback requesting changes
• Once approved, your content will be merged and published to the website

Questions and Support

• Comment on related issues for context
• Ask questions in your pull request if you need clarification