Open-source community

Put something useful back into the community.

Share a model, article, case study, tool, challenge, event, correction, or code improvement. You do not need to be a developer, and you do not need permission before you start.

No code required for content Automated validation Reviewed in public
Choose a starting point

How do you want to contribute?

Simple by design

From idea to merged contribution

  1. 1
    Pick the right folder.

    Every content type under src/content/ has a README with its exact format and an example.

  2. 2
    Add or edit a Markdown file.

    For content, you can do the entire thing in GitHub's web interface. Cloning the repo is optional.

  3. 3
    Open a pull request.

    Describe what you added or changed. A draft PR is completely fine if you want feedback first.

  4. 4
    Let the checks run.

    The site builds automatically and validates required fields, links, and metadata.

  5. 5
    A maintainer reviews it.

    Useful contributions get merged; unclear ones get a question or a suggested adjustment rather than disappearing into a queue.

What belongs here

Useful contributions can be large or tiny. A practical case study is valuable, but so is fixing one outdated link.

  • Articles and case studies that teach something useful from real practice
  • Decision models, tools, and books that belong in the community resource library
  • Challenges and Q&A that give practitioners something concrete to work through or discuss
  • Events, DecisionCAMP material, and community news worth preserving or sharing
  • Vendor’s Corner announcements that are relevant to Decision Management practitioners
  • Corrections and archive improvements — dead links, outdated details, typos, or missing historical material
  • Site and code improvements to the Astro site itself

Most content lives as a plain Markdown file under src/content/. Each content folder has its own README.md with the exact fields, filename convention, and a copy-pasteable example.

A few useful rules

Keep contributions practical and easy to maintain:

  • Write summaries in your own words rather than copying large blocks from another source.
  • Verify outbound links when you can; a missing link is better than a knowingly broken one.
  • If you own a useful PDF, image, spreadsheet, or other file, prefer hosting it in the repository rather than depending on a fragile hotlink.
  • Keep vendor participation relevant and transparent. Sponsorship does not determine editorial content or community guidance.
  • For new Advisory Board members or new sponsorships, start with the community rather than adding the entry directly; the full contribution guide explains those exceptions.

The complete rules and folder-by-folder reference live in CONTRIBUTING.md.

Why contribute?

Decision Management spans business rules, decision modeling, optimization, machine learning, simulation, AI, and the operating practices that connect those methods to real decisions. Useful knowledge is spread across disciplines, companies, vendors, research groups, and decades of community history. This site works best when that knowledge is not dependent on one person or one platform to stay available.

The repository is intentionally open so additions, corrections, and changes can be proposed and reviewed in public. The goal is a living practitioner resource that becomes more useful as more people put something back into it.

Questions or not sure where to start?

You do not need permission before proposing something. Open a draft pull request, start a GitHub issue, or email DecisionManagementCommunity@gmail.com.