1
0
Fork 0
Commit graph

7 commits

Author SHA1 Message Date
Joost De Cock
469eb43c95
feat: Add various content types to docusaurus (#7231)
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.
2024-11-18 11:05:16 +01:00
joostdecock
0dece4d70e wip(org): Started working on v3 workbench 2023-05-08 19:28:03 +02:00
Joost De Cock
322100f54c chore: Extended prettier for config files + run 2022-10-13 16:19:36 +02:00
Joost De Cock
25bbca5fb2 chore: Move meta-info from design config to repo config 2022-08-27 13:25:42 +02:00
joostdecock
217bb8588d fix: Add JSON import assertions for NodeJS 16 2022-08-24 09:45:59 +02:00
Joost De Cock
43ee0f1790 chore: Adapt sites to recent changes 2022-06-17 12:02:09 +02:00
Joost De Cock
e4035b2509 chore: Re-structure workspaces, enforce build order
These are some changes in the way the monorepo is structured,
that are aimed at making it easier to get started.

There are two important changes:

**Multiple workspaces**

We had a yarn workspaces setup at `packages/*`. But our monorepo has
grown to 92 packages which can be overwhelming for people not familiar
with the package names.

To remedy this, I've split it into 4 different workspaces:

- `designs/*`: Holds FreeSewing designs (think patterns)
- `plugins/*`: Holds FreeSewing plugins
- `packages/*`: Holds other packages published on NPM
- `sites/*`: Holds software that is not published as an NPM package,
  such as our various websites and backend API

This should make it easier to find things, and to answer questions like
*where do I find the code for the plugins*.

**Updated reconfigure script to handle build order**

One problem when bootstrapping the repo is inter-dependencies between
packages. For example, building a pattern will only work once
`plugin-bundle` is built. Which will only work once all plugins in the
bundle or built. And that will only work when `core` is built, and so
on.

This can be frustrating for new users as `yarn buildall` will fail.
And it gets overlooked by seasoned devs because they're likely to have
every package built in their repo so this issue doesn't concern them.

To remedy this, we now have a `config/build-order.mjs` file and the
updated `/scripts/reconfigure.mjs` script will enforce the build order
so that things *just work*.
2022-06-16 17:11:31 +02:00