feat: Go technology page with final refinements#135
Open
harshita375 wants to merge 8 commits intomainfrom
Open
feat: Go technology page with final refinements#135harshita375 wants to merge 8 commits intomainfrom
harshita375 wants to merge 8 commits intomainfrom
Conversation
…, 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>
… mentions, internal links - Meta title: .NET 8/10 + Procedure.tech branding - Hero: "modern .NET" instead of ".NET 8" - Migration table: added .NET 8 → .NET 10 row + two-stage approach note - Performance card: TechEmpower benchmark attribution - Discovery step: front-loaded pricing ($5K-$15K) + .NET Upgrade Assistant - Pricing FAQ: summary lead sentence + updated tier labels - Strangler Fig card: zero planned downtime claim - Entity mentions: "Procedure" woven into steps 01/03/05 and risk cards - H2s: "Is Your Legacy .NET Framework Holding You Back?" + "How .NET Modernization Works at Procedure" - New FAQ: "Should we migrate to .NET 8, 9, or 10?" - New FAQ: "Should we rewrite or migrate incrementally?" - Compatibility card: .NET Upgrade Assistant + API Portability Analyzer - 6 contextual internal links via renderLinkedText in MigrationPathsTable and TechnicalCapabilities Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…rnal links Update meta title/description, H2 headings, capability card copy with data-backed claims (React Compiler stats, Strangler Fig pattern). Add internal links to Next.js, Angular, Node.js, React Native, and Python pages. Add new FAQs for Vue.js comparison and evaluating React companies. Insert secondary CTA block between services grid and decision framework. Add renderLinkedText support to CapabilitiesGrid, ProcessTimeline, and RelatedExpertise components for markdown link rendering. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add null guard to prevent crash when description fields (e.g. tagline) are undefined in related expertise pages. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
New technology page at /technologies/go targeting "Go development services" and "Golang development company" keywords. Competitor research against Radixweb, MindInventory, Evrone, BairesDev, and Golang.company informed content depth and differentiation strategy. - 6 capabilities (APIs, microservices, cloud-native, concurrency, CLI, migration) - 10 AEO-optimized FAQs with self-contained answers and specific numbers - 18-item tech stack (Go 1.23, Gin, Echo, Fiber, gRPC, K8s, Terraform...) - 3 engagement models (dedicated dev, backend pod, project-based) - 5-step delivery process with realistic timelines - Internal links to backend-development, cloud, kubernetes, nodejs, python - JSON-LD structured data (Service + FAQPage + BreadcrumbList) - Hero config, booking text, mid-page CTA, pricing section - Technologies hub updated with Go page link Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Merge origin/main into go-page-merge-fix branch, resolving conflicts in:
- ExpertisePageClient.tsx: keep main's schema approach + Stats/WhyTechnology sections, add Go to CapabilitiesGrid slug lists
- react/layout.tsx: keep main's updated title ("75+ Clients, 9+ Years")
- CapabilitiesGrid.tsx: keep main's LinkedText component approach
- render-linked-text.tsx: keep main's strict typing
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Update meta title/description for better SEO targeting - Update H2 keywords: "Go Development Services We Build", "Go Technology Stack We Work With", "Work With Our Go Engineers" - Add entity clarity intro statement for AEO/LLM citation - Update Go version 1.23 -> 1.26 (Feb 2026 release) - Trim and strengthen all 6 capability card descriptions with specific benchmarks - Add internal links: Kubernetes, Prometheus, Python, CI/CD (spaced across page, no clustering) - Add secondary CTA "Not Sure If Go Is Right?" between capabilities and process - Update "What you get" first checkmark with Uber reference - Strengthen FAQ 1 with lead sentence and honesty closing - Add 2 new FAQs: Gin vs Echo vs Fiber, developer evaluation process - Replace all em dashes with double hyphens for consistency Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Deploying website with
|
| Latest commit: |
164434f
|
| Status: | 🚫 Build failed. |
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
1 participant
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
/technologies/go(originally from PR feat: Add Go (Golang) technology page #127) with all merge conflicts resolved and final refinements appliedclaude/fervent-swartz) which had merge conflicts with mainWhat's included
Original Go page (from #127)
Final refinements (this PR adds)
/services/devops/in delivery process—replaced with--for consistencyMerge conflict resolution
ExpertisePageClient.tsx: kept main's schema approach + Stats/WhyTechnology, added Go to slug listsreact/layout.tsx: kept main's updated titleCapabilitiesGrid.tsx: kept main's LinkedText componentrender-linked-text.tsx: kept main's strict typingTest plan
/technologies/go/technologieshub🤖 Generated with Claude Code