Expand service pages with clearer customer-facing value messaging#49
Merged
iaretechnician merged 2 commits intoMay 29, 2026
Merged
Conversation
Copilot created this pull request from a session on behalf of
iaretechnician
May 29, 2026 23:50
View session
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
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.
The homepage and core service pages had become too thin to explain why a visitor would need each offering, what problems Runlevel Systems solves, and what outcomes customers can expect. This update rewrites those pages around plain-English problem → solution → result messaging, with concrete examples and clearer service framing.
Homepage
Why People Contact Ussection with common real-world entry points:Dev Partner page
Why People Hire A Dev Partnerto frame the service around project rescue, missing technical capacity, broken builds, publishing blockers, and time constraintsHow We Helpcards covering:Common Situationscards to make the service legible to non-technical buyersHosting page
Who Hosting Is ForandWhat You Getsections to clarify fit and valueMods page
Why Modding Gets ComplicatedWhat We Actually Docards focused on concrete support tasks:<section class="service-section alt"> <div class="container"> <h2>Why People Contact Us</h2> <div class="benefit-grid"> <article class="benefit-item"> <h3>“My server broke after an update.”</h3> <p>We help repair, restore, and reconfigure servers after updates and mod conflicts.</p> </article> </div> </div> </section>