Repository navigation
feat(web): the page wears GeoSuite's design and favicon - #6
Merged
Merged
Conversation
The hosted Sitemap Builder still had its first look: a dark-blue theme, emoji used as icons and a location-pin favicon, while the hub at tools.trygeosuite.it and its AI Readiness Check had already moved to GeoSuite's design system. Visitors jumping between the free tools landed on what looked like a different site. The page now imports theme.js, copied from TryGeoSuite/geo-toolkit, and follows the hub's structure: the bar header with the free tools link and the language switch, a hero with the crawl form and a short "how it works" panel, the CLI command in a copyable box, results in themed panels (capped and error states carry an icon and text, not color alone) and the hub's closing call to action in place of the old promo box. Light and dark both follow the system setting. The worker serves GeoSuite's official favicon and touch icon as PNG on /favicon.png, /favicon.ico, /apple-touch-icon.png and the old /favicon.svg path, plus the three engine logos the call to action shows. The crawl, the API and the ?url= auto-run are unchanged.
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.
Why
Sitemap Builder still had the first look (dark blue, emoji icons, the pin favicon), while the hub at tools.trygeosuite.it and the AI Readiness Check moved to GeoSuite's design system. One click took visitors from one look to another.
What changes
web/theme.js: copy ofgeo-toolkit/theme.js(tokens, chrome, shared components), kept in step with it.web/page.js: hub-style bar, hero with the form and a "how it works" panel with the npx copy box, results in panels with the generated XML in a code block, and the hub's free-analysis panel. No emoji, no em dash, light and dark; "1 page" now reads in the singular.web/worker.js: GeoSuite's favicon at/favicon.png,/favicon.ico,/apple-touch-icon.pngand the old/favicon.svg; engine logos under/logos/.type=text inputmode=url). API and crawl unchanged.Verified
npm test(16/16) andnpm run lintpass; both languages render scripts that parse.wrangler dev: every route answers 200 with the right type; screenshots desktop light/dark, mobile 390px and real results (example.com, trygeosuite.it with the 40-page cap warning), no horizontal scroll.