jacksonhardaker

# Old Repo
1. Fresh clone
2. Remove origin remote
3. git filter-repo --to-subdirectory-filter foo/bar

# New Repo
1. git add remote og-repo ../path/to/og/repo
2. git pull og-repo main --allow-unrelated-histories

jacksonhardaker

const Z_INDEX_0 = 0;
const Z_INDEX_1 = 100;
const Z_INDEX_2 = 200;
const Z_INDEX_3 = 300;
const Z_INDEX_4 = 400;
const Z_INDEX_5 = 500;
const Z_INDEX_6 = 600;
const Z_INDEX_7 = 700;
const Z_INDEX_8 = 800;
const Z_INDEX_9 = 900;

jacksonhardaker

const presets = ["next/babel"];

const plugins = [];

if (process.env.SERVER_ENV === "production") {
  plugins.push([
    "react-remove-properties",
    { properties: ["data-testid", /data-cy$/] },
  ]);
  plugins.push(["transform-react-remove-prop-types"]);

jacksonhardaker

Keybase proof

I hereby claim:

• I am jacksonhardaker on github.
• I am jacksonhardaker (https://keybase.io/jacksonhardaker) on keybase.
• I have a public key ASCJiDUwocpNBRTnJhrpb4wxx0oqtC-Nz4djkX66ozTS1Ao

To claim this, I am signing this object:

jacksonhardaker

LESS Coding Guidelines

Medium uses a strict subset of LESS for style generation. This subset includes variables and mixins, but nothing else (no nesting, etc.).

Medium's naming conventions are adapted from the work being done in the SUIT CSS framework. Which is to say, it relies on structured class names and meaningful hyphens (i.e., not using hyphens merely to separate words). This is to help work around the current limits of applying CSS to the DOM (i.e., the lack of style encapsulation) and to better communicate the relationships between classes.

Table of contents

• JavaScript