feat(website): highlight big orgs / projects that use Task#2803
Open
feat(website): highlight big orgs / projects that use Task#2803
Conversation
Introduces a new /adopters page listing notable OSS projects using Task, along with an infinite-scroll carousel on the homepage linking to it. The adopter list lives in .vitepress/adopters.ts for easy PR-based submissions; contributing docs explain the process.
Reshuffles the adopters list to lead with big brands (Docker, HashiCorp, Microsoft, Vercel, Google Cloud, AWS) followed by high-profile OSS (FerretDB, Tyk, Outline, etc.), so the section reads as strong social proof rather than a niche catalog. Adds website/scripts/find-adopters, a small Go CLI that sidesteps the 1000-result cap on GitHub Code Search by partitioning queries per star bucket (and per pushed-year when a bucket overflows), then enriches every hit via a batched GraphQL call. The result is a ranked TSV/JSON of adopter candidates, filterable by min stars and owner type, that can be rerun periodically to keep the list fresh. Exposed via `task find-adopters` in website/Taskfile.yml.
… tool Runs the refreshed find-adopters tool against every public Taskfile on GitHub (1190 unique repos, 13 min) and uses the findings to swap in four higher-signal entries: Azure/Azure-Sentinel replaces Microsoft's niche Fabric provider, flet-dev/flet (16k stars, #1 non-Task hit), Anthropic's Rust protobuf, and charmbracelet/glamour join the list. Gogs drops out since it no longer surfaces in the best-match slice GitHub exposes. Rewrites the discovery strategy: GitHub Code Search caps at 1000 results per query and its size: qualifier turned out unreliable (non-monotone total_count, sporadic 404s), so the tool now paginates each of the four Taskfile variants to the cap and supplements with an org: scan over ~100 curated organizations. That's the practical ceiling without GH Archive or BigQuery, and it captures every big-brand hit we care about. Also drops the code-search rate from 24 to 8.5 req/min to match the real 10 req/min authenticated limit.
… repo Drops the dedicated /adopters page, its Vue component, the navbar entry, the sidebar hack, and the contributing-guide section. The homepage carousel already carries the social-proof signal — a separate page attracted virtually no traffic on comparable OSS sites and added maintenance surface without a clear payoff. Also removes the "See all" CTA from the carousel header now that there is nowhere to send visitors to, and centers the remaining label. The find-adopters Go tool moves out of the repo (to ../find-adopters/) — it was always a one-off analysis helper, not code that ships with Task. The adopters.ts file remains the submission surface for anyone motivated enough to PR a new entry.
Promotes the carousel label from <p> to <h2>, links the section to the heading via aria-labelledby, adds an accessible label per chip, and turns the opaque logo <img> tags into proper lazy-loaded assets with explicit dimensions. Adds a subline naming seven brands (Docker, Microsoft, HashiCorp, Vercel, Google Cloud, AWS, Anthropic) so the homepage now has indexable text referencing actual adopters — previously the brand information only lived inside animated chips. Emits a schema.org ItemList of Organization entities (JSON-LD) on the homepage, which none of the comparable OSS sites (Vite, Biome, Astro, Nx, Turborepo) currently expose — cheap differentiator for rich search results.
Introduces a dedicated adopters page with real indexable content: a ~300-word intro, three featured cards for Docker, Microsoft (Azure Sentinel), and HashiCorp, a grid of the remaining eleven projects, and an FAQ covering production-readiness, enterprise usage, Make comparison, and example discovery. Each entry now carries a factual `description` in adopters.ts, which feeds both the page copy and the structured data — a CollectionPage embedding an ItemList of Organization entities plus a FAQPage schema. None of the five OSS sites we benchmarked (Vite, Biome, Astro, Nx, Turborepo) expose equivalent JSON-LD on their showcase pages, so this is a cheap differentiator for rich search results on "who uses Task", "projects using Task", and similar low-competition queries. The homepage carousel links to the new page via a "See all adopters" pill inside the subline. Page wired into the navbar and the sidebar empty-hack list alongside /donate and /team.
Promotes Vercel to the featured row alongside Docker and HashiCorp — closer to the dev-native audience that lands on taskfile.dev — and moves Microsoft down into the general grid. Updates the homepage carousel subline and the enterprise FAQ answer to reflect the same ordering. Renames the adopters-page Q&A block from "Frequently asked questions" to "Why Task?" to stop it from competing with the real technical FAQ at /docs/faq. The FAQPage JSON-LD schema is kept in place — the schema type doesn't need to match the human-readable heading, and the rich snippets still target production-readiness / enterprise / Make comparison / example queries that the /docs/faq doesn't cover.
The homepage carousel already surfaces /adopters via its "See all adopters" link, so keeping the navbar entry was just making the header heavier without meaningful extra discoverability. Google downweights nav-boilerplate internal links anyway, so the SEO hit is minimal — sitemap + homepage link cover crawling.
Swaps em-dashes for commas (or parentheses for the one comment) across the adopters descriptions, page intro, and meta description, per project preference.
vmaerten
changed the title
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.
No description provided.