docs: use one headline for pz everywhere - #6
Merged
Conversation
README, CLAUDE.md, the pz NuGet package description, the root command's --help text and the pz-pipelines skill each carried a different one-line description of what pz is -- "dbt-inspired batch ETL CLI for .NET", "lightweight, developer-first engine for batch ETL/ELT", "batch ETL powered by DuckDB". Someone meeting pz through the CLI, nuget.org and the README saw three products. Settle on one sentence: a lightweight, developer-first batch data pipeline engine for SQL-based ETL/ELT, powered by DuckDB, that can run anywhere without requiring a data platform. It names the category (pipeline engine, not a CLI wrapper), the authoring surface (SQL), the runtime (DuckDB) and the deployment claim (no data platform) in the order a reader needs them.
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.
What
pzdescribed itself three different ways depending on where you met it:README.mdCLAUDE.mdpz --helppzNuGet<Description>pz-pipelinesskillAll five now carry the same sentence:
Wording is adapted only for grammar at each site (leading
pz/PipelineZ (pz), the clause that follows). "dbt-inspired" is gone — the comparison invited the wrong expectations and said nothing about what pz does.The NuGet description drops its now-redundant "run it anywhere, with no data platform required" sentence (the headline says it) and keeps the connector list, which is what nuget.org search matches on.
Verification
dotnet build Pz.slnx -c Release— build succeeded, 0 warningsPZ_TESTS_OFFLINE=1 dotnet test Pz.slnx -c Release --no-build— 21 projects, 0 failures (docker suites skip)pz --helprenders the new descriptionFollow-ups (not in this PR)
tests/Pz.Mcp.Tests/DocsToolsTests.cshas "A CLI for batch ETL/ELT." inside a stubllms.txtfixture. It simulates remote site content, not pz's own copy, so it was left alone.