Feat/lan page

.env.example

@@ -0,0 +1,11 @@
+# BeEKind Environment Variables Template
+
+# Blockchain Configuration (Future)
+# WEB3_PROVIDER_URL=https://mainnet.infura.io/v3/YOUR_PROJECT_ID
+# CONTRACT_ADDRESS=0x...
+
+# AI Configuration (Future)
+# OPENAI_API_KEY=your_api_key_here
+
+# Render Deployment
+# RENDER_SERVICE_ID=your_service_id

.github/workflows/python-publish.yml

@@ -0,0 +1,23 @@
+name: CI
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Use Node.js
+      uses: actions/setup-node@v4
+      with:
+        node-version: '20'
+        cache: 'npm'
+
+    - name: Install dependencies
+      run: npm install

.gitignore

@@ -1,218 +1,3 @@
-# Byte-compiled / optimized / DLL files
-__pycache__/
-*.py[codz]
-*$py.class
-
-# C extensions
-*.so
-
-# Distribution / packaging
-.Python
-build/
-develop-eggs/
-dist/
-downloads/
-eggs/
-.eggs/
-lib/
-lib64/
-parts/
-sdist/
-var/
-wheels/
-share/python-wheels/
-*.egg-info/
-.installed.cfg
-*.egg
-MANIFEST
-
-# PyInstaller
-#   Usually these files are written by a python script from a template
-#   before PyInstaller builds the exe, so as to inject date/other infos into it.
-*.manifest
-*.spec
-
-# Installer logs
-pip-log.txt
-pip-delete-this-directory.txt
-
-# Unit test / coverage reports
-htmlcov/
-.tox/
-.nox/
-.coverage
-.coverage.*
-.cache
-nosetests.xml
-coverage.xml
-*.cover
-*.py.cover
-.hypothesis/
-.pytest_cache/
-cover/
-
-# Translations
-*.mo
-*.pot
-
-# Django stuff:
+node_modules/
 *.log
-local_settings.py
-db.sqlite3
-db.sqlite3-journal
-
-# Flask stuff:
-instance/
-.webassets-cache
-
-# Scrapy stuff:
-.scrapy
-
-# Sphinx documentation
-docs/_build/
-
-# PyBuilder
-.pybuilder/
-target/
-
-# Jupyter Notebook
-.ipynb_checkpoints
-
-# IPython
-profile_default/
-ipython_config.py
-
-# pyenv
-#   For a library or package, you might want to ignore these files since the code is
-#   intended to run in multiple environments; otherwise, check them in:
-# .python-version
-
-# pipenv
-#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
-#   However, in case of collaboration, if having platform-specific dependencies or dependencies
-#   having no cross-platform support, pipenv may install dependencies that don't work, or not
-#   install all needed dependencies.
-# Pipfile.lock
-
-# UV
-#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
-#   This is especially recommended for binary packages to ensure reproducibility, and is more
-#   commonly ignored for libraries.
-# uv.lock
-
-# poetry
-#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
-#   This is especially recommended for binary packages to ensure reproducibility, and is more
-#   commonly ignored for libraries.
-#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
-# poetry.lock
-# poetry.toml
-
-# pdm
-#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
-#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
-#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
-# pdm.lock
-# pdm.toml
-.pdm-python
-.pdm-build/
-
-# pixi
-#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
-# pixi.lock
-#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
-#   in the .venv directory. It is recommended not to include this directory in version control.
-.pixi
-
-# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
-__pypackages__/
-
-# Celery stuff
-celerybeat-schedule
-celerybeat.pid
-
-# Redis
-*.rdb
-*.aof
-*.pid
-
-# RabbitMQ
-mnesia/
-rabbitmq/
-rabbitmq-data/
-
-# ActiveMQ
-activemq-data/
-
-# SageMath parsed files
-*.sage.py
-
-# Environments
-.env
-.envrc
-.venv
-env/
-venv/
-ENV/
-env.bak/
-venv.bak/
-
-# Spyder project settings
-.spyderproject
-.spyproject
-
-# Rope project settings
-.ropeproject
-
-# mkdocs documentation
-/site
-
-# mypy
-.mypy_cache/
-.dmypy.json
-dmypy.json
-
-# Pyre type checker
-.pyre/
-
-# pytype static type analyzer
-.pytype/
-
-# Cython debug symbols
-cython_debug/
-
-# PyCharm
-#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
-#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
-#   and can be added to the global gitignore or merged into this file.  For a more nuclear
-#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
-# .idea/
-
-# Abstra
-#   Abstra is an AI-powered process automation framework.
-#   Ignore directories containing user credentials, local state, and settings.
-#   Learn more at https://abstra.io/docs
-.abstra/
-
-# Visual Studio Code
-#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
-#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
-#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
-#   you could uncomment the following to ignore the entire vscode folder
-# .vscode/
-# Temporary file for partial code execution
-tempCodeRunnerFile.py
-
-# Ruff stuff:
-.ruff_cache/
-
-# PyPI configuration file
-.pypirc
-
-# Marimo
-marimo/_static/
-marimo/_lsp/
-__marimo__/
-
-# Streamlit
-.streamlit/secrets.toml
+verify_final.js

README.md

@@ -1,2 +1,54 @@
-# BeEKind
-La Nostra Missione Creiamo un ecosistema trasparente e incentivante che permetta ai cittadini di contribuire attivamente al bene comune della propria comunità, utilizzando tecnologie all'avanguardia per garantire trasparenza, efficienza e riconoscimento del valore sociale.
+# 🐝 BeEKind - Il Futuro del Volontariato Digitale
+
+[![Live Demo](https://img.shields.io/badge/Live-Demo-brightgreen?style=for-the-badge)](https://beekind-live-v1.onrender.com)
+
+Unisciti all'iniziativa rivoluzionaria di **TATUMA®** per il Comune di Mozzate. **BeEKind** utilizza Blockchain e Intelligenza Artificiale per costruire insieme il bene comune attraverso un ecosistema trasparente e meritocratico.
+
+---
+
+## 🚀 Visualizza il Sito
+Puoi accedere alla versione live dell'applicazione qui:
+👉 **[https://beekind-live-v1.onrender.com](https://beekind-live-v1.onrender.com)**
+
+---
+
+## ✨ Caratteristiche Principali
+*   **Trasparenza Blockchain**: Ogni azione è registrata in modo immutabile su registro distribuito.
+*   **AI-Powered Matching**: Algoritmi avanzati per abbinare le tue competenze alle necessità della comunità.
+*   **Sistema NFT Reward**: Guadagna Badge digitali (Bronzo, Argento, Oro, Platino) scambiabili e certificati.
+*   **Gamification**: Trasforma il volontariato in un'esperienza coinvolgente con punti VR e livelli.
+*   **Governance Locale**: I volontari di livello Platino partecipano alle decisioni della piattaforma.
+
+## 🛠️ Sviluppo Locale
+
+### Prerequisiti
+*   Node.js (v18 o superiore)
+*   NPM
+
+### Installazione e Avvio
+1.  Clona il repository:
+    ```bash
+    git clone https://github.com/TA2MA-Dev/BeEKind.git
+    ```
+2.  Installa le dipendenze:
+    ```bash
+    npm install
+    ```
+3.  Avvia il server di sviluppo:
+    ```bash
+    npm
+    run start
+    ```
+Il sito sarà accessibile all'indirizzo `http://localhost:3000`.
+
+## 🌐 Tecnologie Utilizzate
+*   **Frontend**: Tailwind CSS, FontAwesome, Chart.js.
+*   **Logic**: Vanilla JavaScript (ES6+).
+*   **Deployment**: Render.
+*   **Assets**: Design personalizzato "HoneyComb" by TATUMA®.
+
+## 👨‍💻 Contatti & Social
+Resta aggiornato sulle ultime novità e unisciti alla nostra community attraverso i link ufficiali presenti nel footer della landing page.
+
+---
+© 2026 **TATUMA®** - Tecnologia per il Bene Comune. Tutti i diritti riservati.