-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial version of ehrQL cheatsheet #2239
Conversation
madwort
commented
Nov 20, 2024
•
edited
Loading
edited
- basics of setting up a file
- list of tables / columns
- condensed version of the existing examples page
- some other function reference bits
Deploying databuilder-docs with Cloudflare Pages
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, some minor comments/questions
patients.date_of_death | ||
``` | ||
|
||
### tpp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if the list of tables/columns is the one place where a link to the reference docs would be useful and not clutter?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, it depends on format - I started with a markdown file like this & had the same thought as you, then I switched to a printed page layout & thought it would be useful, now it's back as a long markdown page it seems less valuable, I'd like to leave it for now & maybe reformat the page to more of the sort of shape that I'd expect from a cheatsheet (the main criteria being that a large proportion of the content is visible simultaneously)