KnowCICDWP

KnowCICDWP turns any GitHub repository into a polished, public-facing project page on your WordPress site. It fetches the repository README and release assets through the GitHub API, renders them with a tabbed, theme-aware interface, and keeps everything fast with transient caching.

It also includes a CI/CD workflow generator that produces a complete GitHub Actions `release.yml` for Tauri, Electron, Laravel and WordPress Plugin projects — including a step that pings your site to refresh the cache the moment a new release is published.

Key features

• Display a repo README (Markdown rendered to HTML, no external dependencies) and release downloads via the `[knowcicd project="slug"]` shortcode.
• Tabbed README / Releases interface with smooth transitions, changelog accordions, copy-to-clipboard asset URLs, and an AJAX refresh button.
• Global CSS Theme manager — four built-in themes (Default, Dark, Minimal, Card) plus unlimited reusable user-defined themes, selectable on any project, with an optional per-project Custom CSS override.
• CI/CD workflow generator with an optional "vibe coding" instruction block for AI assistants, plus auto-generated in-app updater manifests (Tauri `latest.json`, Electron `latest.yml`).
• Self-update notifier — a slim, dismissible admin banner alerts you when a newer plugin version is published on GitHub.
• Secure REST webhook (`/wp-json/knowcicd/v1/refresh`) so pipelines can clear the cache on release, authenticated with a per-project token.
• Encrypted GitHub token storage, transient caching with configurable TTL, and graceful fallback to cached data on API errors.

Do I need a GitHub token?

No, public repositories work without one. A token is recommended for private repos or to raise the GitHub API rate limit. Tokens are stored encrypted.

How do I auto-refresh after a release?

Use the CI/CD Workflow generator on the project edit screen. Add the `KNOWCICD_WEBHOOK_URL` and `KNOWCICD_WEBHOOK_TOKEN` repository secrets shown there, and the generated workflow will ping your site automatically on every tagged release.

How do end users get updates?

This site acts as the distribution hub. On each release your pipeline notifies the site, which stores the release data and serves it through per-project endpoints: `/latest.json` (Tauri), `/latest.yml` (Electron), `/update-check` (WordPress plugins) and `/download/{filename}` (proxied asset download). Point your apps at the URLs shown in the project's "Distribution Endpoints" panel — end users never need GitHub access.

Can developers restyle the output?

Yes. Everything is scoped to `.knowcicd-project` and driven by CSS custom properties. Add reusable themes under Settings → CSS Themes, or apply minor per-project tweaks in the Custom CSS override box on the project screen. Download the boilerplate stylesheet from the Settings page for a full reference.

Actions:

• `knowcicd_project_saved` ( int $project_id )
• `knowcicd_webhook_refreshed` ( int $project_id, string $tag )
• `knowcicd_release_stored` ( int $project_id, array $record )
• `knowcicd_asset_download` ( int $project_id, string $filename, string $target_url )

Filters:

• `knowcicd_github_request_args` ( array $args, string $endpoint, int $project_id )
• `knowcicd_readme_html` ( string $html, int $project_id )
• `knowcicd_releases` ( array $releases, int $project_id )
• `knowcicd_markdown_html` ( string $html, string $markdown )
• `knowcicd_workflow_yaml` ( string $yaml, array $selected_types, array $context )
• `knowcicd_theme_choices` ( array $choices )
• `knowcicd_tauri_manifest` ( array $manifest, int $project_id, array $release )
• `knowcicd_electron_yaml` ( string $yaml, int $project_id, array $release )
• `knowcicd_wp_update_check` ( array $payload, int $project_id, array $release )