Skip to content
This repository was archived by the owner on Dec 15, 2022. It is now read-only.
This repository was archived by the owner on Dec 15, 2022. It is now read-only.

Increasing readability of used terminology through adding a definition table #753

@LonelySquid

Description

@LonelySquid

Hello Devs!

Why this post?
I have a tiny suggestion & question about the Keymaps In-Depth page. Some time ago I installed an sublime-block-comment plugin and I figured out I wanted to change the key binding of that plugin, so I found on the settings page of the plugin and found some information. I did not understand this, for I do not understand what a 'selector' is, and have additionaly still no idea what the 'source' is for too. That is when I searched the flight manual of Atom for additional information, despite me grasping it bit by bit it still feels a kind of messy, so this suggestion is primarily about the centralisation of the key concepts being expressed on the Keymaps In-Depth page to enhance readability.

Suggestions

  • Create a table at the top of the Keymaps In-Depth page, listing the Keystroke, Command, Selector (and Source?) with a super brief piece of information, and maybe a link if there is another page that explains more about these basic hotkey topics.
  • Maybe adding colors to the definitions, with an piece of code in color too, so it becomes more visual for beginners like me.
  • Maybe adding a brief summary of the definitions to the keymap.cson too if it whould increase the readability.

I hope this feedback helps! Happy 2022, big thumbs up and thank you for reading!

Aqua

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions