Contributing to Oblique Paradigm

Ways to Contribute

• 📝 Documentation - Improve guides, add examples, fix typos
• 💻 Code - Build features, fix bugs, improve performance
• 🎨 Design - Create UI/UX improvements, visual assets
• 💡 Ideas - Share feedback, propose features, report issues

Documentation Contributions

How to Edit Documentation

Fork the Repository

Visit GitHub repository (opens in a new tab) and click "Fork"

Make Your Changes

Edit the markdown files in the pages/ directory

Submit a Pull Request

Create a PR with a clear description of your changes

Review Process

Maintainers will review and provide feedback

Documentation Guidelines

• Write clearly: Use simple, concise language
• Add examples: Include real-world scenarios
• Stay organized: Follow existing structure
• Test locally: Ensure changes render correctly

Areas Needing Documentation

• Use case examples: More real-world scenarios
• Technical guides: Smart contract interactions
• Video tutorials: Visual learning content
• Translations: Multi-language support

Code Contributions

Development Setup

# Clone the repository
git clone https://github.com/oblique-paradigm/oblique-paradigm-docs.git
cd oblique-paradigm
 
# Install dependencies
npm install
 
# Run development environment
npm run dev
 
# Run tests
npm test

Contribution Process

Find an Issue

Browse GitHub Issues (opens in a new tab) or create one

Claim the Issue

Comment that you're working on it

Create a Branch

git checkout -b feature/your-feature-name

Write Code

Follow coding standards and include tests

Submit PR

Include issue number and detailed description

Code Standards

• Test Coverage: Minimum 80% for new code
• Documentation: JSDoc comments for public APIs
• Style Guide: Follow ESLint configuration
• Commits: Use conventional commit format

Priority Development Areas

Design Contributions

Design System

We're building a cohesive design language:

• Principles: Minimal, accessible, creator-focused
• Colors: Dark theme with high contrast
• Typography: Clear hierarchy, readable fonts
• Components: Reusable, responsive, accessible

How to Contribute Designs

1. Review current designs in Figma (link coming soon)
2. Create proposals for improvements
3. Share mockups in Discord #design channel
4. Iterate based on feedback from community

Design Needs

• Dashboard layouts: Creator portfolio views
• Mobile interfaces: Native app designs
• Marketing materials: Landing pages, graphics
• Brand assets: Logos, icons, illustrations

Community Input

Critical Areas Needing Feedback

Governance Framework Design

• How should projects make scope changes?

• What happens during contributor disagreements?

• Should governance be token-weighted or quadratic?

• How do projects maintain direction while staying democratic?

Economic Model Refinement

• How should tasks be priced in tokens?

• When should profits be distributed?

• What platform fees are reasonable?

• How should acquisitions be handled?

Quality Control Systems

• Who validates completed tasks?

• How are disputes resolved fairly?

• How do contributors build credibility?

• What happens with poor quality work?

Legal & Regulatory Structure

• What legal entity structure for projects?

• How to handle multi-jurisdiction taxes?

• Who owns created intellectual property?

• How to ensure regulatory compliance?

Platform Features & UX

• How should creators discover projects?
• What coordination tools are needed?
• How to manage multiple project tokens?
• What builds contributor trust?

Specific Questions for Different Users

For Project Initiators

• What would make you share equity with unknown collaborators?
• How would you evaluate completed work quality?
• What safeguards against project hijacking do you need?

For Contributors

• What information do you need before joining projects?
• How should the platform protect against non-payment?
• What would convince you profits will actually be shared?

For Everyone

• What collaborative projects excite you most?
• What unfair collaboration experiences have you had?
• How do successful open-source projects handle governance?

Community Channels

Discord Community

Join our Discord (opens in a new tab)

Active channels:

• #general - Main discussion
• #development - Technical talk
• #governance - Platform decisions
• #showcase - Share your work
• #help - Get assistance

GitHub Discussions

GitHub Discussions (opens in a new tab)

• Feature requests
• Technical RFCs
• Community proposals
• Q&A

Working Groups

Join specialized teams focusing on specific aspects:

• Governance WG: Designing decision-making frameworks

• Economics WG: Refining token models and incentives

• Technical WG: Building smart contracts and infrastructure

• Legal WG: Ensuring compliance and protection

Recognition & Rewards

Contributor Recognition

Active contributors receive:

• Reputation badges: Display on profile
• Early access: Test new features first
• Governance power: Extra voting weight
• Token rewards: OP tokens for contributions

Contribution Tracking

All contributions are tracked and recognized:

• GitHub contribution graph
• Discord role progression
• Platform reputation score
• Public contributor list

Community Guidelines

Be Respectful

• Welcome newcomers
• Value diverse perspectives
• Provide constructive feedback
• Assume good intentions

Be Specific

• Explain problems clearly
• Provide reproducible examples
• Suggest concrete solutions
• Back claims with evidence

Be Collaborative

• Build on others' ideas
• Share knowledge freely
• Help others contribute
• Celebrate successes together

Getting Started

Ready to contribute? Here's how to begin:

Join Discord

Connect with the community at discord.gg/BfAESuma (opens in a new tab)

Introduce Yourself

Share your background and interests in #introductions

Find Your Area

Browse channels and working groups that match your skills

Start Small

Begin with documentation fixes or small features

Grow Your Impact

Take on larger projects as you gain familiarity