area17/twill

Twill is an open source CMS toolkit for Laravel that helps developers rapidly create a custom admin console that is intuitive, powerful and flexible. Chat...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 38 minutes ago
Added to GitGenius on September 17th, 2026
Created on June 29th, 2018
Open Issues & Pull Requests: 136 (+0)
GitHub issues: Enabled
Number of forks: 589
Total Stargazers: 3,975 (+0)
Total Subscribers: 84 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.9 days
Mean response time: 73.8 days
90th percentile: 200.4 days
Tracked items: 55

Most active contributors

Sign in to see contributor activity.

How this project is maintained

87% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 84% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 38
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 556 days
Stale 30+ days: 38
Stale 90+ days: 37

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • type: bug (3)
  • type: enhancement (3)
  • impact: high (2)
  • impact: low (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Twill is a Laravel package that helps developers rapidly create a custom CMS admin console.

Twill addresses the need to build feature-rich content management interfaces without reinventing standard functionality. It provides pre-built features and custom Vue.js UI components that handle common CMS operations, allowing developers to focus on application-specific logic. The toolkit embraces Laravel conventions fully and offers flexibility through no lock-in design: developers can create new data models, integrate existing ones, use it within a Laravel application or as a headless CMS, and disable features they don't need.

Twill suits teams building custom content management systems who want to avoid rebuilding standard admin interfaces from scratch. It works well for projects where developers need control over data models and front-end architecture without being constrained by a monolithic CMS. The tool is particularly valuable when a team wants to leverage Laravel's ecosystem while maintaining the ability to extend and customize the admin experience.

The project receives issue reports primarily from outside users rather than the core team, indicating a substantial base of adopters using it in production. Responses to issues and pull requests typically arrive within one to two weeks. Work in the issue tracker centers on enhancements and bug fixes, with most tracked items marked as low impact.