How wendellarnald/fiscalcalendar works
Project type and purpose
• This is a small full-stack web application called “FiscalCalendar.”
• It serves a static frontend (HTML/CSS/JS) that displays fiscal deadlines, and a Go-based backend that exposes those deadlines via an HTTP API endpoint.
File structure
• Top level: README.md plus two main directories:
• frontend/ – static assets (index.html, styles.css, main.js)
• backend/ – Go service (main.go), module files (go.mod, go.sum), data (deadlines.json), and domain model (models/deadline.go)
• The backend likely reads deadlines.json through the Deadline model and exposes them as JSON over HTTP.
• No external database—data is stored in a JSON file under backend/data.
README for additional insights
• Client browser → HTTP GET to Go server → raw JSON data → client renders calendar UI.
Diagramming recommendations
1. Browser → Fetch static assets
2. JS → GET /deadlines API
3. API → Read deadlines.json
4. API → Response JSON → Browser
Essential architectural elements to capture
• Separation of static-asset hosting vs. API logic
• Data-loading path from JSON file through models to HTTP response
• Client-side rendering step