How vikaspoddar25/zentiumtechnologieswebsite works
Zentium is a Salesforce consultancy marketing website. Visitors explore service and industry offerings, company information, case studies, and articles; the primary conversion path is submitting an enquiry or optionally booking through Calendly. Typed files under src/content/ supply the site’s authored material, while route pages and shared sections present it. Contact submissions are handled by an API route and sent through Resend. The index and README support the major content and contact branches; some wiring, including the form’s request to the API, is not shown in the excerpts.
Main entry points: [slug]/page.tsx Service pages · app/page.tsx Home page · [slug]/page.tsx Industry pages · contact/page.tsx Contact page
Components 23
Site routes
- Home page
src/app/page.tsx - Service pages
src/app/services/[slug]/page.tsx - Industry pages
src/app/industries/[slug]/page.tsx - Case study pages
src/app/case-studies/[slug]/page.tsx - Blog pages
src/app/blog/[slug]/page.tsx - Company and legal
src/app/about/page.tsx - Contact page
src/app/contact/page.tsx
Authored content
- Service content
src/content/services.ts - Industry content
src/content/industries.ts - Case study content
src/content/case-studies.ts - Article content
src/content/posts.ts - Company content
src/content/company.ts - Site configuration
src/content/site.ts
Presentation
- Page sections
src/components/sections/company-sections.tsx - Hero and feature sections
src/components/sections/hero.tsx
Contact and SEO
- Enquiry form
src/components/contact/contact-form.tsx - Calendly booking
src/components/contact/calendly.tsx - Contact handler
src/app/api/contact/route.ts - Metadata and SEO
src/lib/seo.ts - Structured data
src/lib/schema.tsx
Other components
- Visitor
- Resend email
- Calendly service
Connections 28
- Visitor → Home page: visits
README.md - Visitor → Service pages: explores
README.md - Visitor → Industry pages: explores
README.md - Visitor → Case study pages: explores
README.md - Visitor → Blog pages: reads
README.md - Visitor → Contact page: starts enquiry
README.md - Home page → Company content: uses
src/app/page.tsx - Home page → Hero and feature sections: renders
src/app/page.tsx - Home page → Page sections: renders
src/app/page.tsx - Service pages → Service content: reads
src/app/services/[slug]/page.tsx - Service pages → Case study content: reads
src/app/services/[slug]/page.tsx - Industry pages → Industry content: reads
src/app/industries/[slug]/page.tsx - Industry pages → Service content: reads
src/app/industries/[slug]/page.tsx - Industry pages → Case study content: reads
src/app/industries/[slug]/page.tsx - Case study pages → Case study content: reads
src/app/case-studies/[slug]/page.tsx - Blog pages → Article content: reads
- Company and legal → Site configuration: reads
src/app/about/page.tsx - Company and legal → Metadata and SEO: builds metadata
src/app/about/page.tsx - Contact page → Enquiry form: renders
src/app/contact/page.tsx - Contact page → Calendly booking: renders
src/app/contact/page.tsx - Contact page → Site configuration: reads
src/app/contact/page.tsx - Enquiry form → Contact handler: submits to
- Contact handler → Resend email: sends enquiry
README.md - Calendly booking → Calendly service: embeds when configured
README.md - Service pages → Metadata and SEO: builds metadata
src/app/services/[slug]/page.tsx - Service pages → Structured data: uses structured data
src/app/services/[slug]/page.tsx - Structured data → Service content: reads offers
src/lib/schema.tsx - Structured data → Site configuration: reads site identity
src/lib/schema.tsx