# What’s on my GitHub (and on this site)

- Link: https://matthummel.com/whats-on-my-github-and-on-this-site/
- Published: 2026-09-18T22:50:44+00:00
- Author: Matthew Hummel

If you want to see how I work, start with the code—not just screenshots. My public
trail of WordPress GitHub projects lives at [@matthummel-pa](https://github.com/matthummel-pa),
and I keep a curated view of studio work on this site at [matthummel.com/about/#code](https://matthummel.com/about/#code).

What you’ll find there are studio concepts and demos: themes, plugins, and experiments
I use to explore ideas, stress-test patterns, and keep skills sharp. They are not
a client case-study grid. They’re invitations to look at structure, naming, and 
how I think about WordPress.

## WordPress GitHub projects worth a look

A few names you’ll see across GitHub and the Code page:

 * **TOCguide** — my first plugin in the [WordPress.org plugin directory](https://wordpress.org/plugins/tocguide/):
   a table of contents block with an optional Reading Guide ([source on GitHub](https://github.com/matthummel-pa/tocguide))
 * **Acreline (wp-acreline)** — theme exploration focused on clean layout and editable
   content patterns
 * **WalkRidge** — studio theme work aimed at presentation and maintainable structure
 * **matthummel-theme** — theme work tied to how this site itself evolves

Each repo is a window into preferences: readable PHP and templates, sensible content
models, and front ends that don’t fight the editor. Some pieces are further along
than others. That’s intentional. Studio work is allowed to be unfinished if the 
learning and the architecture are clear.

## How to use this trail

Browse the [Code page](https://matthummel.com/about/#code) for context and screenshots
where they help. Then open the repos. Fork anything useful. Open an issue or send
a note if something’s unclear—I welcome questions.

If you’re an agency or collaborator evaluating fit, this is the fastest way to see
whether our standards line up. I’ve been building in public where I can, especially
since 2025, because transparent work starts better conversations than polished claims
alone.

## The write-ups behind the code

Code shows what I built. These posts explain why and how:

 * [How I published my first WordPress.org plugin with Cursor, Git, and AI](https://matthummel.com/first-wordpress-org-plugin-tocguide-ai/):
   the full release path for TOCguide, from repo rules to plugin review.
 * [The WordPress table of contents block is planned for core](https://matthummel.com/wordpress-table-of-contents-block/):
   what that means for TOCguide.
 * [WordPress Abilities API: a simple first integration](https://matthummel.com/wordpress-abilities-api-integration-a-practical-first-integration/):
   working code for the new 6.9 API.
 * [My AI workflow for WordPress development on a Mac](https://matthummel.com/ai-workflow-for-wordpress-development/):
   the tools I use every day, and where I still review by hand.

## FAQ

### Are these client sites?

No. They’re studio concepts and demos. Client work stays confidential unless a client
asks to share it.

### Can I use code from these repos?

Check each repository’s license and README. When in doubt, ask—I’m happy to clarify
intent.

### Want to talk about applying similar patterns?

Curious about a specific repo, or need similar patterns on a client site? [Contact me](https://matthummel.com/contact/),
and I’ll get back to you within one business day (ET).

---

You can also follow me on [GitHub](https://github.com/matthummel-pa) or [DEV.to](https://dev.to/matthummeldev),
or subscribe with the [RSS feed](https://matthummel.com/feed/).