Skip to content

Latest commit

Β 

History

History
208 lines (170 loc) Β· 6.55 KB

File metadata and controls

208 lines (170 loc) Β· 6.55 KB

Contributing to WooNuxt

First off β€” thank you! Whether you're fixing a bug, improving docs, adding features, or just giving feedback, you’re helping shape WooNuxt’s future.

This guide explains how to contribute, follow our conventions, and get your pull request merged smoothly.


πŸ† Contributors

Listed in order of contribution β€” based on GitHub stats. Thank you all:

scottyzen
scottyzen
alexookah
alexookah
zackha
zackha
Zielgestalt
Zielgestalt
brunofullstack
brunofullstack
tzhf
tzhf
AlMuz
AlMuz
McRafee
McRafee
atinux
atinux
gabrielrbarbosa
gabrielrbarbosa
danielroe
danielroe
TomCore
TomCore
vpashkov
vpashkov
vernaillen
vernaillen
arshidkv12
arshidkv12

πŸ‘‰ See full contributor graph β†’


πŸ“¦ Looking to Use WooNuxt?

If you're trying to install and use WooNuxt in a project, this file is not for you. Please see the README.md for:

  • Installation instructions
  • Environment setup
  • Usage examples
  • Plugin/module details

This guide is for contributors working on the WooNuxt codebase or documentation.


πŸ› οΈ Make Your Changes, Test, Commit, and Push

  1. Fork the repository on GitHub and clone your fork locally:

    git clone https://github.com/YOUR_USERNAME/woonuxt.git
    cd woonuxt
  2. Create a new branch using a meaningful name:

    git checkout -b feat/your-feature-name
  3. Make your changes in the appropriate part of the codebase:

    • woonuxt_base/ β€” Nuxt 3 frontend
  4. Test your changes locally:

    cd woonuxt_base
    yarn install
    yarn dev

    Then:

    • Open your browser and verify that pages load correctly
    • Interact with cart, product views, and checkout
    • Confirm that WPGraphQL queries resolve properly
    • If modifying the plugin, verify it within the WordPress admin
  5. Stage and commit your changes using Conventional Commits:

    git add .
    git commit -m "feat: add custom slot to ProductCard component"

    Common types:

    • feat: β€” a new feature
    • fix: β€” a bug fix
    • docs: β€” documentation-only changes
    • chore: β€” tooling/config updates
    • style: β€” non-functional style changes (spacing, formatting, etc.)
  6. Push your branch to GitHub:

    git push origin feat/your-feature-name
  7. Open a Pull Request targeting the master branch. Include:

    • A brief title and description
    • Screenshots or before/after examples (if relevant)
    • Any linked issues or related context

πŸ› Reporting Bugs

To report a bug, open a GitHub Issue and include:

  • βœ… What you did
  • βœ… What you expected to happen
  • βœ… What actually happened
  • βœ… WooNuxt, Node, PHP, WordPress, and Nuxt versions
  • βœ… Screenshots, logs, or network errors if helpful

🧭 Questions or Help?

If you're not sure where to start:


Thank you again β€” WooNuxt gets better because of contributors like you. πŸ’š