Skip to content

Comments

feat: .NET Staff Augmentation page — final refinements#120

Open
harshita375 wants to merge 1 commit intomainfrom
dotnet-staff-aug-refinements
Open

feat: .NET Staff Augmentation page — final refinements#120
harshita375 wants to merge 1 commit intomainfrom
dotnet-staff-aug-refinements

Conversation

@harshita375
Copy link
Collaborator

Summary

Comprehensive refinements to the .NET Staff Augmentation page (/technologies/dotnet/staff-augmentation) for keyword optimization, pricing transparency, and internal linking.

H2 keyword optimization:

  • "What Our .NET Staff Augmentation Includes" → "What You Get with .NET Staff Augmentation"
  • ".NET Skills Available Through Staff Augmentation" → "Senior .NET Developer Skills & Experience Levels"
  • "Why Engineering Teams Choose .NET Staff Augmentation" → "When Does .NET Staff Augmentation Make Sense?"

Copy updates (Procedure branding & specificity):

  • "Senior Engineers Only" card: added "minimum of 5 years of production experience" language
  • Step 02 "Candidate Matching": added "from Procedure's engineering team"
  • "Same Timezone Collaboration": "teams in India" → "engineering teams in Mumbai and San Francisco"
  • "Production Experience": "Our" → "Procedure's"
  • Problem intro subtitle: "Staff augmentation" → "Procedure's staff augmentation"

New content:

  • 3 new FAQs: staff aug vs outsourcing, short-term projects (<3 months), typical engagement duration
  • Detailed pricing in rates FAQ ($30-$65/hr breakdown with engagement model context)
  • Typical duration lines on each engagement model card (3-6mo, 4-12mo, 6-18mo)
  • New comparison table section: "Staff Augmentation vs Full-Time Hiring: What Makes Sense?"

Internal linking:

  • Created renderLinkedText utility for markdown-style [text](url) in data strings
  • ASP.NET Core → /technologies/dotnet/
  • legacy .NET Framework / modernize to .NET 8 → /technologies/dotnet/modernization
  • Azure or cloud-native → /services/cloud
  • payment systems / fintech → /industries/financial-services
  • "Talk to our team" in rates FAQ → /contact-us

SEO:

  • Meta title updated: "Procedure" → "Procedure.tech"

Test plan

  • Verify all H2 headings render with updated text
  • Verify "Senior Engineers Only" card shows new copy
  • Verify 3 new FAQs appear in accordion (after modernization FAQ)
  • Verify rates FAQ shows pricing details with clickable "Talk to our team" link
  • Verify typical duration lines appear on engagement model cards
  • Verify comparison table renders between Engagement Models and CTA sections
  • Verify internal links are clickable and navigate to correct pages
  • Verify browser tab shows "Procedure.tech" in title

🤖 Generated with Claude Code

…, comparison table, internal links

- Optimize H2 headings for target keywords (What You Get, Senior .NET Developer Skills)
- Update section title to "When Does .NET Staff Augmentation Make Sense?"
- Add detailed pricing info ($30-$65/hr) to rates FAQ
- Add 3 new FAQs: staff aug vs outsourcing, short-term projects, engagement duration
- Add comparison table: Staff Augmentation vs Full-Time Hiring
- Add typical duration lines to engagement model cards
- Update copy with Procedure branding (Mumbai/SF offices, Procedure's team)
- Add internal links: ASP.NET Core, .NET modernization, cloud services, fintech
- Update meta title to Procedure.tech

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@cloudflare-workers-and-pages
Copy link

Deploying website with  Cloudflare Pages  Cloudflare Pages

Latest commit: 9b68a27
Status: ✅  Deploy successful!
Preview URL: https://72328f7d.website-yiq.pages.dev
Branch Preview URL: https://dotnet-staff-aug-refinements.website-yiq.pages.dev

View logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant