chore: Yeah my first commit

Author: sunib

.github/workflows/deploy.yml

@@ -0,0 +1,35 @@
+name: Deploy to GitHub Pages
+
+on:
+  push:
+    branches: [ main ]
+  workflow_dispatch:
+
+concurrency:
+  group: "pages"
+  cancel-in-progress: true
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout your repository using git
+        uses: actions/checkout@v4
+      - name: Setup Pages
+        uses: actions/configure-pages@v5
+      - name: Install, build, and upload your site
+        uses: withastro/action@v4
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    permissions:
+      pages: write
+      id-token: write
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.gitignore

@@ -0,0 +1,32 @@
+# Node
+node_modules/
+
+# Astro build output
+dist/
+.astro/
+
+# VS Code
+.vscode/
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Logs
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# Env
+.env
+.env.*
+
+# Misc
+*.local
+*.log
+
+# Mac system files
+Icon?
+
+# Windows system files
+Desktop.ini

README.md

@@ -0,0 +1,56 @@
+# Simple Astro Website
+
+This project is a simple website built with [Astro](https://astro.build/), generated by Gemini Code Assist. It demonstrates several best practices for structuring and building modern web applications.
+
+## How to Run This Project
+
+1.  **Install Dependencies**:
+    ```bash
+    npm install
+    ```
+
+2.  **Run the Development Server**:
+    ```bash
+    npm run dev
+    ```
+    This will start a local development server. You can view your site in the browser at the URL provided in your terminal (usually `http://localhost:4321`).
+
+3.  **Build for Production**:
+    ```bash
+    npm run build
+    ```
+    This command builds your site into the `dist/` directory, ready for deployment.
+
+## Best Practices Implemented
+
+Here are some of the best practices used in this project's structure and code:
+
+### 1. Project Structure
+
+The project follows a standard Astro directory structure, which helps keep the code organized and maintainable.
+
+-   `src/`: Contains all of your source code that will be processed by Astro.
+-   `src/pages/`: **File-based Routing**. Every `.astro`, `.md`, or `.js`/`.ts` file in this directory becomes a page on your website. For example, `src/pages/index.astro` is the homepage.
+-   `src/layouts/`: Contains layout components. Layouts are special `.astro` components that wrap page content, providing a consistent structure (like headers, footers, and navigation).
+-   `src/styles/`: A dedicated directory for CSS files. This project uses a `global.css` for site-wide styles.
+-   `public/`: For static assets that don't need to be processed, like `favicon.svg`, images, or fonts. Files here are copied directly to the build output.
+
+### 2. Component-Based Architecture
+
+Astro is a component-based framework. This project uses:
+
+-   **Page Components** (`src/pages/index.astro`): These are responsible for the content of a specific page.
+-   **Layout Components** (`src/layouts/Layout.astro`): These define the reusable HTML shell for pages. The `<slot />` element is a placeholder where the content from the page component is injected. This promotes code reuse and separation of concerns.
+
+### 3. Zero JavaScript by Default
+
+One of Astro's core principles is to ship as little JavaScript as possible. The generated HTML is fully static and interactive elements can be opted into using Astro Islands. This project, being simple, ships 0 KB of client-side JavaScript, making it extremely fast to load.
+
+### 4. Styling
+
+-   **Global Stylesheet**: A `global.css` file is used for base styles, CSS variables (custom properties), and resets. This ensures a consistent look and feel across the entire site.
+-   **Scoped Styles**: While not used in this simple example, Astro supports scoped styling by default. A `<style>` tag inside an `.astro` component will only apply to the HTML elements within that component, preventing CSS conflicts.
+
+### 5. TypeScript Integration
+
+The project is set up with a `tsconfig.json` that extends Astro's base configuration. This provides type safety and improved developer experience with autocompletion and error checking, even within `.astro` files. The `Layout.astro` component uses a TypeScript `interface` to define its expected props.

astro.config.mjs

@@ -0,0 +1,4 @@
+import { defineConfig } from 'astro/config';
+
+// https://astro.build/config
+export default defineConfig({});