ernesto-oss · ernestoresende · Jun 17, 2023 · Jun 17, 2023 · Jun 17, 2023 · Jun 17, 2023
diff --git a/cli/README.md b/cli/README.md
@@ -55,7 +55,7 @@ npx create-cardinal-app@latest
 
 ## Docs
 
-You can find detailed information about the available tech stacks, recommendations on how to choose and use your stack, and addtional resources about the included tools [in the docs](https://cardinal.ernestoresende.com/docs/en/introduction).
+You can find detailed information about the available tech stacks, recommendations on how to choose and use your stack, and addtional resources about the included tools [in the docs](https://cardinal.ernestoresende.com/docs/introduction).
 
 ## Contribution
 

diff --git a/cli/package.json b/cli/package.json
@@ -27,7 +27,7 @@
     "dependencyMap:update": "esrun ./src/helpers/updateDependencyMap.ts",
     "dp:update": "esrun ./src/helpers/updateDependencyMap.ts",
     "dev": "tsup --watch --env.PACKAGE_MANAGER_OVERRIDE=pnpm --env.NODE_ENV=development",
-    "format": "pnpm prettier --parser=babel-ts --check \"src/**/*.{ts,tsx,js,jsx}\" --ignore-unknown",
+    "format": "pnpm prettier --plugin-search-dir=. --check \"src/**/*.{ts,tsx,js,jsx}\" --ignore-unknown",
     "format:write": "pnpm format -w",
     "lint": "pnpm eslint . -c .eslintrc.cjs",
     "lint:fix": "pnpm lint --fix",
@@ -47,10 +47,10 @@
   "devDependencies": {
     "@digitak/esrun": "^3.2.24",
     "@ianvs/prettier-plugin-sort-imports": "^4.0.2",
-    "@types/eslint": "^8.40.1",
+    "@types/eslint": "^8.40.2",
     "@types/fs-extra": "^11.0.1",
     "@types/js-yaml": "^4.0.5",
-    "@types/node": "^20.3.0",
+    "@types/node": "^20.3.1",
     "@typescript-eslint/eslint-plugin": "^5.59.11",
     "@typescript-eslint/parser": "^5.59.11",
     "eslint": "^8.42.0",

diff --git a/cli/prettier.config.cjs b/cli/prettier.config.cjs
@@ -3,7 +3,24 @@ const baseConfig = require("../prettier.config.cjs");
 /** @type {import('prettier').Config} */
 const config = {
   ...baseConfig,
-  plugins: [...baseConfig.plugins],
+  importOrderSeparation: false,
+  importOrderSortSpecifiers: true,
+  importOrderBuiltinModulesToTop: true,
+  importOrderParserPlugins: ["typescript", "decorators-legacy"],
+  importOrderMergeDuplicateImports: true,
+  importOrderCombineTypeAndValueImports: true,
+  importOrder: [
+    "<THIRD_PARTY_MODULES>",
+    "",
+    "^types$",
+    "^@/(.*)$",
+    "^@/helpers(.*)$",
+    "^@/installers/(.*)$",
+    "^@/utils/(.*)$",
+    "",
+    "^[./]",
+  ],
+  plugins: [require("@ianvs/prettier-plugin-sort-imports")],
 };
 
 module.exports = config;
diff --git a/cli/src/index.ts b/cli/src/index.ts
@@ -55,7 +55,7 @@ async function main() {
 
   process.stdout.write(
     `${color.dim(
-      "Need help choosing your stack? Head to https://cardinal.ernestoresende.com/docs/en/recommendations",
+      "Need help choosing your stack? Head to https://cardinal.ernestoresende.com/docs/recommendations",
     )}\n \n`,
   );
 

diff --git a/package.json b/package.json
@@ -29,7 +29,6 @@
   "dependencies": {
     "@changesets/changelog-github": "^0.4.8",
     "@changesets/cli": "^2.26.1",
-    "@ianvs/prettier-plugin-sort-imports": "^4.0.2",
     "@types/node": "^20.2.5",
     "@types/prettier": "^2.7.3",
     "eslint-config-prettier": "^8.8.0",

diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
diff --git a/prettier.config.cjs b/prettier.config.cjs
@@ -6,22 +6,4 @@ module.exports = {
   semi: true,
   trailingComma: "all",
   tabWidth: 2,
-  importOrderSeparation: false,
-  importOrderSortSpecifiers: true,
-  importOrderBuiltinModulesToTop: true,
-  importOrderParserPlugins: ["typescript", "decorators-legacy"],
-  importOrderMergeDuplicateImports: true,
-  importOrderCombineTypeAndValueImports: true,
-  importOrder: [
-    "<THIRD_PARTY_MODULES>",
-    "",
-    "^types$",
-    "^@/(.*)$",
-    "^@/helpers(.*)$",
-    "^@/installers/(.*)$",
-    "^@/utils/(.*)$",
-    "",
-    "^[./]",
-  ],
-  plugins: [require("@ianvs/prettier-plugin-sort-imports")],
 };
diff --git a/www/.prettierrc.cjs b/www/.prettierrc.cjs
diff --git a/www/README.md b/www/README.md
@@ -1,175 +0,0 @@
-# Astro Starter Kit: Docs Site
-
-```bash
-npm create astro@latest -- --template docs
-```
-
-[![Open in StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/github/withastro/astro/tree/latest/examples/docs)
-[![Open with CodeSandbox](https://assets.codesandbox.io/github/button-edit-lime.svg)](https://codesandbox.io/p/sandbox/github/withastro/astro/tree/latest/examples/docs)
-
-> 🧑‍🚀 **Seasoned astronaut?** Delete this file. Have fun!
-
-![docs](https://user-images.githubusercontent.com/4677417/186189283-0831b9ab-d6b9-485d-8955-3057e532ab31.png)
-
-## Features
-
-- ✅ **Full Markdown support**
-- ✅ **Responsive mobile-friendly design**
-- ✅ **Sidebar navigation**
-- ✅ **Search (powered by Algolia)**
-- ✅ **Multi-language i18n**
-- ✅ **Automatic table of contents**
-- ✅ **Automatic list of contributors**
-- ✅ (and, best of all) **dark mode**
-
-## 🧞 Commands
-
-All commands are run from the root of the project, from a terminal:
-
-| Command                | Action                                           |
-| :--------------------- | :----------------------------------------------- |
-| `npm install`          | Installs dependencies                            |
-| `npm run dev`          | Starts local dev server at `localhost:3000`      |
-| `npm run build`        | Build your production site to `./dist/`          |
-| `npm run preview`      | Preview your build locally, before deploying     |
-| `npm run astro ...`    | Run CLI commands like `astro add`, `astro check` |
-| `npm run astro --help` | Get help using the Astro CLI                     |
-
-To deploy your site to production, check out our [Deploy an Astro Website](https://docs.astro.build/guides/deploy) guide.
-
-## 👀 Want to learn more?
-
-Feel free to check [our documentation](https://docs.astro.build) or jump into our [Discord server](https://astro.build/chat).
-
-## Customize This Theme
-
-### Site metadata
-
-`src/config.ts` contains several data objects that describe metadata about your site like title, description, default language, and Open Graph details. You can customize these to match your project.
-
-### CSS styling
-
-The theme's look and feel is controlled by a few key variables that you can customize yourself. You'll find them in the `src/styles/theme.css` CSS file.
-
-If you've never worked with CSS variables before, give [MDN's guide on CSS variables](https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_custom_properties) a quick read.
-
-This theme uses a "cool blue" accent color by default. To customize this for your project, change the `--theme-accent` variable to whatever color you'd like:
-
-```diff
-/* src/styles/theme.css */
-:root {
-  color-scheme: light;
--  --theme-accent: hsla(var(--color-blue), 1);
-+  --theme-accent: hsla(var(--color-red), 1);   /* or: hsla(#FF0000, 1); */
-```
-
-## Page metadata
-
-Astro uses frontmatter in Markdown pages to choose layouts and pass properties to those layouts. If you are using the default layout, you can customize the page in many different ways to optimize SEO and other things. For example, you can use the `title` and `description` properties to set the document title, meta title, meta description, and Open Graph description.
-
-```markdown
----
-title: Example title
-description: Really cool docs example that uses Astro
-layout: ../../layouts/MainLayout.astro
----
-
-# Page content...
-```
-
-For more SEO related properties, look at `src/components/HeadSEO.astro`
-
-### Sidebar navigation
-
-The sidebar navigation is controlled by the `SIDEBAR` variable in your `src/config.ts` file. You can customize the sidebar by modifying this object. A default, starter navigation has already been created for you.
-
-```ts
-export const SIDEBAR = {
-  en: [
-    { text: "Section Header", header: true },
-    { text: "Introduction", link: "en/introduction" },
-    { text: "Page 2", link: "en/page-2" },
-    { text: "Page 3", link: "en/page-3" },
-
-    { text: "Another Section", header: true },
-    { text: "Page 4", link: "en/page-4" },
-  ],
-};
-```
-
-Note the top-level `en` key: This is needed for multi-language support. You can change it to whatever language you'd like, or add new languages as you go. More details on this below.
-
-### Multiple Languages support
-
-The Astro docs template supports multiple languages out of the box. The default theme only shows `en` documentation, but you can enable multi-language support features by adding a second language to your project.
-
-To add a new language to your project, you'll want to extend the current `src/content/docs/[lang]/...` layout:
-
-```diff
- 📂 src/content/docs
- ┣ 📂 en
- ┃ ┣ 📜 page-1.md
- ┃ ┣ 📜 page-2.md
- ┃ ┣ 📜 page-3.astro
-+ ┣ 📂 es
-+ ┃ ┣ 📜 page-1.md
-+ ┃ ┣ 📜 page-2.md
-+ ┃ ┣ 📜 page-3.astro
-```
-
-You'll also need to add the new language name to the `KNOWN_LANGUAGES` map in your `src/config.ts` file. This will enable your new language switcher in the site header.
-
-```diff
-// src/config.ts
-export const KNOWN_LANGUAGES = {
-  English: 'en',
-+  Spanish: 'es',
-};
-```
-
-Last step: you'll need to add a new entry to your sidebar, to create the table of contents for that language. While duplicating every page might not sound ideal to everyone, this extra control allows you to create entirely custom content for every language.
-
-> Make sure the sidebar `link` value points to the correct language!
-
-```diff
-// src/config.ts
-export const SIDEBAR = {
-  en: [
-    { text: 'Section Header', header: true, },
-    { text: 'Introduction', link: 'en/introduction' },
-    // ...
-  ],
-+  es: [
-+    { text: 'Encabezado de sección', header: true, },
-+    { text: 'Introducción', link: 'es/introduction' },
-+    // ...
-+  ],
-};
-
-// ...
-```
-
-If you plan to use Spanish as the default language, you just need to modify the redirect path in `src/pages/index.astro`:
-
-```diff
-<script>
-- window.location.pathname = `/en/introduction`;
-+ window.location.pathname = `/es/introduction`;
-</script>
-```
-
-You can also remove the above script and write a landing page in Spanish instead.
-
-### What if I don't plan to support multiple languages?
-
-That's totally fine! Not all projects need (or can support) multiple languages. You can continue to use this theme without ever adding a second language.
-
-If that single language is not English, you can just replace `en` in directory layouts and configurations with the preferred language.
-
-### Search (Powered by Algolia)
-
-[Algolia](https://www.algolia.com/) offers a free service to qualified open source projects called [DocSearch](https://docsearch.algolia.com/). If you are accepted to the DocSearch program, provide your API Key & index name in `src/config.ts` and a search box will automatically appear in your site header.
-
-Note that Aglolia and Astro are not affiliated. We have no say over acceptance to the DocSearch program.
-
-If you'd prefer to remove Algolia's search and replace it with your own, check out the `src/components/Header.astro` component to see where the component is added.

diff --git a/www/algolia/config.json b/www/algolia/config.json
@@ -1,6 +1,6 @@
 {
   "index_name": "cardinal-docs",
-  "start_urls": ["https://cardinal.ernestoresende.com/docs/en/introduction"],
+  "start_urls": ["https://cardinal.ernestoresende.com/docs/introduction"],
   "stop_urls": [],
   "selectors": {
     "lvl0": { "selector": "[data-algolia-lvl0]", "global": true },

diff --git a/www/astro.config.mjs b/www/astro.config.mjs
@@ -1,8 +1,8 @@
-import { defineConfig } from "astro/config";
-import react from "@astrojs/react";
-import tailwind from "@astrojs/tailwind";
 import image from "@astrojs/image";
 import mdx from "@astrojs/mdx";
+import react from "@astrojs/react";
+import tailwind from "@astrojs/tailwind";
+import { defineConfig } from "astro/config";
 
 // https://astro.build/config
 export default defineConfig({
-Original file line number
+Diff line change
@@ Expand Up / @@ -55,7 +55,7 @@ npx create-cardinal-app@latest @@
     ## Docs
-    You can find detailed information about the available tech stacks, recommendations on how to choose and use your stack, and addtional resources about the included tools [in the docs](https://cardinal.ernestoresende.com/docs/en/introduction).
+    You can find detailed information about the available tech stacks, recommendations on how to choose and use your stack, and addtional resources about the included tools [in the docs](https://cardinal.ernestoresende.com/docs/introduction).
     ## Contribution
@@ Expand Down @@