A Rails engine for easily including static pages like 'About us' or marketing content in your application.
High Voltage is a Ruby gem and Rails engine designed to simplify the inclusion of static pages in Ruby on Rails applications. It automatically handles routing and rendering for pages like 'About us', marketing content, or directions by treating them as view templates stored in a designated directory. This eliminates the need to manually configure routes and controllers for static content.
Rails developers who need to add static content pages to their applications without creating custom controllers and routes for each page. It's particularly useful for projects requiring marketing sites, informational pages, or any non-dynamic content integrated into a Rails app.
Developers choose High Voltage because it reduces boilerplate code by providing a convention-based approach to static pages, integrates seamlessly with Rails' routing and view system, and offers flexibility through configuration and override options when custom behavior is needed.
Easily include static pages in your Rails app.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically routes URLs to view files in `app/views/pages`, including support for nested directories, eliminating manual route configuration for static content.
Seamlessly works with Rails features like `content_for` for page titles and I18n for localization, fitting naturally into existing Rails workflows.
Allows custom controllers for adding authentication, different layouts, or advanced page-finding logic, providing adaptability beyond static defaults.
With minimal configuration, pages are created as view templates and linked using `page_path`, reducing boilerplate code for static pages.
The gem is only receiving bug fixes and compatibility updates, with no new features planned, which may limit its evolution for modern needs.
Designed exclusively for static pages; integrating dynamic content requires complex overrides or separate solutions, adding development overhead.
Built-in caching was removed, forcing developers to rely on Rails caching mechanisms manually, which can be an extra step for performance optimization.