From 389bafdefc55eabe938c613499e623a28cb920e6 Mon Sep 17 00:00:00 2001 From: cha0s Date: Fri, 19 Jan 2024 08:09:19 -0600 Subject: [PATCH] chore: docs --- website/docs/creating-a-fleck.mdx | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/website/docs/creating-a-fleck.mdx b/website/docs/creating-a-fleck.mdx index f6ff4df..b908f0a 100644 --- a/website/docs/creating-a-fleck.mdx +++ b/website/docs/creating-a-fleck.mdx @@ -12,21 +12,17 @@ If you are following along from the previous getting started
About that "2 flecks" thing... - Actually, your server application has **4 flecks** at this point: + Actually, your server application has **3 flecks** at this point: - `@flecks/core` - `@flecks/core/server` - `@flecks/server` - - `@flecks/server/server` flecks will load the `[...]/server` fleck under any fleck that is loaded on the server. This is also the case when using `@flecks/web` which will automatically load `[...]/client` flecks which are only loaded in the browser. We'll be exploring this specifically in the next section. If you're intersted in diving deeper, see [the platforms concept page](#todo). - Some frameworks make it a little more opaque to work with isomorphic code, but the flecks - philosophy is that visibility is believability: you'll have to be explicit about which code - runs where.
## Your first fleck