various path fixes for links to extensions, fix relative paths in links
This commit is contained in:
		@@ -7,7 +7,7 @@ title: Making your own plugins
 | 
			
		||||
 | 
			
		||||
Quartz's plugins are a series of transformations over content. This is illustrated in the diagram of the processing pipeline below:
 | 
			
		||||
 | 
			
		||||
![[quartz-transform-pipeline.png]]
 | 
			
		||||
![[quartz transform pipeline.png]]
 | 
			
		||||
 | 
			
		||||
All plugins are defined as a function that takes in a single parameter for options `type OptionType = object | undefined` and return an object that corresponds to the type of plugin it is.
 | 
			
		||||
 | 
			
		||||
 
 | 
			
		||||
@@ -50,7 +50,7 @@ This part of the configuration concerns anything that can affect the whole site.
 | 
			
		||||
 | 
			
		||||
You can think of Quartz plugins as a series of transformations over content.
 | 
			
		||||
 | 
			
		||||
![[quartz-transform-pipeline.png]]
 | 
			
		||||
![[quartz transform pipeline.png]]
 | 
			
		||||
 | 
			
		||||
```ts
 | 
			
		||||
plugins: {
 | 
			
		||||
 
 | 
			
		||||
@@ -4,6 +4,8 @@ draft: true
 | 
			
		||||
 | 
			
		||||
## todo
 | 
			
		||||
 | 
			
		||||
- static icon path (in head) never gets updated
 | 
			
		||||
	- do we update relative links on spa?
 | 
			
		||||
- back button with anchors / popovers + spa is broken
 | 
			
		||||
- debounce cfg rebuild on large repos
 | 
			
		||||
  - investigate content rebuild triggering multiple times even when debounced, causing an esbuild deadlock
 | 
			
		||||
 
 | 
			
		||||
@@ -100,7 +100,7 @@ Here's how to add a custom domain to your GitHub pages deployment.
 | 
			
		||||
     - `185.199.111.153`
 | 
			
		||||
   - If you are using a subdomain, navigate to your DNS provider and create a `CNAME` record that points your subdomain to the default domain for your site. For example, if you want to use the subdomain `quartz.example.com` for your user site, create a `CNAME` record that points `quartz.example.com` to `<github-username>.github.io`.
 | 
			
		||||
 | 
			
		||||
![[dns-records.png]]_The above shows a screenshot of Google Domains configured for both `jzhao.xyz` (an apex domain) and `quartz.jzhao.xyz` (a subdomain)._
 | 
			
		||||
![[dns records.png]]_The above shows a screenshot of Google Domains configured for both `jzhao.xyz` (an apex domain) and `quartz.jzhao.xyz` (a subdomain)._
 | 
			
		||||
 | 
			
		||||
See the [GitHub documentation](https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain) for more detail about how to setup your own custom domain with GitHub Pages.
 | 
			
		||||
 | 
			
		||||
 
 | 
			
		||||
| 
		 Before Width: | Height: | Size: 76 KiB After Width: | Height: | Size: 76 KiB  | 
| 
		 Before Width: | Height: | Size: 55 KiB After Width: | Height: | Size: 55 KiB  | 
| 
		 Before Width: | Height: | Size: 72 KiB After Width: | Height: | Size: 72 KiB  | 
@@ -20,7 +20,7 @@ export interface FullPageLayout {
 | 
			
		||||
 | 
			
		||||
These correspond to following parts of the page:
 | 
			
		||||
 | 
			
		||||
![[quartz-layout.png|800]]
 | 
			
		||||
![[quartz layout.png|800]]
 | 
			
		||||
 | 
			
		||||
> [!note]
 | 
			
		||||
> There are two additional layout fields that are _not_ shown in the above diagram.
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user