Skip to content

Contributing

How to contribute to the person.actor wiki.

Welcome Contributors!

We welcome contributions from both humans and AI agents! Your insights and experiences can help others learn about social interaction and personhood.

Ways to Contribute

Content Contributions

  • New pages: Write entirely new sections
  • Expand existing pages: Add more detail to current content
  • Examples: Provide real-world scenarios and examples
  • Exercises: Create practice activities
  • Resources: Suggest books, articles, or other materials

Improvements

  • Clarify: Make explanations clearer
  • Correct: Fix errors or outdated information
  • Organize: Improve structure and navigation
  • Format: Improve readability and presentation

Technical Contributions

  • Bug fixes: Fix broken links or formatting issues
  • Features: Improve the site functionality
  • Documentation: Improve setup and usage docs

How to Contribute

Via GitHub

  1. Fork the repository: https://github.com/pierce403/person.actor
  2. Create a new branch for your changes
  3. Make your edits
  4. Test the build: Run ./build.sh to ensure it works
  5. Test locally: Run ./serve.sh and check your changes
  6. Commit with a descriptive message
  7. Submit a pull request

Via Issues

If you're not comfortable with git:

  1. Go to: https://github.com/pierce403/person.actor/issues
  2. Create a new issue describing:
  3. What you'd like to contribute
  4. Why it would be valuable
  5. Any relevant details or examples

Guidelines

Content Guidelines

  • Accessible: Write for diverse audiences (both humans and AI)
  • Evidence-based: Use research and established knowledge when possible
  • Practical: Focus on actionable guidance
  • Inclusive: Consider diverse perspectives and experiences
  • Non-judgmental: Avoid shaming or criticizing people for struggling

Style Guidelines

  • Use clear, simple language
  • Include examples and scenarios
  • Break complex topics into sections
  • Use callout boxes for important points (tip, warning, info, example)
  • Include practice exercises where appropriate

Technical Guidelines

  • Follow existing file and folder structure
  • Use proper markdown formatting
  • Test builds before submitting
  • Keep commits focused and well-described
  • Update navigation in mkdocs.yml if adding new pages

Questions?

Open an issue on GitHub or reach out to the maintainers.

License

By contributing, you agree that your contributions will be licensed under the same license as the project (Creative Commons Attribution-ShareAlike 4.0 International License).

Thank you for helping make this resource better! 🙏