mirror of
https://github.com/prdlk/website.git
synced 2026-08-02 17:31:41 +00:00
feat(content): introduce projects, experience & speaking collections and support tagging, experiences & draft status across content types
This commit is contained in:
Prad Nukala
+55
-12
@@ -1,4 +1,4 @@
|
||||
import { defineCollection } from "astro:content";
|
||||
import { defineCollection, reference } from "astro:content";
|
||||
import { glob } from "astro/loaders";
|
||||
import { z } from "astro/zod";
|
||||
|
||||
@@ -12,8 +12,13 @@ const baseSchema = z.object({
|
||||
title: titleSchema,
|
||||
});
|
||||
|
||||
const post = defineCollection({
|
||||
loader: glob({ base: "./src/content/post", pattern: "**/*.{md,mdx}" }),
|
||||
// Experiences double as a taxonomy: projects, writing & speaking reference them
|
||||
// by id so each experience page can render everything filed under it.
|
||||
const experienceRefs = z.array(reference("experience")).default([]);
|
||||
|
||||
// /writing section.
|
||||
const writing = defineCollection({
|
||||
loader: glob({ base: "./src/content/writing", pattern: "**/*.{md,mdx}" }),
|
||||
schema: ({ image }) =>
|
||||
baseSchema.extend({
|
||||
description: z.string(),
|
||||
@@ -26,6 +31,7 @@ const post = defineCollection({
|
||||
draft: z.boolean().default(false),
|
||||
ogImage: z.string().optional(),
|
||||
tags: z.array(z.string()).default([]).transform(removeDupsAndLowerCase),
|
||||
experiences: experienceRefs,
|
||||
publishDate: z
|
||||
.string()
|
||||
.or(z.date())
|
||||
@@ -38,22 +44,59 @@ const post = defineCollection({
|
||||
}),
|
||||
});
|
||||
|
||||
const note = defineCollection({
|
||||
loader: glob({ base: "./src/content/note", pattern: "**/*.{md,mdx}" }),
|
||||
schema: baseSchema.extend({
|
||||
// /projects section.
|
||||
const projects = defineCollection({
|
||||
loader: glob({ base: "./src/content/projects", pattern: "**/*.{md,mdx}" }),
|
||||
schema: ({ image }) =>
|
||||
baseSchema.extend({
|
||||
description: z.string().optional(),
|
||||
coverImage: z
|
||||
.object({
|
||||
alt: z.string(),
|
||||
src: image(),
|
||||
})
|
||||
.optional(),
|
||||
link: z.url().optional(),
|
||||
repo: z.url().optional(),
|
||||
tags: z.array(z.string()).default([]).transform(removeDupsAndLowerCase),
|
||||
experiences: experienceRefs,
|
||||
publishDate: z.iso
|
||||
.datetime({ offset: true }) // Ensures ISO 8601 format with offsets allowed (e.g. "2024-01-01T00:00:00Z" and "2024-01-01T00:00:00+02:00")
|
||||
.datetime({ offset: true }) // ISO 8601 with offsets allowed (e.g. "2024-01-01T00:00:00Z")
|
||||
.transform((val) => new Date(val)),
|
||||
}),
|
||||
});
|
||||
|
||||
const tag = defineCollection({
|
||||
loader: glob({ base: "./src/content/tag", pattern: "**/*.{md,mdx}" }),
|
||||
schema: z.object({
|
||||
title: titleSchema.optional(),
|
||||
// Experience = resume entries that also act as the taxonomy for the site.
|
||||
const experience = defineCollection({
|
||||
loader: glob({ base: "./src/content/experience", pattern: "**/*.{md,mdx}" }),
|
||||
schema: baseSchema.extend({
|
||||
organization: z.string(),
|
||||
role: z.string().optional(),
|
||||
location: z.string().optional(),
|
||||
url: z.url().optional(),
|
||||
description: z.string().optional(),
|
||||
startDate: z.coerce.date(),
|
||||
endDate: z.coerce.date().optional(), // omit for current/ongoing
|
||||
}),
|
||||
});
|
||||
|
||||
export const collections = { post, note, tag };
|
||||
// Speaking = talks/presentations rendered with an embedded Cloudflare Stream
|
||||
// player, linking back to the original YouTube recording as the source.
|
||||
const speaking = defineCollection({
|
||||
loader: glob({ base: "./src/content/speaking", pattern: "**/*.{md,mdx}" }),
|
||||
schema: baseSchema.extend({
|
||||
description: z.string(),
|
||||
videoId: z.string(), // Cloudflare Stream video UID
|
||||
originalSource: z.url().optional(), // link to the original YouTube video
|
||||
event: z.string().optional(),
|
||||
draft: z.boolean().default(false),
|
||||
tags: z.array(z.string()).default([]).transform(removeDupsAndLowerCase),
|
||||
experiences: experienceRefs,
|
||||
publishDate: z
|
||||
.string()
|
||||
.or(z.date())
|
||||
.transform((val) => new Date(val)),
|
||||
}),
|
||||
});
|
||||
|
||||
export const collections = { writing, projects, experience, speaking };
|
||||
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
title: Sonr
|
||||
organization: Sonr
|
||||
role: Founder & Lead Engineer
|
||||
location: Remote
|
||||
url: https://sonr.io
|
||||
startDate: 2021-01-01
|
||||
description: Building decentralized identity infrastructure — a blockchain-based service network for user-owned authentication and data.
|
||||
---
|
||||
|
||||
Founded and lead engineering at Sonr, a decentralized identity and data network. Built the core blockchain protocol, WebAuthn-based authentication, and developer tooling for self-sovereign identity.
|
||||
|
||||
Projects and writing filed under this experience appear below.
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
title: Sonr Network
|
||||
description: A decentralized identity and data network with WebAuthn-based authentication.
|
||||
publishDate: "2024-10-14T11:23:00Z"
|
||||
link: "https://sonr.io"
|
||||
repo: "https://github.com/sonr-io/sonr"
|
||||
tags: ["blockchain", "identity", "go"]
|
||||
experiences: ["sonr"]
|
||||
---
|
||||
|
||||
The core protocol and service network powering self-sovereign identity. Users own their authentication credentials and data, with no central authority.
|
||||
|
||||
Built with the Cosmos SDK, IPFS, and WebAuthn. This project is filed under my **Sonr** experience.
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
title: The Future of Decentralized Identity
|
||||
description: A talk on self-sovereign identity and why users should own their authentication.
|
||||
videoId: REPLACE_WITH_CLOUDFLARE_STREAM_UID
|
||||
originalSource: https://www.youtube.com/watch?v=dQw4w9WgXcQ
|
||||
event: Example Conf 2024
|
||||
publishDate: "2024-06-01"
|
||||
tags: ["identity", "blockchain"]
|
||||
experiences: ["sonr"]
|
||||
---
|
||||
|
||||
A walkthrough of the architecture behind user-owned identity, the tradeoffs of decentralization, and where the ecosystem is heading.
|
||||
|
||||
Replace `videoId` with the real Cloudflare Stream UID and write up the talk notes here.
|
||||
@@ -0,0 +1,135 @@
|
||||
---
|
||||
title: "Markdown Admonitions"
|
||||
description: "This post showcases using the markdown admonition feature in Astro Cactus"
|
||||
publishDate: "25 Aug 2024"
|
||||
updatedDate: "4 July 2025"
|
||||
tags: ["markdown", "admonitions"]
|
||||
---
|
||||
|
||||
## What are admonitions
|
||||
|
||||
Admonitions (also known as “asides”) are useful for providing supportive and/or supplementary information related to your content.
|
||||
|
||||
## How to use them
|
||||
|
||||
To use admonitions in Astro Cactus, wrap your Markdown content in a pair of triple colons `:::`. The first pair should also include the type of admonition you want to use.
|
||||
|
||||
For example, with the following Markdown:
|
||||
|
||||
```md
|
||||
:::note
|
||||
Highlights information that users should take into account, even when skimming.
|
||||
:::
|
||||
```
|
||||
|
||||
Outputs:
|
||||
|
||||
:::note
|
||||
Highlights information that users should take into account, even when skimming.
|
||||
:::
|
||||
|
||||
## Admonition Types
|
||||
|
||||
The following admonitions are currently supported:
|
||||
|
||||
- `note`
|
||||
- `tip`
|
||||
- `important`
|
||||
- `warning`
|
||||
- `caution`
|
||||
|
||||
### Note
|
||||
|
||||
```md
|
||||
:::note
|
||||
Highlights information that users should take into account, even when skimming.
|
||||
:::
|
||||
```
|
||||
|
||||
:::note
|
||||
Highlights information that users should take into account, even when skimming.
|
||||
:::
|
||||
|
||||
### Tip
|
||||
|
||||
```md
|
||||
:::tip
|
||||
Optional information to help a user be more successful.
|
||||
:::
|
||||
```
|
||||
|
||||
:::tip
|
||||
Optional information to help a user be more successful.
|
||||
:::
|
||||
|
||||
### Important
|
||||
|
||||
```md
|
||||
:::important
|
||||
Crucial information necessary for users to succeed.
|
||||
:::
|
||||
```
|
||||
|
||||
:::important
|
||||
Crucial information necessary for users to succeed.
|
||||
:::
|
||||
|
||||
### Caution
|
||||
|
||||
```md
|
||||
:::caution
|
||||
Negative potential consequences of an action.
|
||||
:::
|
||||
```
|
||||
|
||||
:::caution
|
||||
Negative potential consequences of an action.
|
||||
:::
|
||||
|
||||
### Warning
|
||||
|
||||
```md
|
||||
:::warning
|
||||
Critical content demanding immediate user attention due to potential risks.
|
||||
:::
|
||||
```
|
||||
|
||||
:::warning
|
||||
Critical content demanding immediate user attention due to potential risks.
|
||||
:::
|
||||
|
||||
## Customising the admonition title
|
||||
|
||||
You can customise the admonition title using the following markup:
|
||||
|
||||
```md
|
||||
:::note[My custom title]
|
||||
This is a note with a custom title.
|
||||
:::
|
||||
```
|
||||
|
||||
Outputs:
|
||||
|
||||
:::note[My custom title]
|
||||
This is a note with a custom title.
|
||||
:::
|
||||
|
||||
## GitHub Repository Cards
|
||||
|
||||
You can add dynamic cards that link to GitHub repositories, on page load, the repository information is pulled from the GitHub API.
|
||||
|
||||
::github{repo="chrismwilliams/astro-theme-cactus"}
|
||||
|
||||
You can also link a Github user:
|
||||
|
||||
::github{user="withastro"}
|
||||
|
||||
To use this feature you just use the "Github" directive:
|
||||
|
||||
```markdown title="Linking a repo"
|
||||
::github{repo="chrismwilliams/astro-theme-cactus"}
|
||||
```
|
||||
|
||||
```markdown title="Linking a user"
|
||||
::github{user="withastro"}
|
||||
```
|
||||
@@ -0,0 +1,174 @@
|
||||
---
|
||||
title: "A post of Markdown elements"
|
||||
description: "This post is for testing and listing a number of different markdown elements"
|
||||
publishDate: "22 Feb 2023"
|
||||
updatedDate: 22 Jan 2024
|
||||
tags: ["test", "markdown"]
|
||||
pinned: true
|
||||
---
|
||||
|
||||
## This is a H2 Heading
|
||||
|
||||
### This is a H3 Heading
|
||||
|
||||
#### This is a H4 Heading
|
||||
|
||||
##### This is a H5 Heading
|
||||
|
||||
###### This is a H6 Heading
|
||||
|
||||
## Horizontal Rules
|
||||
|
||||
---
|
||||
|
||||
---
|
||||
|
||||
---
|
||||
|
||||
## Emphasis
|
||||
|
||||
**This is bold text**
|
||||
|
||||
_This is italic text_
|
||||
|
||||
~~Strikethrough~~
|
||||
|
||||
## Quotes
|
||||
|
||||
"Double quotes" and 'single quotes'
|
||||
|
||||
## Blockquotes
|
||||
|
||||
> Blockquotes can also be nested...
|
||||
>
|
||||
> > ...by using additional greater-than signs right next to each other...
|
||||
|
||||
## References
|
||||
|
||||
An example containing a clickable reference[^1] with a link to the source.
|
||||
|
||||
Second example containing a reference[^2] with a link to the source.
|
||||
|
||||
[^1]: Reference first footnote with a return to content link.
|
||||
|
||||
[^2]: Second reference with a link.
|
||||
|
||||
If you check out this example in `src/content/post/markdown-elements/index.md`, you'll notice that the references and the heading "Footnotes" are added to the bottom of the page via the [remark-rehype](https://github.com/remarkjs/remark-rehype#options) plugin.
|
||||
|
||||
## Lists
|
||||
|
||||
Unordered
|
||||
|
||||
- Create a list by starting a line with `+`, `-`, or `*`
|
||||
- Sub-lists are made by indenting 2 spaces:
|
||||
- Marker character change forces new list start:
|
||||
- Ac tristique libero volutpat at
|
||||
- Facilisis in pretium nisl aliquet
|
||||
- Nulla volutpat aliquam velit
|
||||
- Very easy!
|
||||
|
||||
Ordered
|
||||
|
||||
1. Lorem ipsum dolor sit amet
|
||||
2. Consectetur adipiscing elit
|
||||
3. Integer molestie lorem at massa
|
||||
|
||||
4. You can use sequential numbers...
|
||||
5. ...or keep all the numbers as `1.`
|
||||
|
||||
Start numbering with offset:
|
||||
|
||||
57. foo
|
||||
1. bar
|
||||
|
||||
## Code
|
||||
|
||||
Inline `code`
|
||||
|
||||
Indented code
|
||||
|
||||
// Some comments
|
||||
line 1 of code
|
||||
line 2 of code
|
||||
line 3 of code
|
||||
|
||||
Block code "fences"
|
||||
|
||||
```
|
||||
Sample text here...
|
||||
```
|
||||
|
||||
Syntax highlighting
|
||||
|
||||
```js
|
||||
var foo = function (bar) {
|
||||
return bar++;
|
||||
};
|
||||
|
||||
console.log(foo(5));
|
||||
```
|
||||
|
||||
### Expressive code examples
|
||||
|
||||
Adding a title
|
||||
|
||||
```js title="file.js"
|
||||
console.log("Title example");
|
||||
```
|
||||
|
||||
A bash terminal
|
||||
|
||||
```bash
|
||||
echo "A base terminal example"
|
||||
```
|
||||
|
||||
Highlighting code lines
|
||||
|
||||
```js title="line-markers.js" del={2} ins={3-4} {6}
|
||||
function demo() {
|
||||
console.log("this line is marked as deleted");
|
||||
// This line and the next one are marked as inserted
|
||||
console.log("this is the second inserted line");
|
||||
|
||||
return "this line uses the neutral default marker type";
|
||||
}
|
||||
```
|
||||
|
||||
[Expressive Code](https://expressive-code.com/) can do a ton more than shown here, and includes a lot of [customisation](https://expressive-code.com/reference/configuration/).
|
||||
|
||||
## Tables
|
||||
|
||||
| Option | Description |
|
||||
| ------ | ------------------------------------------------------------------------- |
|
||||
| data | path to data files to supply the data that will be passed into templates. |
|
||||
| engine | engine to be used for processing templates. Handlebars is the default. |
|
||||
| ext | extension to be used for dest files. |
|
||||
|
||||
### Table Alignment
|
||||
|
||||
| Item | Price | # In stock |
|
||||
| ------------ | :---: | ---------: |
|
||||
| Juicy Apples | 1.99 | 739 |
|
||||
| Bananas | 1.89 | 6 |
|
||||
|
||||
### Keyboard elements
|
||||
|
||||
| Action | Shortcut |
|
||||
| --------------------- | ------------------------------------------ |
|
||||
| Vertical split | <kbd>Alt+Shift++</kbd> |
|
||||
| Horizontal split | <kbd>Alt+Shift+-</kbd> |
|
||||
| Auto split | <kbd>Alt+Shift+d</kbd> |
|
||||
| Switch between splits | <kbd>Alt</kbd> + arrow keys |
|
||||
| Resizing a split | <kbd>Alt+Shift</kbd> + arrow keys |
|
||||
| Close a split | <kbd>Ctrl+Shift+W</kbd> |
|
||||
| Maximize a pane | <kbd>Ctrl+Shift+P</kbd> + Toggle pane zoom |
|
||||
|
||||
## Images
|
||||
|
||||
Image in the same folder: `src/content/post/markdown-elements/logo.png`
|
||||
|
||||
|
||||
|
||||
## Links
|
||||
|
||||
[Content from markdown-it](https://markdown-it.github.io/)
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 3.6 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 591 KiB |
@@ -0,0 +1,10 @@
|
||||
---
|
||||
title: "Example Cover Image"
|
||||
description: "This post is an example of how to add a cover/hero image"
|
||||
publishDate: "04 July 2023"
|
||||
updatedDate: "14 August 2023"
|
||||
coverImage:
|
||||
src: "./cover.png"
|
||||
alt: "Astro build wallpaper"
|
||||
tags: ["test", "image"]
|
||||
---
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
title: "A working draft title"
|
||||
description: "This post is for testing the draft post functionality"
|
||||
publishDate: "10 March 2024"
|
||||
tags: ["test"]
|
||||
draft: true
|
||||
---
|
||||
|
||||
If this is working correctly, this post should only be accessible in a dev environment, as well as any tags that are unique to this post.
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "Lorem ipsum dolor sit, amet consectetur adipisicing elit. Id"
|
||||
description: "This post is purely for testing if the css is correct for the title on the page"
|
||||
publishDate: "01 Feb 2023"
|
||||
tags: ["test"]
|
||||
---
|
||||
|
||||
## Testing the title tag
|
||||
@@ -0,0 +1,22 @@
|
||||
---
|
||||
title: "Example OG Social Image"
|
||||
publishDate: "27 January 2023"
|
||||
description: "An example post for Astro Cactus, detailing how to add a custom social image card in the frontmatter"
|
||||
tags: ["example", "blog", "image"]
|
||||
ogImage: "/social-card.png"
|
||||
---
|
||||
|
||||
## Adding your own social image to a post
|
||||
|
||||
This post is an example of how to add a custom [open graph](https://ogp.me/) social image, also known as an OG image, to a blog post.
|
||||
By adding the optional ogImage property to the frontmatter of a post, you opt out of [satori](https://github.com/vercel/satori) automatically generating an image for this page.
|
||||
|
||||
If you open this markdown file `src/content/post/social-image.md` you'll see the ogImage property set to an image which lives in the public folder[^1].
|
||||
|
||||
```yaml
|
||||
ogImage: "/social-card.png"
|
||||
```
|
||||
|
||||
You can view the one set for this template page [here](https://astro-cactus.chriswilliams.dev/social-card.png).
|
||||
|
||||
[^1]: The image itself can be located anywhere you like.
|
||||
@@ -0,0 +1,66 @@
|
||||
---
|
||||
title: "Adding Webmentions to Astro Cactus"
|
||||
description: "This post describes the process of adding webmentions to your own site"
|
||||
publishDate: "11 Oct 2023"
|
||||
tags: ["webmentions", "astro", "social"]
|
||||
updatedDate: 6 December 2024
|
||||
pinned: true
|
||||
---
|
||||
|
||||
## TLDR
|
||||
|
||||
1. Add a link on your homepage to either your GitHub profile and/or email address as per [IndieLogin's](https://indielogin.com/setup) instructions. You _could_ do this via `src/components/SocialList.astro`, just be sure to include `isWebmention` to the relevant link if doing so.
|
||||
2. Create an account @ [Webmention.io](https://webmention.io/) by entering your website's address.
|
||||
3. Add the link feed and api key to a `.env` file with the key `WEBMENTION_URL` and `WEBMENTION_API_KEY` respectively, you could rename `.env.example` found in this template. You can also add the optional `WEBMENTION_PINGBACK` link here too.
|
||||
4. Go to [brid.gy](https://brid.gy/) and sign-in to each social account[s] you wish to link.
|
||||
5. Publish and build your website, remember to add the api key, and it should now be ready to receive webmentions!
|
||||
|
||||
## What are webmentions
|
||||
|
||||
Put simply, it's a way to show users who like, comment, repost and more, on various pages on your website via social media.
|
||||
|
||||
This theme displays the number of likes, mentions and replies each blog post receives. There are a couple of more webmentions that I haven't included, like reposts, which are currently filtered out, but shouldn't be too difficult to include.
|
||||
|
||||
## Steps to add it to your own site
|
||||
|
||||
Your going to have to create a couple of accounts to get things up-and-running. But, the first thing you need to ensure is that your social links are correct.
|
||||
|
||||
### Add link(s) to your profile(s)
|
||||
|
||||
Firstly, you need to add a link on your site to prove ownership. If you have a look at [IndieLogin's](https://indielogin.com/setup) instructions, it gives you 2 options, either an email address and/or GitHub account. I've created the component `src/components/SocialList.astro` where you can add your details into the `socialLinks` array, just include the `isWebmention` property to the relevant link which will add the `rel="me authn"` attribute. Whichever way you do it, make sure you have a link in your markup as per IndieLogin's [instructions](https://indielogin.com/setup)
|
||||
|
||||
```html
|
||||
<a href="https://github.com/your-username" rel="me">GitHub</a>
|
||||
```
|
||||
|
||||
### Sign up to Webmention.io
|
||||
|
||||
Next, head over to [Webmention.io](https://webmention.io/) and create an account by signing in with your domain name, e.g. `https://astro-cactus.chriswilliams.dev/`. Please note that .app TLDs don't function correctly. Once in, it will give you a couple of links for your domain to accept webmentions. Make a note of these and create a `.env` file (this template include an example `.env.example` which you could rename). Add the link feed and api key with the key/values of `WEBMENTION_URL` and `WEBMENTION_API_KEY` respectively, and the optional `WEBMENTION_PINGBACK` url if required. Please try not to publish this to a repository!
|
||||
|
||||
:::note
|
||||
You don't have to include the pingback link. Maybe coincidentally, but after adding it I started to receive a higher frequency of spam in my mailbox, informing me that my website could be better. TBH they're not wrong. I've now removed it, but it's up to you.
|
||||
:::
|
||||
|
||||
### Sign up to Brid.gy
|
||||
|
||||
You're now going to have to use [brid.gy](https://brid.gy/). As the name suggests, it links your website to your social media accounts. For every account you want to set up (e.g. Mastodon), click on the relevant button and connect each account you want brid.gy to search. Just to note again, brid.gy currently has an issue with .app TLDs.
|
||||
|
||||
## Testing everything works
|
||||
|
||||
With everything set, it's now time to build and publish your website. **REMEMBER** to set your environment variables `WEBMENTION_API_KEY` & `WEBMENTION_URL` with your host.
|
||||
|
||||
You can check to see if everything is working by sending a test webmention via [webmentions.rocks](https://webmention.rocks/receive/1). Log in with your domain, enter the auth code, and then the url of the page you want to test. For example, to test this page I would add `https://astro-cactus.chriswilliams.dev/posts/webmentions/`. To view it on your website, rebuild or (re)start dev mode locally, and you should see the result at the bottom of your page.
|
||||
|
||||
You can also view any test mentions in the browser via their [api](https://github.com/aaronpk/webmention.io#api).
|
||||
|
||||
## Things to add, things to consider
|
||||
|
||||
- At the moment, fresh webmentions are only fetched on a rebuild or restarting dev mode, which obviously means if you don't update your site very often you wont get a lot of new content. It should be quite trivial to add a cron job to run the `getAndCacheWebmentions()` function in `src/utils/webmentions.ts` and populate your blog with new content. This is probably what I'll add next as a github action.
|
||||
|
||||
- I have seen some mentions have duplicates. Unfortunately, they're quite difficult to filter out as they have different id's.
|
||||
|
||||
- I'm not a huge fan of the little external link icon for linking to comments/replies. It's not particularly great on mobile due to its size, and will likely change it in the future.
|
||||
|
||||
## Acknowledgements
|
||||
|
||||
Many thanks to [Kieran McGuire](https://github.com/chrismwilliams/astro-theme-cactus/issues/107#issue-1863931105) for sharing this with me, and the helpful posts. I'd never heard of webmentions before, and now with this update hopefully others will be able to make use of them. Additionally, articles and examples from [kld](https://kld.dev/adding-webmentions/) and [ryanmulligan.dev](https://ryanmulligan.dev/blog/) really helped in getting this set up and integrated, both a great resource if you're looking for more information!
|
||||
@@ -0,0 +1,22 @@
|
||||
import { type CollectionEntry, getCollection } from "astro:content";
|
||||
|
||||
/** All experiences, most recent (by startDate) first. */
|
||||
export async function getAllExperience(): Promise<CollectionEntry<"experience">[]> {
|
||||
const entries = await getCollection("experience");
|
||||
return entries.sort((a, b) => b.data.startDate.valueOf() - a.data.startDate.valueOf());
|
||||
}
|
||||
|
||||
const hasExperience = (
|
||||
entry: { data: { experiences: { id: string }[] } },
|
||||
id: string,
|
||||
): boolean => entry.data.experiences.some((ref) => ref.id === id);
|
||||
|
||||
/** Every project, writing & talk filed under a given experience id. */
|
||||
export async function getContentForExperience(id: string) {
|
||||
const [projects, writing, speaking] = await Promise.all([
|
||||
getCollection("projects", (e) => hasExperience(e, id)),
|
||||
getCollection("writing", (e) => (import.meta.env.PROD ? !e.data.draft : true) && hasExperience(e, id)),
|
||||
getCollection("speaking", (e) => (import.meta.env.PROD ? !e.data.draft : true) && hasExperience(e, id)),
|
||||
]);
|
||||
return { projects, writing, speaking };
|
||||
}
|
||||
+4
-38
@@ -1,49 +1,15 @@
|
||||
import { type CollectionEntry, getCollection } from "astro:content";
|
||||
|
||||
/** filter out draft posts based on the environment */
|
||||
export async function getAllPosts(): Promise<CollectionEntry<"post">[]> {
|
||||
return await getCollection("post", ({ data }) => {
|
||||
export async function getAllPosts(): Promise<CollectionEntry<"writing">[]> {
|
||||
return await getCollection("writing", ({ data }) => {
|
||||
return import.meta.env.PROD ? !data.draft : true;
|
||||
});
|
||||
}
|
||||
|
||||
/** Get tag metadata by tag name */
|
||||
export async function getTagMeta(tag: string): Promise<CollectionEntry<"tag"> | undefined> {
|
||||
const tagEntries = await getCollection("tag", (entry) => {
|
||||
return entry.id === tag;
|
||||
});
|
||||
return tagEntries[0];
|
||||
}
|
||||
|
||||
/** groups posts by year (based on option siteConfig.sortPostsByUpdatedDate), using the year as the key
|
||||
/** groups posts by year, using the year as the key
|
||||
* Note: This function doesn't filter draft posts, pass it the result of getAllPosts above to do so.
|
||||
*/
|
||||
export function groupPostsByYear(posts: CollectionEntry<"post">[]) {
|
||||
export function groupPostsByYear(posts: CollectionEntry<"writing">[]) {
|
||||
return Object.groupBy(posts, (post) => post.data.publishDate.getFullYear().toString());
|
||||
}
|
||||
|
||||
/** returns all tags created from posts (inc duplicate tags)
|
||||
* Note: This function doesn't filter draft posts, pass it the result of getAllPosts above to do so.
|
||||
* */
|
||||
export function getAllTags(posts: CollectionEntry<"post">[]) {
|
||||
return posts.flatMap((post) => [...post.data.tags]);
|
||||
}
|
||||
|
||||
/** returns all unique tags created from posts
|
||||
* Note: This function doesn't filter draft posts, pass it the result of getAllPosts above to do so.
|
||||
* */
|
||||
export function getUniqueTags(posts: CollectionEntry<"post">[]) {
|
||||
return [...new Set(getAllTags(posts))];
|
||||
}
|
||||
|
||||
/** returns a count of each unique tag - [[tagName, count], ...]
|
||||
* Note: This function doesn't filter draft posts, pass it the result of getAllPosts above to do so.
|
||||
* */
|
||||
export function getUniqueTagsWithCount(posts: CollectionEntry<"post">[]): [string, number][] {
|
||||
return [
|
||||
...getAllTags(posts).reduce(
|
||||
(acc, t) => acc.set(t, (acc.get(t) ?? 0) + 1),
|
||||
new Map<string, number>(),
|
||||
),
|
||||
].sort((a, b) => b[1] - a[1]);
|
||||
}
|
||||
|
||||
@@ -0,0 +1,8 @@
|
||||
import { type CollectionEntry, getCollection } from "astro:content";
|
||||
|
||||
/** filter out draft talks in production */
|
||||
export async function getAllSpeaking(): Promise<CollectionEntry<"speaking">[]> {
|
||||
return await getCollection("speaking", ({ data }) => {
|
||||
return import.meta.env.PROD ? !data.draft : true;
|
||||
});
|
||||
}
|
||||
Reference in New Issue
Block a user