feat: Node.js technology page final refinements (32 changes)#134
Open
harshita375 wants to merge 6 commits intomainfrom
Open
feat: Node.js technology page final refinements (32 changes)#134harshita375 wants to merge 6 commits intomainfrom
harshita375 wants to merge 6 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>
SEO/AEO optimization, content tightening, and UX improvements for /technologies/nodejs/. Key changes: updated meta tags, replaced generic "Why Node.js" section with buyer-focused content, added framework comparison table, compact Node.js vs alternatives table, tightened process steps, added AEO claims, new FAQs, internal cross-links, and engagement model restructure. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
Changes by file
layout.tsxnodejs.mdxIntroStatement.tsxExpertisePageClient.tsxTechDecisionTable.tsxFrameworkComparison.tsxCustomStackTable.tsxTest plan
/technologies/nodejsrenders correctly with dev server🤖 Generated with Claude Code