Repository navigation
doc: correct the FAQ contact answer and the Preface language list - #68
Merged
Merged
Conversation
…s page The FAQ said each kit lists its maintainer's contact information at the end. No kit does: no chapter carries an email address or a contact or maintainer statement, and every chapter ends with its Citations section. Point readers at the channels that exist: an issue on this repository for questions about a kit, and the data-access page for questions about the data or about access to it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The book has no python examples: 587 `{r}` chunks and 60 plain bash
fences. The only other mention is the description of PyBIDS in the raw
MRI kit, which is about an external tool and stays.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Contributor
|
The preview for this pull request has been removed. |
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.
Two sentences in the front matter promised things the chapters do not deliver.
FAQ, "Who should I contact?" said that each kit lists its maintainer's contact information at the end, and to use those channels. No kit does: across every
*.qmdthere are no email addresses and no contact or maintainer statements outside the FAQ itself, and every chapter ends with its Citations section. Only six files carry a name-onlyauthors:block (the Psychosocial kit, its imputation appendix, and the four CRF appendices); the MRI and omics kits have none. The answer now points at the two channels that exist: an issue on this repository for questions about a kit, and the data-access page on a2cps.org (already linked from the first FAQ entry) for questions about the data or about access to it.Preface said the examples rely on "shell commands,
R, andpython". The book has 587{r}chunks and 60 plainbashfences, and no python; the only other mention is the description of the PyBIDS package in the raw MRI kit, which is about an external tool and is unchanged. The sentence now says shell commands andR.Neither file contains executable code, so there is no
_freezechange; the preview render is the check that this holds. The prek hooks pass on both files.Not included, for separate consideration:
authors:block per kit, in the shape used by the six files that already have one (it renders as an "Authors" byline under the chapter title). This needs the per-kit maintainer mapping, and each touched chapter with code would need a re-render and a_freezecommit.repo-actions: [issue]in_quarto.yml, which would add a "Report an issue" link to every page and make the FAQ answer discoverable from each kit.🤖 Generated with Claude Code