Express server
A persistent server organizes a health endpoint and contact route with CORS middleware.
- Contact request
- Express route
- Required-field checks
- SMTP transport
- JSON response
Portfolio Contact — API Architecture
Express source for Portfolio Contact — API Architecture (opens in a new tab)Serverless source for Portfolio Contact — API Architecture (opens in a new tab)
Source studyBoth implementations are available as source. Email delivery is not demonstrated here.
01 / THE PROBLEM & FOCUSBehind the
Behind the
experience.
Two approaches to a portfolio contact flow: an Express server and a focused serverless handler.
This source study compares an Express contact API with a Vercel-oriented serverless handler. Both accept contact details, validate required fields, configure CORS, and use Nodemailer with environment-based SMTP settings.
Implementation focus
- Contact request and response handling
- Required-field validation and CORS configuration
- SMTP integration through Nodemailer
02 / TECHNICAL & DESIGN DECISIONSThe decisions
The decisions
behind the interface.
01
Define the request
Accept the contact name, email, subject, and message as JSON.
02
Validate the input
Check required fields and return clear success or error responses.
03
Connect email delivery
Configure a Nodemailer transport through environment variables.
From message to response.
Serverless handler
A single exported function handles method checks, preflight responses, validation, and delivery.
- Contact request
- POST / OPTIONS handler
- Required-field checks
- SMTP transport
- JSON response
03 / THE INTERFACE
A closer look.
Actual project screens. Select one to explore the details.
What came out of it.
A paired source study covering request handling, validation, CORS, and environment-based email configuration.
Express source for Portfolio Contact — API Architecture (opens in a new tab)Serverless source for Portfolio Contact — API Architecture (opens in a new tab)
Explore my GitHub profile UP NEXT / 08