Consistent Handling of “Title” Field Across All Templates #520
Description
Several templates/components handle the Title field differently. Some use it as a frontend‑visible heading, while others use it only as an internal label for editors in the backend. This inconsistency creates confusion and leads to unexpected behavior on the frontend.
Current Problem
- In some components, the Title field is displayed on the frontend and automatically hidden when the component has no visible content (e.g., no products available).
- In other components—such as the Product Slider—the Title field is not used for frontend display. Instead, the editor must manually add a separate text field for the visible title.
- This manually added title does not disappear when the component has no content (e.g., no related products, missing variants, empty product lists), resulting in an empty section with a visible heading.
Why This Is an Issue
- Editors expect consistent behavior across templates.
- It creates extra work and confusion when some components require a custom title field while others don’t.
- It leads to poor UX when a title is shown even though the component itself is empty.
- It increases the risk of layout issues and “floating” headings on the page