sharing template between frontend and backend (admin or adminhtml) in magento

sharing template between frontend and backend (admin or adminhtml) in magento

October 6, 2026 · Illustrated author avatarBy Stefan Bogdanescu
sharing template between frontend and backend (admin or adminhtml) in magento

Reusing Frontend UI Components in Magento Adminhtml

As a Magento developer, you might often find yourself wanting to reuse certain frontend templates or UI components in your adminhtml (backend) views. This could be due to similar functionality requiring the same user interface, or it might simply be to maintain consistency between your frontend and backend designs.

Understanding the Divide Between Frontend and Adminhtml

Magento separates its frontend and backend responsibilities into distinct areas for a reason. The design/frontend directory contains all the theme-specific assets like templates (phtml), layouts (xml), and stylesheets that power your store’s public interface. On the other hand, the design/adminhtml folder houses these same types of files but specifically for the admin panel.

By default, Magento does not provide a shared location or mechanism to directly reference frontend components from the backend. This is primarily due to the different layout structures and context required by each environment.

Current Options for Sharing UI Components

However, there are workarounds available:

1. Copying Templates Between Directories

You can copy your desired frontend template into a corresponding location in design/adminhtml. For example, if you have a template located at app/design/frontend/default/mytheme/template/catalog/product/view.phtml, you could copy it to app/design/adminhtml(default)/mytheme/template/sales/order/view.phtml.

This approach works but it’s not ideal. It creates duplicated code and makes maintenance more difficult.

2. Using a Custom Module

You can create a custom Magento module that includes your shared component in its own template directory, then reference this from both frontend and adminhtml layouts as needed. This provides better separation of concerns.

Best Practice: Extending the Core to Share Layout Handles

A cleaner solution is to extend the core layout handles and include your shared components within them. Here’s an example:

  1. In your custom module, create a new layout XML file (e.g., app/code/Vendor/Module/view/frontend/layout/your_layout_file.xml).

  2. Define your component as a block inside this new layout handle.

  3. Then, from both frontend and adminhtml layouts, you can include the new layout handle:

<!-- app/design/frontend/default/mytheme/layout/some_page.phtml -->
<referenceContainer name="content">
    <block class="Magento\Framework\View\Element\Template" template="Vendor_Module::your_template_file.phtml"/>
</referenceContainer>
<!-- app/design/adminhtml/default/default/layout/some_admin_page.xml -->
<referenceContainer name="content">
    <block class="Magento\Framework\View\Element\Template" template="Vendor_Module::your_template_file.phtml"/>
</referenceContainer>

Remember, if you’re sharing complex components or want to maintain them in a single place for both frontend and adminhtml, consider using a custom module approach. It provides better separation of concerns and easier maintenance.

Conclusion

While Magento does not provide an out-of-the-box mechanism to share UI components directly between the frontend and adminhtml areas, it allows you to work around this limitation through various techniques like copying files or creating custom modules with shared layout handles. The best choice depends on your specific needs.

Remember, consistency is key in user experience. Reusing components can help maintain a consistent look and feel across your Magento installation.

If you’re looking for more advanced Magento development tips and tricks, consider checking out Laravel Company’s Magento development services. We specialize in providing high-quality, performance-driven solutions tailored to our clients’ unique business needs.

Catalog Themes Admin Orders

Our network