How to contribute

Overview

Portfolio Slicer has benefited greatly from community help over the years, especially around external data scripts, troubleshooting, and documentation.

Contributions are welcome when they help other users reproduce, understand, or improve a real workflow.

Useful Types of Contributions

Examples of useful contributions include:

bug reports with reproducible steps
improvements to documentation
script fixes or enhancements
support notes about source-provider changes
examples showing how a real workflow was made to work

What Makes a Contribution Helpful

When you contribute, try to include:

the Portfolio Slicer version involved
the script version involved, if relevant
the environment or Excel version
the exact error message or unexpected behavior
sample input or output where possible
a description of what you expected instead

The more concrete and reproducible the report is, the easier it is for others to test it.

Script Contribution Advice

If you contribute a script change:

explain which provider or workflow it affects
describe any new configuration parameters
avoid breaking existing file formats unless absolutely necessary
mention whether the change affects quotes, dividends, exchange rates, or final PSData files

Community Context

Historically, a number of Portfolio Slicer script improvements came from community members who needed support for real data sources and then shared their work with others.