Merge branch 'dev' of github.com:royalgarter/feathernote into dev

Author: djinni-hppro

.github/workflows/deploy.yml

@@ -0,0 +1,41 @@
+name: Deploy
+on:
+  push:
+    branches: alpine
+  pull_request:
+    branches: alpine
+
+jobs:
+  deploy:
+    name: Deploy
+    runs-on: ubuntu-latest
+
+    permissions:
+      id-token: write # Needed for auth with Deno Deploy
+      contents: read # Needed to clone the repository
+
+    steps:
+      - name: Clone repository
+        uses: actions/checkout@v4
+
+      - name: Install Deno
+        uses: denoland/setup-deno@v2
+        with:
+          deno-version: v2.x
+
+      - name: Install Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: lts/*
+
+      - name: Install step
+        run: "npm install"
+
+      - name: Upload to Deno Deploy
+        uses: denoland/deployctl@v1
+        with:
+          project: "feathernote"
+          entrypoint: "src/server.js"
+          root: ""
+          
+          

.gitignore

@@ -40,6 +40,9 @@ next-env.d.ts
 .genkit/*
 .env*
 
+package-lock.json
+
 # firebase
 firebase-debug.log
-firestore-debug.log
+firestore-debug.log
+src/published_notes/*.json

.idx/icon.svg

@@ -0,0 +1,42 @@
+# Gemini Guidelines
+
+## Development Workflow
+
+-   **Plan First:** Before implementing, draft a plan in `docs/<feature_name>.md`.
+-   **Iterate:** Implement changes step-by-step. Avoid large, sweeping modifications.
+-   **Preserve Code:** When removing code, comment it out with a `DEPRECATED` notice instead of deleting it outright.
+
+## Core Principles
+
+-   **Simplicity & Readability:** Write simple, straightforward, and easy-to-understand code.
+-   **Performance:** Consider performance without sacrificing readability.
+-   **Maintainability & Testability:** Write code that is easy to update and test.
+-   **Reusability:** Create reusable components and functions.
+-   **Minimalism:** Less code is less debt. Keep the footprint small.
+-   **Clarification & Specificity:** Ask for more details and provide open-ended suggestions if the request is ambiguous.
+
+## Best Practices
+
+-   **Vanilla JavaScript First:** Avoid introducing new frameworks (e.g., React, Vue) or large libraries (e.g., jQuery).
+-   **Leverage Alpine.js:** Use the existing `mainApp` data object for UI logic and state.
+-   **Global Scope Awareness:** All JavaScript is loaded via `<script>` tags; be mindful of the global scope.
+-   **Functional Style:** Prefer functional, immutable, and stateless approaches where they improve clarity.
+-   **Early Returns:** Use early returns to avoid nested conditions.
+-   **Descriptive Naming:** Use clear names for variables and functions (e.g., `handle` prefix for handlers).
+-   **Constants:** Use constants instead of functions where possible.
+-   **DRY (Don't Repeat Yourself):** Avoid code duplication.
+-   **Minimal Changes:** Only modify code relevant to the current task.
+-   **TODOs:** Mark issues in existing code with a `TODO:` prefix.
+-   **Clean Logic:** Keep core logic clean and push implementation details to the edges.
+
+## Formatting
+
+-   **Indentation:** Use tabs.
+-   **Semicolons:** Always use semicolons.
+-   **Braces:** Use One True Brace Style (1TBS).
+
+## Naming Conventions
+
+-   **camelCase:** For variables and functions (e.g., `noteEditorVisible`, `fetchNotes`).
+-   **UPPER_SNAKE_CASE:** For constants and globals (e.g., `DB_NAME`, `NOTE_STORE`).
+-   **\_prefix:** Consider for internal/private functions (e.g., `_doSomethingInternal`).