Torque Admin is a Rails Engine that gives your application a fully-featured administrative interface with minimal configuration. It is built on top of vanilla Rails with Hotwire in mind, supports Bootstrap, Bulma, Tailwind, and Semantic UI out of the box, and streams heavy pages by default for a snappy user experience.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/crashtech/torque-admin/llms.txt
Use this file to discover all available pages before exploring further.
Installation
Add Torque Admin to your Gemfile and mount the engine in minutes.
Quickstart
Configure your first admin application and declare your first resource.
Core Concepts
Understand Applications, Resources, Routing, and the Elements DSL.
Configuration
Tune themes, authentication, streaming, and namespace isolation.
Why Torque Admin?
Most Rails admin frameworks lock you into a specific UI library and rendering approach. Torque Admin is different:- Framework-agnostic UI — choose Bootstrap, Bulma, Tailwind, or Semantic UI (Fomantic-UI); or bring your own.
- Hotwire-first streaming — index and dashboard pages stream their content via
ActionController::Live, keeping the browser responsive even over slow connections. - Declarative Elements DSL — define menus, forms, and tables once as reusable Element classes; let the engine wire them to your controllers automatically.
- Multiple admin instances — run separate admin portals (e.g.,
AdminandPartnerAdmin) inside a single Rails application, each fully isolated. - Extended routing DSL —
resources,dashboard,section,widgets,actions, andauthenticatehelpers let you describe your admin surface in plain Ruby.
How It Works
Mount the engine
Call
admin inside your routes.rb to mount the engine and declare your admin resources.Generate a base controller
Create an
Admin::BaseController that inherits from your ApplicationController and includes Torque::Admin::BaseController.Torque Admin is currently in alpha (
v0.1.0.a1). The public API is stable enough for production experimentation, but breaking changes may occur before the 1.0 release.