Repository navigation
docs: add a services page and link it from the home page - #139
Merged
Merged
Conversation
This was referenced Oct 24, 2026
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.
Adds
docs/services.md, a page describing the paid work Artur Shiriev offers around the modern-python stack, and links it from the home page after the stack overview. MkDocs adds it to the nav on its own.The page has four offers:
It shows no prices. The only call to action is email.
The structure follows comparable pages: REVSYS's fixed-scope code review, Evil Martians' habit of tying each service to one of their open-source tools, and Pydantic's enterprise support page, which says up front that the library stays free.
Not on the page on purpose: remote-only, NDA terms, response times, engagement length.
mkdocs build --strictpasses andjust testpasses (175 tests).