- Review the existing markup, styles, and sorter logic so new work stays consistent.
- Confirm the change aligns with the MIT license and fits the directory-table scope.
- Open an issue to propose substantial additions (new components, large refactors, or rebrands).
- Fork the repository and create a focused feature branch.
- Work in plain HTML, CSS, and vanilla JavaScript—avoid build tooling or frameworks.
- Open
index.htmllocally in current Chrome, Firefox, and Safari (or equivalents) to verify behavior. - Note the browsers tested, sample data used, and any accessibility checks performed.
- Remove stray files and confirm
git statusis clean before committing.
- Preserve semantic table structure and keyboard-accessible sorting controls.
- Keep styles scoped to the directory table to avoid collisions when embedded in Ghost.
- Document new configuration options or data requirements in
README.mdor inline comments when necessary. - Limit comments to clarifying non-obvious logic or Ghost-specific considerations.
- Use imperative commit messages (e.g.,
Add newsletter filter column). - In the PR description, summarize the change, testing evidence, and any compatibility risks.
- Attach screenshots or screen recordings if the change alters visuals or interaction.
- Respond quickly to review feedback so changes can ship without rework.
- Include expected vs. actual behavior, reproduction steps, sample rows, and browser details.
- Flag breaking regressions or accessibility concerns as high priority.
- For security-sensitive topics, follow
SECURITY.mdinstead of opening a public ticket.