Share what helps the next build.

Report a reproducible issue, improve an explanation or share a reusable section. Start with the contribution guide and make your next contribution useful to someone building with BlockBite.

# In your coding agent

blockbite dev
blockbite validate
blockbite build

Ready for WordPress.

Choose a concrete way to contribute.

Pick the route that matches the work you can share.

  • Explore the repositories

    Find public projects and check their contribution guidance.

    View GitHub
  • Improve the docs

    Propose a focused correction with a link to the page and an explanation of the change.

    Explore documentation
  • Share reusable work

    Read how islands are packaged and how community requests are handled.

    Explore Island Collections

Give your contribution useful context.

A focused example helps the next person understand the problem and act on it.

  1. Check the guide

    Read the documentation for the feature and the relevant contribution instructions.

  2. Show the behavior

    Describe the observed result or the improvement you want to propose.

  3. Include an example

    Share a small reproducible case and the versions involved, with private information removed.

  4. Use the right route

    Submit through the documented repository or community request path.

Keep the useful references close.

Find the context for the part of BlockBite you are working with.

Documentation

Find setup instructions, concepts and workflows.

Browse Docs

Public repositories

Browse public projects and their available contribution routes.

View GitHub

Questions about contributing

Where should I report a problem?

Start with the contribution guidance in the relevant public repository on GitHub. Follow the reporting route it provides and remove credentials or private material from any shared example.

Are shared islands automatically published?

Community submissions have review and visibility rules. Submitting an island does not automatically publish it.

Where should I start with a documentation correction?

Read the contribution guide, identify the page and explain the specific correction you propose.

Start with one useful contribution.

Bring a focused question, a reproducible issue or an improvement you can explain.