Thank you for your interest in contributing! This document explains how to get set up and submit changes.
-
Prerequisites: Node.js 18+, npm 9+, and a local WordPress installation (6.4+).
-
Clone and install:
git clone https://github.com/dknauss/Borges.git cd borges-bibliography-builder npm install -
Link to WordPress: symlink or copy the plugin folder into your
wp-content/plugins/directory. -
Start development mode:
npm run start
-
Activate the plugin in the WordPress admin under Plugins.
- JavaScript follows the @wordpress/scripts ESLint configuration.
- SCSS follows the WordPress Stylelint configuration.
- Run linting before committing:
npm run lint:js npm run lint:css
npm run test # Unit tests (Jest)Tests live alongside the source in src/ or in a __tests__/ directory. When adding a feature or fixing a bug, include tests that cover the change.
- Create a branch from
mainwith a descriptive name (e.g.,fix/doi-detection-edge-case). - Make your changes with clear, focused commits.
- Run linting and tests before pushing.
- Open a pull request against
main. In the PR description:- Describe what changed and why.
- Reference any related issues (
Closes #123). - Include testing steps if the change affects editor behavior.
- A maintainer will review your PR. Please respond to feedback and keep the PR up to date with
main.
Use the bug report issue template. Include steps to reproduce, expected behavior, and your WordPress/browser versions.
Do not report security vulnerabilities in public issues. See SECURITY.md for responsible disclosure instructions.