Supista Projects Blog Guidelines

These rules apply to every file and article inside this directory. They extend the repository-level AGENTS.md.

Route and content model

Publish the center at /products/supista-projects/blogs
Publish articles as /products/supista-projects/blogs/{numeric-id}-{seo-title-slug}
Keep IDs permanent after publication; never recycle an ID
Add article content to src/supistaProjectsBlog/posts.ts and use the shared templates
Use pagination after every three articles unless research shows a better tested threshold
Connect every article to three genuinely relevant articles with relatedIds

Attribute every article to Durgesh Satyam with the role Founder & CEO, Supista.com
Keep the visible byline and BlogPosting.author structured data aligned
Link the byline and author sameAs data to https://www.linkedin.com/in/durgesh-satyam-71800099/
Write for delivery leaders, PMOs, operations leaders, founders, and functional managers
Lead with the answer, then explain the operating method and practical next action
Prefer evidence-led guidance over product promotion; mention Supista only where the workflow or screenshot adds clarity
Use plain English, active voice, short paragraphs, descriptive H2 headings, and scannable lists
Never invent customer names, results, benchmarks, or statistics
Define specialist terms on first use and keep one search intent per article
Include a concise quick-answer block, three takeaways, four or more substantive sections, and two or more FAQs
Review dates, feature claims, links, and screenshots before changing updatedAt

Keep the SEO title descriptive and concise; include the primary phrase naturally
Keep meta descriptions near 150–160 characters and state the reader outcome
Use exactly one H1; build a logical H2 hierarchy with stable anchor IDs
Put the direct answer and key entities near the beginning of the article
Use descriptive image alt text that explains the visible product context
Add BlogPosting, BreadcrumbList, and matching FAQPage JSON-LD
Keep canonical URLs self-referencing and use absolute production URLs in structured data
Link to the Supista Projects product, blog center, /contact, and related articles
Add every published route to public/sitemap-0.xml; keep next-sitemap.config.js routing rules aligned
Do not stuff keywords, hide copy, repeat boilerplate answers, or create near-duplicate articles

Prefer current Supista Projects screenshots from public/assets/img/screenshots/PMS
Store original editorial assets in public/assets/img/supista-projects/blog
Use licensed-free or generated imagery only; document the source or generation prompt in the delivery note
Do not place essential explanations inside images
Set intrinsic width and height, meaningful alt text, responsive sizes, and lazy loading below the fold
Keep keyboard focus visible, use semantic links and buttons, and use native <details> for FAQs

Confirm the article route returns 200 and the numeric ID matches the data record
Confirm title, description, canonical, social image, dates, and JSON-LD in page source
Check pagination, previous/next metadata, breadcrumbs, table-of-contents anchors, and all related links
Review desktop and mobile screenshots against the existing local server
Run TypeScript or lint checks without starting another server or running a production build