Skip to main content

Welcome Contributors

The LLMTAG protocol is an open-source, community-driven project. We welcome contributions from developers, content creators, AI researchers, and anyone passionate about ethical AI and content creator rights.

Get Started Contributing

CodeDocumentationCommunityTestingPromotion

Ways to Contribute

Code Contributions

WordPress Plugin Development

1

Fork the Repository

Fork the LLMTAG WordPress Plugin repository on GitHub.
2

Set Up Development Environment

Set up a local WordPress development environment with the plugin.
3

Create a Feature Branch

Create a new branch for your feature or bug fix.
4

Make Your Changes

Implement your changes following our coding standards.
5

Test Your Changes

Write tests and ensure all existing tests pass.
6

Submit a Pull Request

Submit a pull request with a clear description of your changes.

Protocol Implementation

Core Protocol

Repository: llmtag-core Focus: Protocol specification and reference implementation Languages: JavaScript, Python, PHP

SDK Development

Repository: llmtag-sdks Focus: Software development kits for various languages Languages: JavaScript, Python, PHP, Go, Rust

Documentation Contributions

Improving Existing Documentation

1

Identify Areas for Improvement

Look for unclear explanations, missing examples, or outdated information.
2

Create a Fork

Fork the documentation repository.
3

Make Your Changes

Improve clarity, add examples, or fix errors.
4

Test Your Changes

Ensure all links work and examples are accurate.
5

Submit a Pull Request

Submit your improvements with a clear description.

Creating New Documentation

Tutorials

Content: Step-by-step guides for specific use cases Format: Markdown with code examples Audience: Beginners to advanced users

API Documentation

Content: Complete API reference and examples Format: OpenAPI specification + examples Audience: Developers and integrators

Case Studies

Content: Real-world implementation examples Format: Detailed case studies with code Audience: Content creators and developers

Best Practices

Content: Guidelines and recommendations Format: Structured guides with examples Audience: All users

Community Contributions

Helping Others

Discord Support

Activity: Answer questions in Discord channels Time Commitment: As much as you can spare Impact: Help newcomers get started

GitHub Discussions

Activity: Participate in technical discussions Time Commitment: Regular participation Impact: Shape the direction of the project

Code Reviews

Activity: Review pull requests and provide feedback Time Commitment: 1-2 hours per week Impact: Maintain code quality

Testing

Activity: Test new features and report bugs Time Commitment: Flexible Impact: Ensure reliability and stability

Content Creation

1

Blog Posts

Write blog posts about LLMTAG implementation, AI ethics, or content creator rights.
2

Video Tutorials

Create video tutorials for implementing LLMTAG on different platforms.
3

Conference Talks

Speak at conferences about AI ethics and content protection.
4

Social Media

Share LLMTAG content and engage with the community on social media.

Development Guidelines

Coding Standards

WordPress Plugin

PHP Standards

Standard: WordPress Coding Standards Tools: PHPCS, PHPStan Documentation: WordPress Handbook

JavaScript Standards

Standard: ESLint with WordPress rules Tools: ESLint, Prettier Documentation: WordPress JavaScript Standards

General Development

Git Workflow

1

Fork and Clone

Fork the repository and clone it to your local machine.
2

Create Feature Branch

Create a descriptive branch name: feature/add-new-directive or fix/analytics-bug.
3

Make Changes

Make your changes with clear, atomic commits.
4

Write Tests

Add or update tests for your changes.
5

Update Documentation

Update relevant documentation if needed.
6

Submit Pull Request

Submit a pull request with a clear title and description.

Pull Request Guidelines

PR Title Format

type(scope): brief description

Examples:
feat(plugin): add new AI agent blocking feature
fix(api): resolve authentication issue
docs(spec): update directive documentation
test(analytics): add unit tests for reporting

PR Description Template

## Description
Brief description of the changes.

## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change
- [ ] Documentation update

## Testing
- [ ] Tests pass locally
- [ ] New tests added for new functionality
- [ ] Manual testing completed

## Checklist
- [ ] Code follows project style guidelines
- [ ] Self-review completed
- [ ] Documentation updated
- [ ] No breaking changes (or clearly documented)

Testing Guidelines

WordPress Plugin Testing

Unit Tests

Framework: PHPUnit Coverage: Minimum 80% Focus: Individual functions and methods

Integration Tests

Framework: WordPress Test Suite Coverage: Plugin integration with WordPress Focus: End-to-end functionality

Protocol Testing

1

Parser Testing

Test the llmtag.txt parser with various input formats.
2

Validation Testing

Test validation logic for different directive combinations.
3

Compatibility Testing

Test compatibility with different AI agents and scenarios.
4

Performance Testing

Test performance with large llmtag.txt files and high request volumes.

Documentation Standards

Writing Guidelines

Clarity

Principle: Write for your audience Practice: Use clear, concise language Avoid: Jargon and technical complexity

Examples

Principle: Show, don’t just tell Practice: Include practical examples Avoid: Abstract explanations only

Documentation Structure

1

Introduction

Provide context and explain the purpose of the document.
2

Prerequisites

List any requirements or setup needed.
3

Step-by-Step Instructions

Provide clear, numbered steps for procedures.
4

Examples

Include practical examples and code snippets.
5

Troubleshooting

Address common issues and solutions.

Community Guidelines

Code of Conduct

Our community is built on mutual respect and collaboration:

Communication Guidelines

Discord

Use for: Real-time discussions, quick questions Tone: Friendly and informal Response time: Immediate to a few hours

GitHub

Use for: Technical discussions, bug reports Tone: Professional and detailed Response time: 1-3 business days

Recognition and Rewards

Contributor Recognition

GitHub Contributors

Recognition: Listed in project README Criteria: Meaningful code contributions Benefits: Public recognition, networking

Community Champions

Recognition: Featured in newsletter Criteria: Outstanding community support Benefits: Public recognition, speaking opportunities

Contributor Benefits

Getting Started

First Contribution

1

Join the Community

Join our Discord server and introduce yourself.
2

Find a Good First Issue

Look for issues labeled “good first issue” or “help wanted”.
3

Set Up Development Environment

Follow the setup instructions in the repository README.
4

Make Your First Contribution

Start with a small change like fixing a typo or adding a test.
5

Get Feedback

Submit your first pull request and get feedback from maintainers.

Mentorship Program

Get a Mentor

Experienced contributorsOne-on-one guidanceSkill developmentCareer advice

Resources

Development Resources

Learning Resources

WordPress Development

Open Source Best Practices

Content Creator Rights

Questions?

Need Help Getting Started?

Email usJoin DiscordCheck GitHub DiscussionsFind a mentor
I