diff --git a/content/advanced/creating components.md b/content/advanced/creating components.md
index 0944eedd..6cdaed19 100644
--- a/content/advanced/creating components.md
+++ b/content/advanced/creating components.md
@@ -2,9 +2,129 @@
title: Creating your own Quartz components
---
-See the [component listing](/tags/component) for a full-list of the Quartz built-in components.
+> [!warning]
+> This guide assumes you have experience writing JavaScript and are familiar with TypeScript.
-- css
-- scripts
+Normally on the web, we write layout code using HTML which looks something like the following:
+
+```html
+
+ An article header
+ Some content
+
+```
+
+This piece of HTML represents an article with a leading header that says "An article header" and a paragraph that contains the text "Some content". This is normally combined with CSS to style the page and JavaScript to add interactivity.
+
+However, HTML doesn't let you create reusable templates. If you wanted to create a new page, you would need to copy and paste the above snippet and edit the header and content yourself. This isn't great if we have a lot of content on our site that shares a lot of similar layout. The smart people who created React also had similar thoughts, inventing the concept of JSX Components to solve the code duplication problem.
+
+In effect, components allow you to write a JavaScript function that takes some data and produces HTML as an output. **While Quartz doesn't use React, it uses the same component concept to allow you to easily express layout templates in your Quartz site.**
+
+> [!hint]
+> For those coming from React, Quartz components are different from React components in that it only uses JSX for templating and layout. Hooks like `useEffect`, `useState`, etc. are not rendered.
+## An Example Component
+
+### Constructor
+Component files are written in `.tsx` files that live in the `quartz/components` folder. These are re-exported in `quartz/components/index.ts` so you can use them in layouts and other components more easily.
+
+Each component file should have a default export that satisfies the `QuartzComponentConstructor` function signature. It is a function that takes in a single optional parameter `opts` and returns a Quartz Component. The type of the parameters `ops` is defined by the interface `Options` which you as the component creator also decide.
+
+In your component, you can use the values from the configuration option to change the rendering behaviour inside of your component. For example, the component in the code snippet below will not render if the `favouriteNumber` option is below 0.
+
+```tsx {11-17}
+interface Options {
+ favouriteNumber: number
+}
+
+const defaultOptions: Options = {
+ favouriteNumber: 42
+}
+
+export default ((userOpts?: Options) => {
+ const opts = { ...userOpts, ...defaultOpts }
+ function YourComponent(props: QuartzComponentProps) {
+ if (opts.favouriteNumber < 0) {
+ return null
+ }
+
+ return My favourite number is {opts.favouriteNumber}
+ }
+
+ return YourComponent
+}) satisfies QuartzComponentConstructor
+```
+
+### Props
+The Quartz component itself (lines 11-17 highlighted above) looks like a React component. It takes in properties (sometimes called [props](https://react.dev/learn/passing-props-to-a-component)) and returns JSX.
+
+All Quartz components accept the same set of props which are defined in `QuartzComponentProps`:
+
+```tsx title="quartz/components/types.ts"
+// simplified for sake of demonstration
+export type QuartzComponentProps = {
+ fileData: QuartzPluginData
+ cfg: GlobalConfiguration
+ tree: Node
+ allFiles: QuartzPluginData[]
+ displayClass?: "mobile-only" | "desktop-only"
+}
+```
+
+- `fileData`: Any metadata [[making plugins|plugins]] may have added to the current page.
+ - `fileData.slug`: slug of the current page.
+ - `fileData.frontmatter`: any frontmatter parsed.
+- `cfg`: The `configuration` field in `quartz.config.ts`.
+- `tree`: the resulting [HTML AST](https://github.com/syntax-tree/hast) after processing and transforming the file. This is useful if you'd like to render the content using [hast-util-to-jsx-runtime](https://github.com/syntax-tree/hast-util-to-jsx-runtime) (you can find an example of this in `quartz/components/pages/Content.tsx`).
+- `allFiles`: Metadata for all files that have been parsed. Useful for doing page listings or figuring out the overall site structure.
+- `displayClass`: a utility class that indicates a preference from the user about how to render it in a mobile or desktop setting. Helpful if you want to conditionally hide a component on mobile or desktop.
+
+### Styling
+Quartz components can also define a `.css` property on the actual function component which will get picked up by Quartz. This is expected to be a CSS string which can either be inlined or imported from a `.scss` file.
+
+Note that inlined styles **must** be plain vanilla CSS.
+
+```tsx {6-10} title="quartz/components/YourComponent.tsx"
+export default (() => {
+ function YourComponent() {
+ return Example Component
+ }
+
+ YourComponent.css = `
+ p {
+ color: red;
+ }
+ `
+
+ return YourComponent
+}) satisfies QuartzComponentConstructor
+```
+
+Imported styles, however, can be from SCSS files.
+
+```tsx {1-2,9} title="quartz/components/YourComponent.tsx"
+// assuming your stylesheet is in quartz/components/styles/YourComponent.scss
+import styles from "./styles/YourComponent.scss"
+
+export default (() => {
+ function YourComponent() {
+ return Example Component
+ }
+
+ YourComponent.css = styles
+ return YourComponent
+}) satisfies QuartzComponentConstructor
+```
+
+> [!warning]
+> Quartz does not use CSS modules so any styles you declare here apply *globally*. If you only want it to apply to your component, make sure you use specific class names and selectors.
+### Scripts and Interactivity
- listening for the nav event
- best practice: anything here should unmount any existing event handlers to prevent memory leaks
+
+### Using a Component
+#### In a layout
+#### In the configuration
+
+
+> [!hint]
+> Look in `quartz/components` for more examples of components in Quartz as reference for your own components!
diff --git a/quartz/styles/base.scss b/quartz/styles/base.scss
index 185582e8..5a6b5dbc 100644
--- a/quartz/styles/base.scss
+++ b/quartz/styles/base.scss
@@ -42,6 +42,7 @@ ul,
hyphens: auto;
}
+
.math {
font-size: 1.1rem;
&.math-display {
@@ -108,6 +109,10 @@ a {
margin-top: 0;
margin-bottom: 0;
}
+
+ p > strong {
+ color: var(--dark);
+ }
}
& > #quartz-body {
diff --git a/quartz/styles/callouts.scss b/quartz/styles/callouts.scss
index d49443e8..f26f2cce 100644
--- a/quartz/styles/callouts.scss
+++ b/quartz/styles/callouts.scss
@@ -14,59 +14,59 @@
&[data-callout="note"] {
--color: #448aff;
- --border: #448aff22;
- --bg: #448aff09;
+ --border: #448aff44;
+ --bg: #448aff10;
}
&[data-callout="abstract"] {
--color: #00b0ff;
- --border: #00b0ff22;
- --bg: #00b0ff09;
+ --border: #00b0ff44;
+ --bg: #00b0ff10;
}
&[data-callout="info"],
&[data-callout="todo"] {
--color: #00b8d4;
- --border: #00b8d422;
- --bg: #00b8d409;
+ --border: #00b8d444;
+ --bg: #00b8d410;
}
&[data-callout="tip"] {
--color: #00bfa5;
- --border: #00bfa522;
- --bg: #00bfa509;
+ --border: #00bfa544;
+ --bg: #00bfa510;
}
&[data-callout="success"] {
--color: #09ad7a;
- --border: #09ad7122;
- --bg: #09ad7109;
+ --border: #09ad7144;
+ --bg: #09ad7110;
}
&[data-callout="question"] {
--color: #dba642;
- --border: #dba64222;
- --bg: #dba64209;
+ --border: #dba64244;
+ --bg: #dba64210;
}
&[data-callout="warning"] {
--color: #db8942;
- --border: #db894222;
- --bg: #db894209;
+ --border: #db894244;
+ --bg: #db894210;
}
&[data-callout="failure"],
&[data-callout="danger"],
&[data-callout="bug"] {
--color: #db4242;
- --border: #db424222;
- --bg: #db424209;
+ --border: #db424244;
+ --bg: #db424210;
}
&[data-callout="example"] {
--color: #7a43b5;
- --border: #7a43b522;
- --bg: #7a43b509;
+ --border: #7a43b544;
+ --bg: #7a43b510;
}
&[data-callout="quote"] {