Repository navigation
docs: rewrite Phlo Transform blog from first principles - #20
Merged
Merged
Conversation
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.
Summary
Reworks the Phlo Transform blog into a much more complete first-principles series aligned with the v0.1 implementation.
Naming rule
The series now uses Phlo Transform consistently for this product. Phlo is reserved for the wider lakehouse framework and is no longer used as shorthand for Phlo Transform in prose. Literal implementation identifiers such as
phlo-transform,phlo.toml,.phlo/,phlo_main, and crate names remain unchanged.Rewritten
BUILD/SKIP/CACHED, verified cross-environment adoptionCLEAN/REVIEW/UNSUPPORTEDAdded
Index
docs/blog/README.mdnow includes a reading guide, glossary, all 10 posts, and the current v0.1 features reflected across the series.Docs only; no runtime code changes.