546ee8cc22b22e7cc0e8b94d83d56c8229e1d3ba
The blog post page ignored the API entirely and rendered a hardcoded placeholder article, so every published post showed the same invented content regardless of what was stored in the database. Metadata (author, category, date, tags, counts) came from placeholders too. post.body is plain text written from the admin panel, so parse it into paragraphs, h1/h2 headings and lists and render the pieces as text nodes. dangerouslySetInnerHTML is deliberately not used: there is no sanitiser in this app, so injecting author-supplied HTML would be an XSS hole. The body falls back to the excerpt, then to an empty-state message. The cover image now renders only when featured_image holds a real URL; the seeded rows point at via.placeholder.com, so they render nothing rather than a broken or third-party image. Also guard the about-me section: title and description are NULL in the live database, so it now falls back to Persian text, omits the skills grid when there are none, and degrades to a skeleton if the API fails instead of crashing.
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.
Languages
TypeScript
97.5%
JavaScript
1.5%
CSS
1%