Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Minogar28/DIRECTORIO_UDC/llms.txt

Use this file to discover all available pages before exploring further.

Directorio UDC is built on a classic two-tier architecture: a React single-page application handles everything the user sees and interacts with, while a dedicated Express.js REST API manages data access and business logic on the server. The two services are developed and deployed independently, communicating over HTTP, which keeps the presentation layer completely decoupled from the data layer and makes each service easy to develop, test, and scale on its own.

​
Services

​
Frontend — FRONTEND/

The frontend is a React 19 + TypeScript single-page application scaffolded and served by Vite. During development Vite’s built-in dev server starts on port 5173 and provides instant Hot Module Replacement (HMR), so changes to any component or stylesheet appear in the browser without a full page reload. For production, vite build compiles and bundles the application into a set of static assets that can be served by any CDN or static hosting provider.
DetailValue
FrameworkReact 19
LanguageTypeScript
Build toolVite 8
Dev port5173

​
Backend — BACKEND/

The backend is an Express.js 5 HTTP server written in plain JavaScript and run with Node.js. It exposes a REST API that the frontend calls to read and write advisory-space data. The server listens on port 3000 and uses the cors npm package to allow cross-origin requests from the Vite dev server during development.
DetailValue
FrameworkExpress 5
RuntimeNode.js (CommonJS)
API port3000

​
Service Communication

The React SPA runs entirely in the browser and makes HTTP requests to the Express backend to fetch and submit data. Because the Vite dev server (localhost:5173) and the Express API (localhost:3000) run on different ports, the browser treats them as separate origins and would normally block cross-origin requests. To allow this, the backend loads the cors npm package as Express middleware. The following snippet shows the intended setup for index.js: 
const cors = require('cors');
app.use(cors());
With CORS enabled on the backend, the browser permits the frontend to call the API freely during development. In production both services should be co-located behind the same domain, or the CORS configuration should be restricted to the exact frontend URL.

​
Directory Structure

DIRECTORIO_UDC/
├── FRONTEND/
│   ├── public/
│   │   ├── favicon.svg
│   │   └── icons.svg
│   ├── src/
│   │   ├── assets/
│   │   ├── App.tsx
│   │   ├── App.css
│   │   ├── index.css
│   │   └── main.tsx
│   ├── index.html
│   ├── vite.config.ts
│   ├── tsconfig.json
│   └── package.json
└── BACKEND/
    └── package.json

​
Explore Further

Frontend Architecture

React 19, TypeScript, Vite configuration, CSS theming, and the component tree.

Backend Architecture

Express 5, CORS setup, CommonJS module system, and how to start the server.

Build docs developers (and LLMs) love

Get started for freeTalk to us