Weave Code
Sharp Laravel Package
code16/sharp
Sharp is a code-driven content management framework for Laravel. Build CMS sections with a clean PHP API and no front-end code: manage, search, filter and validate structured data, run custom commands, and handle authorizations, all data-agnostic and following Laravel conventions.
Sharp is a content management framework built for Laravel as a package, designed to bring a clean UI and excellent developer experience to the CMS section of any project. Driven entirely by code, it exposes a clean and documented PHP API that follows Laravel conventions, keeping your application free of framework adherence. Sharp is data-agnostic, making no assumptions about your persistence layer.
- Create, update and delete structured data with built-in validation and error handling
- Display, search, sort and filter records effortlessly
- Run custom commands on one, several or all instances
- Handle authorizations and validation through a simple API
- Build complete admin interfaces without writing any front-end code
Requires Laravel 11+ and PHP 8.3+.
Frequently asked questions about Sharp
- What is code16/sharp and what does it do in Laravel?
- Sharp, published as code16/sharp, is a code-driven content management framework for Laravel. It provides a packaged admin/CMS layer for CRUD, validation, search, sort, filters, and custom commands using a clean PHP API. It is data-agnostic and intended to keep CMS concerns out of your domain code.
- How do I install code16/sharp in a Laravel application?
- Install it with Composer, then follow Sharp's setup steps to publish assets and register routes, entities, policies, fields, and commands in your Laravel app. These are conventional Laravel integration points, but the exact sequence should be validated in a non-production branch. Check the official documentation for the current package version and required setup.
- Does Sharp require Laravel 11 and PHP 8.3?
- Yes. Sharp requires Laravel 11 or newer and PHP 8.3 or newer, so those versions are a hard gate. Confirm your production Laravel and PHP versions before evaluating it further.
- Can Sharp work with my existing Eloquent models and database schema?
- Sharp is data-agnostic and does not own your persistence schema, so it can sit over existing Eloquent models and tables. You map models and tables to Sharp entities while keeping domain logic in application services rather than only in Sharp configuration. This lowers forced schema-migration risk, but mapping and policy behavior still need a spike.
- How does authorization work in Sharp with Laravel policies and existing auth?
- Sharp uses Laravel conventions for auth, policies, validation, and middleware, so using your existing guard is a key integration point to prove. SSO, 2FA/passkeys, tenant scoping, and row-level authorization should be tested explicitly rather than assumed. Run a timeboxed spike with your real auth and policy setup before committing.
- Can I use Sharp for an API-only Laravel backend?
- Sharp is an admin/CMS layer with a packaged UI, so it is a weaker fit for API-only products that do not need an internal admin surface. It can still fit a Laravel backend that needs internal CRUD, content operations, search, filters, and commands. If your product is strictly API-only, evaluate whether the admin UI is actually needed.
- What are Sharp's main features for content operations and admin use cases?
- Sharp supports create, update, and delete operations with validation and error handling, plus display, search, sort, and filter views. It can run custom commands on one instance, a selection, or all instances, and it handles authorization and validation. Standard screens require no front-end code and are driven through the PHP API.
- How do I customize Sharp with custom fields, embeds, or dashboard widgets?
- Standard Sharp screens require no front-end code, but custom fields, embeds, and dashboard widgets may require Vue or Sharp-internal knowledge. Scope those customizations separately and timebox a spike around the specific UI behavior you need. Keep bespoke admin UX requirements explicit before choosing Sharp.
- What security concerns should I review before using Sharp in production?
- Review Sharp's CMS attack surface carefully: recent fixes have covered SVG/HTML sanitization, IDOR, reorder policy checks, and signed download URLs. Prove upload storage, scanning, serving, route prefixes, middleware isolation, CSP/nonce handling, and policy authorization in your environment. Treat a security review as part of the pilot, not an afterthought.
- What should I know about Sharp maintenance, support, and major upgrades?
- Sharp is actively maintained with documentation, a demo, an MIT license, and recent security fixes, but maintainer concentration and unknown commercial support add vendor risk. Validate release metadata and the v9-to-v10 major upgrade path during due diligence. Stars show interest, not production proof, so run a bounded pilot and keep an exit plan.
Weaver
How can I help you explore Laravel packages today?