Skip to content

UX suggestion: simplify the intro text of "Cover geometry" page #564

@environ314

Description

@environ314

Checklist

  • I have searched existing enhancements and this is not a duplicate.
  • This request covers a single enhancement (open a separate issue for each one).
  • I have filled out the template below.

Adaptive Cover Pro version

2.27.0

Is your enhancement related to a problem?

Context

The "Cover geometry" configuration page currently starts with a general intro paragraph,
followed by a second paragraph listing which fields apply to which cover type
(vertical, awning, tilt/venetian, etc.):

"Height of window and shaded zone are mandatory for vertical and awning covers.
Reveal depth and sill height improve geometric precision for windows recessed in the wall.
Awning width and angle apply to horizontal awnings. Slat depth and spacing are mandatory
for tilt/venetian covers."

Image

Observation

This second paragraph is redundant, because the form displayed just below
already only shows the fields relevant to the cover type selected in the previous step.
The user doesn't need to mentally filter "which fields apply to me" — the UI already does it.

The paragraph adds reading load and makes the page feel denser than it actually is.

Describe the solution you'd like

Replace the per-type field listing with a short contextual sentence that reflects
the already-selected cover type, for example:

"Enter the measurements below for your {cover_type} cover."

Where {cover_type} is dynamically filled with "vertical", "awning", "tilt/venetian", etc.

Alternatively, if dynamic substitution is not convenient, simply remove the second
paragraph entirely — the form labels are self-explanatory.

The first paragraph (explaining why these measurements matter for sun-blocking calculation)
remains valuable and should stay.

Benefit

  • Shorter, less intimidating page
  • No redundant information
  • Contextual feedback ("you're configuring a vertical cover") reinforces user confidence

Alternatives you've considered

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions