Skip to content

Use links and buttons consistently #258

@arildm

Description

@arildm

Use links for navigation, and buttons for actions.

Some buttons that should be links:

  • "New corpus"
  • "Edit" in the config panel
  • "Manage access" in the sharing panel
  • "Custom config" on the corpus config page

Proposed style guidelines below.

  • Update code to match this
  • Add this to dev docs

  • Use buttons for actions (that change app state or mental state) and links for navigation
    • If both state-changing and navigating, use a button
    • Remove link underline in places where links are default, e.g. app header
    • For buttons, use <RouteButton> or <ActionButton>, which use the mink-button class
      • Complement with button-{primary,danger,warning,success}, button-mute (less eye-catching) and button-slim (smaller)

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationuxUser experience, usability issues

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions