How dsanchezcr/website works
Project Type and Purpose
• This is a Jamstack-style personal website built with Docusaurus (React + MDX) and hosted as an Azure Static Web App.
• It includes a small C# Azure Function in the api folder to handle contact-form email sending.
Main Components
a. Frontend (Static Site)
• Docusaurus framework under src, blog, disney, universal and static asset folders
• React + MDX pages and custom components (.tsx/.js, .css)
• Internationalization data under i18n
b. Backend API
• Azure Function project in api with SendEmail.cs for contact‐form submissions
• host.json configuration
c. Hosting & CDN
• Azure Static Web Apps service (builds and serves the static files)
• Azure Functions runtime for the API endpoint
d. CI/CD Pipeline
• GitHub Actions workflows:
– azure-static-web-apps-delightful-moss for frontend
– api.yml for functions deployment
e. External Services
• Email delivery service (e.g., SendGrid or SMTP) invoked by the Azure Function
Component Relationships & Data Flow
• User’s Browser → HTTP GET → Azure Static Web Apps CDN → serves static HTML/CSS/JS
• Browser (Contact Form) → HTTP POST → /api/SendEmail endpoint → Azure Function → calls external email service → returns status
• GitHub (repo) → on push → GitHub Actions → build & deploy frontend to Static Web Apps and backend to Azure Functions
Architectural Patterns & Principles
• Jamstack: pre-built static assets + client-side hydration
• Microservice for dynamic behavior: single API function for email
• CI/CD: GitOps via GitHub Actions
• Separation of concerns: static content vs. serverless compute
Key Technologies & Frameworks
• Docusaurus (React, MDX)
• TypeScript/JavaScript for UI components
• C# Azure Functions for backend
• Azure Static Web Apps & Azure Functions hosting
• GitHub Actions for CI/CD