Skip to content

Instantly share code, notes, and snippets.

View kwhite's full-sized avatar
:octocat:
what happens when i do th

Katherine White kwhite

:octocat:
what happens when i do th
View GitHub Profile
@kwhite
kwhite / gist:4331645a4bd8d49346fdcaa417b1922b
Created September 28, 2020 19:50 — forked from rxaviers/gist:7360908
Complete list of github markdown emoji markup

People

:bowtie: :bowtie: 😄 :smile: 😆 :laughing:
😊 :blush: 😃 :smiley: ☺️ :relaxed:
😏 :smirk: 😍 :heart_eyes: 😘 :kissing_heart:
😚 :kissing_closed_eyes: 😳 :flushed: 😌 :relieved:
😆 :satisfied: 😁 :grin: 😉 :wink:
😜 :stuck_out_tongue_winking_eye: 😝 :stuck_out_tongue_closed_eyes: 😀 :grinning:
😗 :kissing: 😙 :kissing_smiling_eyes: 😛 :stuck_out_tongue:
@kwhite
kwhite / README-Template.md
Last active May 15, 2018 15:06 — forked from PurpleBooth/README-Template.md
A template to make good README.md

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

@kwhite
kwhite / pull_request_template.md
Last active July 30, 2020 14:37 — forked from indiesquidge/pull_request_template.md
An example PR template

Description

As a developer, I need to start with a story.

A few sentences describing the overall goals of the pull request's commits. What is the current behavior of the app? What is the updated/expected behavior with this PR? Include your acceptance critiera! If your tasks were well-written, you can probably copy/paste some of this.

Affected URL

link_to_relevant_multidev_or_test_site

@kwhite
kwhite / keybase.md
Created December 4, 2017 17:36
KeyBase Proof

Keybase proof

I hereby claim:

  • I am kwhite on github.
  • I am cheshirekat (https://keybase.io/cheshirekat) on keybase.
  • I have a public key ASATfDmrZmijxSRiBfKTLgOeR3Rtm_yEIxXkKx_64rrqRwo

To claim this, I am signing this object:

@kwhite
kwhite / wcus2017-gutenberg-feedback.md
Last active December 14, 2017 18:19
Tab-based usability feedback on Gutenberg navigation.

Gutenberg Feedback 2017-12-03

Terminology

In my feedback I’m defining things this way:

  • Items - Individual block types in a list.
  • Sections - Groupings of Items with a semantic title
  • Tabs - Recent, Blocks, Embeds

Block insertion controls

Ultimately… I think the editor navigation would make more sense with a “rule” that tabs move you from “unit” to “unit”, and arrows move you within (and between, if they are nested) sections/units. It gives the interaction more of a consistent rule and I feel like it would help because people are transitioning between mental states if they’re perusing a list of Items vs jumping from Recent to Embed, for example.