Repository navigation
Improve ProfitCtl website demo, branding, and sharing - #67
Merged
Merged
Conversation
|
Linked to Plane Work Item(s) References This comment was auto-generated by Plane |
hudsonaikins
marked this pull request as ready for review
October 3, 2026 00:11
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.
ProfitCtl now shows its real CLI through a repeating browser terminal using a fictional product scenario. Visitors can see increased usage miss a margin target, compare a cheaper route, and inspect the inputs. The homepage and documentation follow the browser’s light or dark preference.
Validation on 92c72d9:
Published at https://profitctl.com through production deployment e4f3ff65-b3dd-4acb-a2c9-3c013b2ddc36. Cloudflare confirms the exact commit. Live home/docs metadata and SVG, PNG, ICO, Apple touch, application icon, and sharing JPEG match the tested build. Automatic Git deployment remains separate from the successful direct upload.
Actual iMessage rendering and Google search indexing were not tested. Existing cached previews may take time to refresh. PR merge requires maintainer approval.