Bridges were developed simultaneously with Projectfile Specification as its first consumers.
Damián Búho
Projectfile Bridges
Origin
What it does
- syncronizes your projectfile with dozen of formats: from NPM's package.json and CITATION.cff to Crystal's shard.yaml and browserlistsrc.
- generates config for all the tools that can yet use projectfile directly
- generates READMEs, Code Of Conduct, CONTRIBUTING/SUPPORT/SECURITY.md, AI Policy and many others (with localization)
- pushes metadata to all forges
- keeps everything synced and consistent with single source of truth
What's next
- more bridges (cargo.toml, go.mod)
- better default template for documentation
It's for you if
- if you adopted the Projectfile
- if you have a lot of places where metadata can go inconsistent
- if you have at least one pre-commit hook that rewrites metadata to keep them sane
- if you have huge fleet of projects
It's not for you if
- if you didn't adopt the Projectfile yet