simplify top level sdk quickstart

Author: devalog

fern/products/sdks/fern-folder.mdx

@@ -1,34 +1,85 @@
 ---
 title: Quickstart
-subtitle: Set up the fern folder
 ---
 
 Configuring Fern starts with the `fern` folder, the root directory that contains
-your API definitions, generators, and your CLI version. 
-
-## Set up the fern folder
+your API definitions, SDK generators, and CLI version. 
 
 <Steps>
+<Step title="Install the Fern CLI">
 
-<Markdown src="/products/sdks/snippets/install-cli.mdx"/>
-
-  ### Initialize the Fern Folder
-
-  <Markdown src="/products/sdks/snippets/initialize-fern-folder-intro.mdx"/>
+  ```bash
+  npm install -g fern-api
+  ```
+</Step>
+ <Step title="Initialize the fern folder">
+  Initialize the fern folder with your existing OpenAPI specification, or start from scratch with a Fern Definition template. Specify your organization name using the `--organization` flag. 
 
-  <AccordionGroup>
-  <Markdown src="/products/sdks/snippets/option-1-openapi.mdx"/>
+  ```bash
+  # OpenAPI (local)
+  fern init --openapi path/to/openapi.yml \
+  --organization <YourOrganization>
 
-  <Accordion title="Option 2: Fern Definition">
-  
-  <Markdown src="/products/sdks/snippets/option-2-fern-def.mdx"/>
-    </Accordion>
+  # OpenAPI (URL)
+  fern init --openapi https://api.example.com/openapi.yml \
+  --organization <YourOrganization>
 
-    {/* <Markdown src="/products/sdks/snippets/option-3-asyncapi.mdx"/> */}    
-  </AccordionGroup>
+  # Fern Definition
+  fern init --organization <YourOrganization>
+  ```
+  <Tip>
+    OpenAPI accepts both JSON and YAML formats. You can always convert a [Fern Definition to OpenAPI](/api-definitions/ferndef/export-openapi) or OpenAPI to a Fern Definition later on.
+  </Tip>
+     
+  This creates a `fern` folder in your current directory.
+  <Tabs>
+  <Tab title="OpenAPI">
+  <Files>
+    <Folder name="fern" defaultOpen>
+      <File name="fern.config.json" comment="root-level configuration" />
+      <Folder name="api" defaultOpen comment="your API">
+        <File name="generators.yml" comment="generators you're using" />
+        <Folder name="openapi" defaultOpen>
+          <File name="openapi.yml" comment="API-level configuration" />
+        </Folder>
+      </Folder>
+    </Folder>
+  </Files>
+  </Tab>
+  <Tab title="Fern Definition">
+  <Files>
+    <Folder name="fern" defaultOpen>
+      <File name="fern.config.json" comment="root-level configuration" />
+      <File name="generators.yml" comment="generators you're using" />
+      <Folder name="definition" defaultOpen>
+        <File name="api.yml" comment="API-level configuration" />
+        <File name="imdb.yml" comment="endpoints, types, and errors" />
+      </Folder>
+    </Folder>
+  </Files>
 
-  ### Next: Set up your repository structure
+  <Note> `imdb.yml` contains an example movies API. If you’re just
+  generating an SDK for test purposes, you can leave this file as it is. To
+  generate an SDK for your own API instead of the example movies API,
+  replace `imdb.yml` with your own endpoints, types, and errors. </Note>
+  </Tab>
+  </Tabs>
+  </Step>
+  <Step title="Next steps">
 
-  Now that you have your `fern` folder initialized, [learn how to organize your repositories for SDK generation](/sdks/overview/project-structure).
- 
+  <CardGroup cols={2}>
+    <Card title="Learn about project structure" icon="regular folder-tree" href="/learn/sdks/overview/project-structure">
+      Understand how to organize your API definitions and generators.
+    </Card>
+    <Card title="Generate SDKs" icon="regular code" href="/learn/sdks/overview/introduction">
+      Explore all supported languages.
+    </Card>
+    <Card title="Build with TypeScript" icon="regular rocket" href="/learn/sdks/generators/typescript/quickstart">
+      Get started with TypeScript SDK generation.
+    </Card>
+    <Card title="Add custom code" icon="regular code-branch" href="/learn/sdks/overview/custom-code">
+      Extend your generated SDKs with custom functionality.
+    </Card>
+  </CardGroup>
+ </Step>
 </Steps>