VSinerva/freesewing
1
0
Fork 0
Code Activity

feat: Add various content types to docusaurus (#7231)

Browse source 
This brings blog posts, showcase posts, and newsletter editions into the Docusaurus site.

It also adds support for using TailwindCSS inside a container. So this will probably end up being the new freesewing.org site in v4.
This commit is contained in:
Joost De Cock 2024-11-18 11:05:16 +01:00 • committed by GitHub
parent ef8f68bcaf
commit 469eb43c95
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
595 changed files with 20432 additions and 2469 deletions
Download patch file Download diff file Expand all files Collapse all files

13
sites/dev/docs/tutorials/pattern-design/part2/our-first-part/readme.mdx
View file

@ -1,6 +1,6 @@
---
title: Creating a part
order: 20
sidebar_position: 20
---
Much like garments themselves, patterns are made up of _parts_.
@ -9,14 +9,14 @@ so on. The pattern you create today is very simple, and only has one part: the b
:::tip
It's a good idea to keep each part in its own file. You don't *have to* do
this, but it's a good habit to get into.
It's a good idea to keep each part in its own file. You don't _have to_ do
this, but it's a good habit to get into.
:::
## bib.mjs
I am going to use the **From scratch** template. So the files I want to edit live
I am going to use the **From scratch** template. So the files I want to edit live
in `design/from-scratch`.
Our part lives in `design/from-scratch/src/bib.mjs`, and it currently looks like this:
@ -41,8 +41,8 @@ The only mandatory keys on a part object are `name` and `draft`.
:::note RELATED
Refer to [the part reference documentation](/reference/api/part) for
all details about configuring the part object
Refer to [the part reference documentation](/reference/api/part) for
all details about configuring the part object
:::
:::note
@ -52,7 +52,6 @@ Each parts stands on its own, and parts from various designs can be combined
to create other designs.
:::
### The part name
```src/bib.mjs