This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /* title */ | |
| .daily-note-title { | |
| font-size: var(--font-smallest) !important; | |
| padding: var(--size-4-1) var(--context-padding) !important; | |
| color: var(--text-faint) !important; | |
| max-width: 100% !important; | |
| transition: color .3s ease; |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /* title */ | |
| .daily-note-title { | |
| font-size: var(--font-smallest) !important; | |
| padding: var(--size-4-1) var(--context-padding) !important; | |
| color: var(--text-faint) !important; | |
| max-width: 100% !important; | |
| transition: color .3s ease; |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /* | |
| There's two ways to see if the answer matches more efficiently | |
| Both of ways use arrays to contain the answers, and loop through them to find the answer | |
| These are better beacuse | |
| 1. they're less lines, and easier to read from a developer's perspective | |
| 2. they're also more flexible; say if you wanted to use this code in another app, | |
| or change the words themselves for any other reason, it's easy to edit the answers array | |
| and use the same code again because the actual answers are defined in one place rather | |
| than in each "if" case over and over again | |
| */ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /* | |
| There's two ways to see if the answer matches more efficiently | |
| Both of ways use arrays to contain the answers, and loop through them to find the answer | |
| These are better beacuse | |
| 1. they're less lines, and easier to read from a developer's perspective | |
| 2. they're also more flexible; say if you wanted to use this code in another app, | |
| or change the words themselves for any other reason, it's easy to edit the answers array | |
| and use the same code again because the actual answers are defined in one place rather | |
| than in each "if" case over and over again | |
| */ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| import React, { useState, useEffect } from "react" | |
| // eslint-disable-next-line | |
| import { css, jsx } from "@emotion/core" | |
| import styled from "@emotion/styled" | |
| import tw from "tailwind.macro" | |
| /* @jsx jsx */ | |
| const Wrapper = styled.div` | |
| ${tw`bg-gray-200 rounded-sm block`} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| import React, { useState, useEffect } from "react" | |
| import axios from "axios" | |
| // eslint-disable-next-line | |
| import { css, jsx } from "@emotion/core" | |
| import tw from "tailwind.macro" | |
| /* @jsx jsx */ | |
| import NewPasteForm from "../components/molecules/new-paste" | |
| import Card from "../components/atoms/card" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| import React from "react" | |
| import { Link } from "gatsby" | |
| import styled from "styled-components" | |
| import tw from "tailwind.macro" | |
| // Arrow components | |
| import DownGold from "../../images/icons/arrow/Down-gold.svg" | |
| import RightGold from "../../images/icons/arrow/Right-gold.svg" | |
| import DownPurple from "../../images/icons/arrow/Down-purple.svg" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| module.exports = { | |
| theme: { | |
| extend: {} | |
| }, | |
| variants: {}, | |
| plugins: [] | |
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /* | |
| Tailwind - The Utility-First CSS Framework | |
| A project by Adam Wathan (@adamwathan), Jonathan Reinink (@reinink), | |
| David Hemphill (@davidhemphill) and Steve Schoger (@steveschoger). | |
| Welcome to the Tailwind config file. This is where you can customize | |
| Tailwind specifically for your project. Don't be intimidated by the | |
| length of this file. It's really just a big JavaScript object and |
NewerOlder