f5686d45be
* wip: updating settings layout * most issues resolved * settings layout revamped * fix:multiple unrequired toast on formatter settings resolved * feat: updated ai-models tabs to extract common components and logic * chore: formatting fix * chore: code cleanup * fix: forward navigation handling * fix: model selections ux * fix: vocabulary update flow * chore: update lang list * chore: cleanup migrations * fix: invalid drag class on back buttont * chore: swap to tanstack router * fix: history navigation * chore: clean up + models unification * chore: cleanup migrations * refactor: settings deep merges --------- Co-authored-by: amadeus-x1 <45001978+amadeus-x1@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| app | ||
| components/ui | ||
| content/docs | ||
| lib | ||
| public | ||
| scripts | ||
| .env.example | ||
| .gitignore | ||
| components.json | ||
| eslint.config.mjs | ||
| mdx-components.tsx | ||
| next.config.mjs | ||
| package.json | ||
| postcss.config.mjs | ||
| README.md | ||
| source.config.ts | ||
| tsconfig.json | ||
| wrangler.jsonc | ||
www
This is a Next.js application generated with Create Fumadocs.
Run development server:
npm run dev
# or
pnpm dev
# or
yarn dev
Open http://localhost:3000 with your browser to see the result.
Content Management
Docs
Docs are written in MDX in the contents/docs folder.
Fetching Blog Content
This project includes a script to fetch blog content and images from an S3-compatible storage (Wasabi):
# Set up environment variables (see .env.example)
pnpm fetch-content
The script will:
- Fetch MDX files from the
blog/folder in the S3 bucket and save them tocontent/blogs/ - Fetch images from the
blog-images/folder in the S3 bucket and save them topublic/blog/
Building the Application
The build process includes fetching content from S3:
pnpm build
The build will fail if the content fetch fails. This ensures that the site is always built with the latest content and that any issues with the content fetch process are immediately apparent.
To use this in CI/CD environments, make sure to configure the appropriate AWS credentials as environment variables.