Alpaca Issue Tracker vs Jamie's Front-End Editor for Content Teams

Alpaca Issue Tracker is a powerful yet simple issue tracking system that lives inside your WordPress admin. Built with the WordPress philosophy in mind, it provides a Trello-like kanban board interface for managing bugs, feature requests, and project tasks. Key Features Kanban Board Interface – Drag-and-drop issues between and within fully customizable status columns Automatic Context Capture – Browser info, page context, and technical details are saved with each bug report submitted from the front end Built for WordPress – Uses native WordPress components, post types, taxonomies and database tables Extensibility – Developers can add custom functions and integrations via conventional WordPress actions & filters Respects User Permissions – Integrates with WordPress user roles and capabilities Screenshot Capture – See exactly what the user saw, captured and processed locally within the browser Comment and Activity Thread – A unified view of each issue’s progress, supporting attachment uploads and user mentions Priority Management – Flag high-priority items and set deadlines Assignee System – Assign issues and checklist items to team members Email Notifications – Instant or daily digest email notifications for the issues you care about Translation Ready – Fully localized and ready for translation into any language (including RTL support) No Artificial Limitations – Use on as many sites, with as many users, issues, attachments and interactions as you need Perfect For Freelance developers managing client sites Small agencies tracking bugs and feature requests Development teams needing lightweight project management Clients performing QA on a new site Account managers responsible for rolling retainer contracts Enterprises and government bodies needing extra reassurance on hosting How It Works Clients don’t have the time or knowledge to provide detailed technical reports when they spot a problem. But developers can’t do their job without that detail. Alpaca Issue Tracker solves this by automatically capturing all the technical context WordPress already knows about each page request. When a user reports an issue via the Alpaca Issue Tracker front-end toolbar, the plugin silently captures: – A screenshot of what the user can see – Browser and device information – Current page URL and template – Queried object details and HTTP headers – Any JavaScript errors This gives developers everything they need to reproduce and fix issues quickly, with zero burden on the client. Issues can also be created on the admin side, meaning Alpaca Issue Tracker can also be used as a complete project management system, to plan new features or track internal tasks. Third-Party Libraries Alpaca Issue Tracker includes runtime copies or bundled output from the following GPL-compatible libraries: Bowser – MIT license – https://github.com/bowser-js/bowser DOMPurify – MPL-2.0 option from (MPL-2.0 OR Apache-2.0) – https://github.com/cure53/DOMPurify Marked – MIT license – https://marked.js.org/ PrismJS – MIT license – https://prismjs.com/ PropTypes – MIT license – https://github.com/facebook/prop-types SnapDOM – MIT license – https://github.com/zumerlab/snapdom Recommended Plugins Alpaca Issue Tracker uses user images throughout its interface, for extra humanity. We recommend Simple Local Avatars as a reliable solution for processing and hosting photos of your users without using an external service. Development Source code and build configuration are available at: https://github.com/rareview/alpaca-issue-tracker Building from Source Clone the repository Run npm install Run npm run lint Run npm run build Run npm run zip to create a distributable package The distributed plugin includes compiled JavaScript and CSS assets. The source files, dependency manifests, and build instructions are available in the repository above. Composer dependencies are used for development tooling and coding standards checks. Privacy Policy Alpaca Issue Tracker does not collect or transmit any data outside of your WordPress installation. All issue data, screenshots, and technical information are captured and stored locally in your WordPress database and/or filesystem. Credits Developed by Rareview®

Jamie’s Front-End Editor for Content Teams lets your team edit page and post content directly from the front end of your WordPress site. No need to open the block editor — click any text, link, button or image on the live page and change it in place. Built on the WordPress Interactivity API with no build step required. Give your team precise, bounded editing: let them fix the copy that should change, and lock down the parts that shouldn’t. Features: Click any paragraph or heading to edit it inline, right on the live page Add, edit or remove links on your text without leaving the page Replace images from the media library, set alt text, or remove an image, all on the front end Edit button text and links from the front end too Block markup is fully preserved on save Lock a whole page from front-end editing with a single checkbox Lock individual blocks or whole sections, using the block’s own Lock option (padlock) or a CSS class. Locks cover everything nested inside and are enforced on save, not just hidden in the UI Edits are recorded as native WordPress block notes, so there’s an audit trail A central Site changes screen (Tools menu) lists every front-end edit across the whole site — what changed, where, by whom and when — with filters by user, page, block type and date, plus search and CSV export Admin settings to choose which block types are editable Option to restrict chosen roles to front-end-only editing (no wp-admin access) Secure — only users with edit permissions see the editing UI