feat: .NET Technology Page — Final Refinements#119
Open
harshita375 wants to merge 10 commits intomainfrom
Open
feat: .NET Technology Page — Final Refinements#119harshita375 wants to merge 10 commits intomainfrom
harshita375 wants to merge 10 commits intomainfrom
Conversation
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Change headline from duplicate "AI Engineering Services" to "Enterprise AI Engineering" - Reword AI Application Development capability to avoid overlap with use cases - Add useCasesSubtitle field support for customizable section subtitles - Rewrite use case descriptions with specific, value-driven copy - Update FAQ answers with varied openings and technical depth (RAG, fine-tuning, guardrails) - Rewrite markdown CTA section to address prototype-to-production gap Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add new .NET Development page with enterprise-focused content - Create new components: ArchitectureSection, EngagementModels, ExpertiseCTAWithTestimonial, PhilosophySection, RiskReversal - Update TechStack with grouped chips variant - Update WhoWeWorkWith with tabs variant and 2-column bullet list - Add split layout variant to RiskReversal component - Update Stats component to accept custom stats props - Add supporting content types for new page sections - Include 7 SEO-optimized FAQs with mid-length answers Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
…d content updates - Add HowItWorks timeline component with 5-step engagement flow - Add LinkedText utility for parsing markdown links in frontmatter strings - Add internal links across capabilities, tech stack, and common applications - Update H2 headings for better SEO and branding - Fix hero to show single paragraph (tagline only) for dotnet page - Add Stats subtitle with intro paragraph - Update FAQ #1 with leading summary sentence - Add team size detail to Dedicated .NET Team engagement model - Update meta title for SEO - Remove all em dashes from dotnet page content - Add subtitle prop to Stats component Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add howItWorks, philosophy, and riskReversal split-variant fields to ExpertiseFrontmatter in content-types.ts. Add philosophy mapping in content.ts. Fixes Cloudflare Pages build failure. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…ation-Page-Final-Refinement # Conflicts: # app/services/[slug]/ExpertisePageClient.tsx # components/expertise/ArchitectureSection.tsx # components/expertise/CapabilitiesGrid.tsx # components/expertise/EngagementModels.tsx # components/expertise/ExpertiseCTAWithTestimonial.tsx # components/expertise/ExpertiseHero.tsx # components/expertise/PhilosophySection.tsx # components/expertise/RiskReversal.tsx # components/expertise/TechStack.tsx # components/expertise/WhoWeWorkWith.tsx # components/expertise/WhyChooseProcedure.tsx # components/expertise/index.ts # components/sections/Stats.tsx # content/services/ai-agents.mdx # content/services/ai-engineering.mdx # lib/content-types.ts # lib/content.ts
…d content updates Apply all refinements to the correct /technologies/dotnet page after merging main. Adds How It Works section, inline links to related services/industries, updated Stats/CapabilitiesGrid/TechStack titles, FAQ improvements, engagement model detail, and SEO meta updates. Removes duplicate /services/ dotnet pages. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Deploying website with
|
| Latest commit: |
5f26f6a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://07a3867f.website-yiq.pages.dev |
| Branch Preview URL: | https://dot-net-staff-augmentation-p.website-yiq.pages.dev |
harshita375
force-pushed
the
Dot-Net-Staff-Augmentation-Page-Final-Refinement
branch
from
a679953 to
5f26f6a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Applies all content and component refinements to the correct
/technologies/dotnetpage after syncing with main. Supersedes PR #89 which targeted the old/services/path.Content refinements (dotnet.mdx):
Component enhancements:
HowItWorkscomponent (vertical numbered timeline with Framer Motion animations)LinkedTextcomponent (parses[text](url)markdown into Next.js<Link>)Statswith subtitle prop supportLinkedTexttoCapabilitiesGrid,TechStack(grouped variant), andWhoWeWorkWith(commonApplications)howItWorksandphilosophytypes toExpertiseFrontmatterand content mappingCleanup:
content/services/dotnet-development.mdxTest plan
/technologies/dotnetpage renders with all sections (hero, capabilities, tech stack, how it works, engagement models, risk reversal, FAQ, CTA)/services/dotnet-developmentno longer exists (404)npm run build— TypeScript compilation passesnpm run lint— 0 errors🤖 Generated with Claude Code