diff --git a/content/4.guide/6.theming-guide/1.introduction.md b/content/4.guide/6.theming-guide/1.introduction.md
new file mode 100644
index 00000000..eee89e45
--- /dev/null
+++ b/content/4.guide/6.theming-guide/1.introduction.md
@@ -0,0 +1,75 @@
+---
+toc: true
+title: Theming Guide
+---
+## Theming in Nuxt
+
+This document explains how to set up and manage **theming in Nuxt 3**, including:
+
+- Defining **brand colors** and **semantic colors** (primary, secondary, etc.)
+- Structuring **theme tokens** for consistency
+- Theming with **Tailwind CSS** and **PrimeVue**
+- (Optional) Supporting light/dark mode and multiple themes
+
+---
+
+## 1. What is Theming?
+
+**Theming** is the process of defining a consistent visual identity for your application.
+
+It usually includes:
+
+- 🟡 Defining **brand colors** (e.g., your company's primary palette)
+- 🟢 Defining **semantic colors** (e.g., success, warning, error)
+- 🔵 Applying these colors globally in UI components
+- âš« Optionally enabling **light/dark** or multiple theme variants
+
+---
+
+## 2. Options for Theming in Nuxt
+
+You can manage themes in Nuxt using:
+
+1. **Tailwind CSS** – Define colors in `tailwind.config.js` and use utility classes
+2. **PrimeVue** – Use built-in themes or create custom theme overrides
+3. **CSS variables** – For flexible, runtime theme switching
+
+---
+
+## 3. Defining Brand & Semantic Colors (Base Layer)
+
+Even before Tailwind or PrimeVue, define your **color tokens** clearly.
+
+### Example color tokens:
+
+Brand colors:
+
+- `Primary`: #1D4ED8
+
+- `Secondary`: #9333EA
+
+- `Accent`: #F59E0B
+
+Semantic colors:
+
+- `Success`: #10B981
+
+- `Warning`: #F59E0B
+
+- `Error`: #EF4444
+
+- `Info`: #3B82F6
+
+
+These tokens can be used across Tailwind and PrimeVue themes to keep the system **consistent**.
+
+---
+
+## Final Notes
+
+* Use variables for colors, backgrounds, gradients, and even shadows.
+* Combine Tailwind's arbitrary values with semantic CSS variables.
+* Maintain consistent naming across light/dark modes.
+* Document each variable clearly to help future developers.
+
+A scalable theming approach will improve maintainability, accessibility, and performance across your Vue or Nuxt projects.
diff --git a/content/4.guide/6.theming-guide/2.nuxt-with-tailwind.md b/content/4.guide/6.theming-guide/2.nuxt-with-tailwind.md
new file mode 100644
index 00000000..f6415d9e
--- /dev/null
+++ b/content/4.guide/6.theming-guide/2.nuxt-with-tailwind.md
@@ -0,0 +1,131 @@
+---
+toc: true
+title: Nuxt with Tailwind
+---
+
+## Tailwind Installation
+
+Using Tailwind CSS in your Nuxt project is only one command away.
+
+#### 1. Install `@nuxtjs/tailwindcss` dependency to your project:
+
+```
+npx nuxi@latest module add tailwindcss
+```
+#### 2. If not already done, add it to your modules section in your nuxt.config:
+
+```
+export default defineNuxtConfig({
+ modules: ['@nuxtjs/tailwindcss']
+})
+```
+
+### Tailwind Files
+
+When running your Nuxt project, this module will look for these files:
+
+- `./assets/css/tailwind.css`
+- `./tailwind.config.{js,cjs,mjs,ts}`
+
+If these files don't exist, the module will automatically generate a basic configuration for them, so you don't have to create these files manually.
+
+You can create the `tailwind.config.js` file by running the following command, as noted by the Tailwind CSS installation guide:
+
+```
+npx tailwindcss init
+```
+
+If the above fails, you can try `npx tailwindcss-cli init`.
+
+If you're going to create your own CSS file for Tailwind CSS, make sure to add the @tailwind directives:
+
+```css
+@tailwind base;
+@tailwind components;
+@tailwind utilities;
+```
+
+### Module Configuration
+
+You can customize the module's behavior by using the tailwindcss property in nuxt.config:
+
+```js
+export default defineNuxtConfig({
+ modules: ['@nuxtjs/tailwindcss'],
+ tailwindcss: {
+ // Options
+ }
+})
+```
+
+
+## Theming with Tailwind CSS
+
+### Step 1: Define Colors in Tailwind
+
+Edit `tailwind.config.js`:
+
+```js
+export default {
+ darkMode: 'class',
+ theme: {
+ extend: {
+ colors: {
+ // Brand colors
+ brand: {
+ primary: '#1D4ED8',
+ secondary: '#9333EA',
+ accent: '#F59E0B'
+ },
+
+ // Semantic colors
+ semantic: {
+ success: '#10B981',
+ warning: '#F59E0B',
+ error: '#EF4444',
+ info: '#3B82F6'
+ }
+ }
+ }
+ }
+}
+```
+
+âś… Now you can use these colors anywhere:
+
+```html
+
+
Success message
+```
+
+### Step 2: (Optional) Use CSS Variables for Multiple Themes
+
+If you want multiple themes (e.g., light, dark, blue), define variables in a global CSS file.
+
+`assets/css/theme.css:`
+
+```css
+:root {
+ --color-primary: #1D4ED8;
+ --color-secondary: #9333EA;
+ --color-bg: #ffffff;
+ --color-text: #000000;
+}
+
+[data-theme="dark"] {
+ --color-primary: #60A5FA;
+ --color-secondary: #C084FC;
+ --color-bg: #0F172A;
+ --color-text: #ffffff;
+}
+```
+
+Use in components:
+
+```html
+
+```
+
+Or register these CSS variables as Tailwind colors if you prefer utility classes.
diff --git a/content/4.guide/9.primevue-theming-guide.md b/content/4.guide/6.theming-guide/3.nuxt-with-primevue.md
similarity index 89%
rename from content/4.guide/9.primevue-theming-guide.md
rename to content/4.guide/6.theming-guide/3.nuxt-with-primevue.md
index 699a2f65..47caf704 100644
--- a/content/4.guide/9.primevue-theming-guide.md
+++ b/content/4.guide/6.theming-guide/3.nuxt-with-primevue.md
@@ -1,9 +1,9 @@
---
toc: true
-title: PrimeVue Theming Guide
+title: Nuxt with Primevue
---
-## Introduction
+## Theming with PrimeVue
This guide outlines a structured approach to applying theming in Vue and Nuxt apps using **CSS custom properties** alongside **Tailwind CSS** and **PrimeVue**. It helps ensure your application is both performant and maintainable with scalable light and dark modes.
@@ -13,7 +13,7 @@ This guide outlines a structured approach to applying theming in Vue and Nuxt ap
- **[Install Tailwind CSS](https://tailwindcss.nuxtjs.org/getting-started/installation){:target="_blank"}**
-## 1. Tailwind Setup
+### 1. Tailwind Setup
Ensure your project includes Tailwind’s base setup:
@@ -23,7 +23,7 @@ Ensure your project includes Tailwind’s base setup:
@tailwind utilities;
```
-## 2. Adding Dark Mode Support
+### 2. Adding Dark Mode Support
PrimeVue uses the `system` as the default `darkModeSelector` in theme configuration. If you have a dark mode switch in your application, set the `darkModeSelector` to the selector you utilize such as `.my-app-dark` in your nuxt config so that PrimeVue can fit in seamlessly with your color scheme.
@@ -62,12 +62,12 @@ theme: {
}
```
-## 3. Defining Light and Dark Themes
+### 3. Defining Light and Dark Themes
Use CSS custom properties (`--var-name`) inside `:root` for light theme and a custom class (e.g., `.my-app-dark`) for dark theme overrides. Add the theming vairables in your css file where tailwind is already setup.
-### Light Theme
+#### Light Theme
```css
:root {
@@ -101,7 +101,7 @@ Use CSS custom properties (`--var-name`) inside `:root` for light theme and a cu
}
```
-### Dark Theme
+#### Dark Theme
```css
:root.my-app-dark {
@@ -133,11 +133,11 @@ Use CSS custom properties (`--var-name`) inside `:root` for light theme and a cu
---
-## 3. Using CSS Variables with Tailwind CSS
+### 3. Using CSS Variables with Tailwind CSS
While Tailwind doesn’t directly support variables in all utilities, **arbitrary values** allow us to use CSS variables in most cases:
-### Practical Examples
+#### Practical Examples
```html
@@ -158,7 +158,7 @@ While Tailwind doesn’t directly support variables in all utilities, **arbitrar
> ⚠️ Gradients and background images must be applied using `bg-[image:var(--bg-circle-subtle)]` to render properly.
-## 4. Switching Between Light and Dark Themes
+### 4. Switching Between Light and Dark Themes
Following is a very basic example implementation of a dark mode switch, you may extend it further by involving `prefers-color-scheme` to retrieve it from the system initially and use `localStorage` to make it stateful. See this [article](https://dev.to/abbeyperini/dark-mode-toggle-and-prefers-color-scheme-4f3m){:target="_blank"} for more information.
@@ -174,7 +174,7 @@ function toggleDarkMode() {
```
-## 5. Naming Best Practices
+### 5. Naming Best Practices
To keep your styles scalable:
@@ -195,12 +195,3 @@ To keep your styles scalable:
| `--gradient-5` | `--bg-circle-spotlight` |
---
-
-## Final Notes
-
-* Use variables for colors, backgrounds, gradients, and even shadows.
-* Combine Tailwind's arbitrary values with semantic CSS variables.
-* Maintain consistent naming across light/dark modes.
-* Document each variable clearly to help future developers.
-
-A scalable theming approach will improve maintainability, accessibility, and performance across your Vue or Nuxt projects.
diff --git a/content/4.guide/6.theming-guide/4.primevue-optimizations.md b/content/4.guide/6.theming-guide/4.primevue-optimizations.md
new file mode 100644
index 00000000..2a38ea57
--- /dev/null
+++ b/content/4.guide/6.theming-guide/4.primevue-optimizations.md
@@ -0,0 +1,51 @@
+---
+toc: true
+title: Primevue Optimizations
+---
+
+## Optimization
+
+Reduce bundle size through the following optimizations:
+
+#### 1. Turn off primevue's `autoImport` option
+
+```js
+primevue: {
+ autoImport: false,
+}
+```
+
+#### 2. components
+
+When `autoImport` is disabled, use the `include` and `exclude` for manual registration.
+
+The components to import and register are defined with the `include` option using a string array. When the value is ignored or set using the `*` alias, all of the components are registered.
+
+```js
+primevue: {
+ components: {
+ include: ['Button', 'DataTable']
+ }
+}
+```
+
+In case all components are imported, particular components can still be excluded with the exclude option.
+
+```js
+primevue: {
+ components: {
+ include: '*',
+ exclude: ['Galleria', 'Carousel']
+ }
+}
+```
+
+By default, for compatibility reasons, Chart and Editor components are excluded. To include them simply set the `exclude` option to an empty list.
+
+```js
+primevue: {
+ components: {
+ exclude: []
+ }
+}
+```
\ No newline at end of file
diff --git a/content/4.guide/7.FFMPEG-Video-Generation-Tool/1.introduction-and-installation.md b/content/4.guide/7.FFMPEG-Video-Generation-Tool/1.introduction-and-installation.md
new file mode 100644
index 00000000..54e43a86
--- /dev/null
+++ b/content/4.guide/7.FFMPEG-Video-Generation-Tool/1.introduction-and-installation.md
@@ -0,0 +1,101 @@
+---
+toc: true
+title: Introduction and Installation
+---
+
+## What is FFmpeg?
+
+[FFmpeg](https://ffmpeg.org/) is a **powerful open-source multimedia framework** used to record, convert, and stream audio and video. It works via command line and supports **a wide range of formats**, making it one of the most versatile tools for video and audio processing.
+
+FFmpeg can handle almost anything related to media:
+- Converting image sequences into videos
+- Extracting or merging audio and video
+- Compressing large media files without losing quality
+- Supporting transparency and advanced encoding options
+- Widely used in web apps, media servers, and streaming platforms
+
+## Why Use FFmpeg?
+
+- **Cross-platform** — works on Windows, macOS, and Linux.
+- **Lightweight & Fast** — no GUI required, pure CLI power.
+- **Supports transparency** (WebM, MOV, etc.) for use in modern websites.
+- **Free & Open Source** — no licensing cost.
+- **Highly customizable** for professional and web development workflows.
+
+With FFmpeg, you can automate media workflows, optimize assets for websites, or create complex media processing pipelines — all from your terminal.
+
+
+## FFmpeg Installation and Setup (Windows)
+
+This guide explains how to **install FFmpeg**, **set up environment variables**, and **verify the installation** so that you can use `ffmpeg` from anywhere in the terminal or Command Prompt.
+
+---
+
+
+## 1. Prerequisites
+
+Before you begin, make sure you have:
+
+- A Windows system (Windows 10 or higher recommended)
+- Internet connection
+- Administrator access (to edit system variables)
+
+---
+
+## 2. Download FFmpeg
+
+1. Go to the official build site [https://www.gyan.dev/ffmpeg/builds](https://www.gyan.dev/ffmpeg/builds)
+2. Scroll down to **“Release Builds”**
+3. Click and download the file:
+
+Example: `ffmpeg-8.0-full_build.zip`
+
+---
+
+
+## 3. Extract FFmpeg
+
+1. Right-click on the downloaded `.zip` file
+2. Select **“Extract All”**
+3. Choose a location to extract (for example): `C:\ffmpeg`
+4. After extracting, the folder structure will look like: `C:\ffmpeg\ffmpeg-8.0-full_build\bin`
+
+
+> 💡 **Note:** The `bin` folder contains the actual `ffmpeg.exe` file. That’s what we’ll add to the environment variables next.
+
+---
+
+## 4. Set Environment Variables
+
+To use FFmpeg globally in Command Prompt or PowerShell, we need to **add it to the system PATH**.
+
+### Steps:
+
+1. Press **Win + R** → type `sysdm.cpl` → hit **Enter**
+2. Go to **“Advanced”** tab → click **“Environment Variables…”**
+3. Under **“System variables”**, select **`Path`** → click **Edit**
+4. Click **New** → paste the `bin` folder path: `C:\ffmpeg\ffmpeg-8.0-full_build\bin`
+5. Click **OK** on all windows to save the changes
+
+---
+
+## 5. Verify FFmpeg Installation
+
+1. Open **Command Prompt** or **PowerShell**
+2. Type:
+```
+ffmpeg -version
+```
+
+3. If everything is correct, you’ll see output similar to:
+```
+ffmpeg version 8.0 ...
+configuration: ...
+libavcodec ...
+```
+
+âś… This confirms FFmpeg is installed and accessible from anywhere.
+
+
+
+
\ No newline at end of file
diff --git a/content/4.guide/7.FFMPEG-Video-Generation-Tool/2.usage.md b/content/4.guide/7.FFMPEG-Video-Generation-Tool/2.usage.md
new file mode 100644
index 00000000..55949098
--- /dev/null
+++ b/content/4.guide/7.FFMPEG-Video-Generation-Tool/2.usage.md
@@ -0,0 +1,239 @@
+---
+title: Usage
+toc: true
+---
+
+## FFmpeg Usage and Requirements
+
+Once FFmpeg is installed and added to your system PATH, you can start using it directly from **Command Prompt** or **PowerShell** to create videos from image sequences.
+
+This section explains:
+
+- File & naming requirements
+- Basic usage to generate videos
+- Transparent background support
+- Compression and optimization tips
+- Using the generated video on a website
+
+---
+
+## 1. Requirements Before Using FFmpeg
+
+Before running commands, make sure:
+
+- FFmpeg is installed and working (`ffmpeg -version`)
+- All PNG images are in **one folder**
+- Filenames are **sequentially numbered**, for example:
+```
+frame00001.png
+frame00002.png
+frame00003.png
+...
+```
+
+
+> ⚠️ **Important:** FFmpeg uses sequential numbers to combine images in the correct order.
+
+---
+
+## 2. Navigate to the Image Folder
+
+Open **Command Prompt** and navigate to your image folder:
+
+```
+cd C:\path\to\your\images
+```
+
+For example:
+
+```
+cd C:\Users\Parth\Desktop\PNGSequence
+```
+
+This ensures FFmpeg can find the image sequence easily.
+
+
+## 3. Creating a Basic MP4 Video
+
+Use the following command to convert PNG sequence to MP4 (non-transparent):
+
+```
+ffmpeg -framerate 30 -i frame%05d.png -c:v libx264 -pix_fmt yuv420p output.mp4
+```
+
+### What this command means:
+
+| Option | Description |
+| ------------------ | -------------------------------------------------- |
+| `-framerate 30` | Sets 30 FPS |
+| `-i frame%05d.png` | Reads files like frame00001.png, frame00002.png... |
+| `-c:v libx264` | Uses H.264 codec |
+| `-pix_fmt yuv420p` | Makes it browser-compatible |
+| `output.mp4` | Output filename |
+
+
+### Understanding `frame%05d.png`
+
+When creating a video from an image sequence, FFmpeg uses a **filename pattern** to read the images in the correct order.
+
+`frame%05d.png` is an example of that pattern.
+
+- **`frame`** → The base filename (can be changed to anything, e.g., `image`, `shot`, `animation`, etc.).
+- **`%05d`** → A placeholder for numbers:
+ - `%d` inserts a number.
+ - `05` means the number will be **5 digits long**, padded with zeros if needed.
+ - Example: `00001`, `00002`, `00003`, …
+- **`.png`** → The image file extension.
+
+#### Example:
+If your images are named:
+
+frame00001.png
+frame00002.png
+frame00003.png
+
+The command would be:
+```cmd
+ffmpeg -framerate 30 -i frame%05d.png output.mp4
+```
+
+FFmpeg will detect and read the images in sequence, creating a smooth video.
+
+🪄 Tip:
+
+- %03d → 3 digits (e.g., 001, 002)
+
+- %04d → 4 digits (e.g., 0001, 0002)
+
+- %05d → 5 digits (e.g., 00001, 00002)
+
+âś… Important:
+The base filename (like frame) is fully customizable. For example:
+
+```cmd
+ffmpeg -framerate 30 -i image%05d.png output.mp4
+```
+
+will work if your files are named image00001.png, image00002.png, etc.
+
+This gives you flexibility to match your file naming convention.
+
+
+
+âś… MP4 is widely supported, but does not support transparency.
+
+## 4. Creating a Transparent Background Video (WebM)
+
+If your PNGs have transparency, use WebM with VP9 codec:
+
+```
+ffmpeg -framerate 30 -i frame%05d.png -c:v libvpx-vp9 -pix_fmt yuva420p -auto-alt-ref 0 -crf 15 output.webm
+```
+
+| Option | Description |
+| ------------------- | ----------------------------- |
+| `libvpx-vp9` | VP9 codec that supports alpha |
+| `-pix_fmt yuva420p` | Keeps transparency |
+| `-auto-alt-ref 0` | Required for alpha channel |
+| `-crf 15` | High quality (lower = better) |
+
+🟢 WebM is the best option for transparent looping animations on websites.
+
+## 5. Optional: MOV with ProRes 4444 (For Editing Software)
+
+If you're working with editing software (e.g., After Effects or Premiere Pro), you can export transparent .mov:
+
+```
+ffmpeg -framerate 30 -i frame%05d.png -c:v prores_ks -profile:v 4444 -pix_fmt yuva444p10le output.mov
+```
+
+đź’ˇ MOV supports alpha channel but is heavier than WebM.
+
+## 6. Controlling Quality with CRF
+
+CRF (Constant Rate Factor) controls quality vs. file size.
+
+| CRF Value | Quality | File Size |
+| --------- | --------- | --------- |
+| 10–15 | Very High | Large |
+| 18–25 | Good | Balanced |
+| 30+ | Low | Small |
+
+Example:
+
+```
+ffmpeg -framerate 30 -i frame%05d.png -c:v libvpx-vp9 -pix_fmt yuva420p -crf 25 -auto-alt-ref 0 output.webm
+```
+
+📌 Lower CRF = better quality but bigger file.
+📌 Higher CRF = smaller file but lower quality.
+
+## 7. Optimizing File Size
+
+To reduce file size without ruining quality, try these options:
+
+### 1. Lower Frame Rate
+
+```
+-framerate 15
+```
+
+### 2. Scale Down Resolution
+
+```
+-vf "scale=640:-1"
+```
+
+### 3. Limit Duration
+
+```
+-t 5
+```
+
+### Example:
+
+```
+ffmpeg -framerate 15 -i frame%05d.png -vf "scale=640:-1" -c:v libvpx-vp9 -pix_fmt yuva420p -crf 25 -auto-alt-ref 0 output.webm
+```
+
+## 8. Using the Video on a Website
+
+To support most browsers:
+
+ - Use WebM (transparent) as the primary source
+ - Use MP4 (non-transparent) as a fallback for Safari / iOS
+
+### Example HTML:
+
+```html
+
+```
+
+âś… Works smoothly on modern browsers
+âś… Supports transparency in Chrome, Edge, Firefox
+❌ Safari currently does not support WebM alpha
+
+## 9. Common Errors & Fixes
+
+| Problem | Cause | Fix |
+| ------------------------ | ---------------------------- | ---------------------- |
+| `ffmpeg` not recognized | Environment variable not set | Recheck PATH |
+| Black background | MP4 format used | Use WebM with VP9 |
+| Output is pixelated | CRF too high | Lower CRF value |
+| Wrong order of frames | Filenames not sequential | Rename files correctly |
+| Playback issue in Safari | No WebM support | Add MP4 fallback |
+
+
+## 10. Recommended Settings for Web Use
+
+| Setting | Recommended |
+| ------------ | ----------------------------- |
+| Format | WebM (VP9) |
+| Frame Rate | 24–30 FPS |
+| CRF | 15–25 |
+| Resolution | ≤ 1080p |
+| Transparency | `yuva420p` pixel format |
+| Looping | `