documentation
documentation copied to clipboard
opensafely
Documentation for the OpenSAFELY platform
The "[How to use the OpenSAFELY command-line interface](https://docs.opensafely.org/opensafely-cli/)" page contains a section on JupyterLab. Whilst we don't intend to deprecate `opensafely jupyter`, we should encourage users to work with JupyterLab...
MkDocs 1.6.0 now helpfully checks these, as does lychee, so we should fix those that are broken.
In the Bristol-Cambridge-Oxford meeting on May 2, 2024 @venexia asked a question about keeping Git branches in sync with job-server workspaces. The question was prompted by an exchange with tech...
We're now sponsoring the project, and can use — or at least trial — the Insiders version. - [x] Confirm that the license covers our use. (We believe it does...
We currently install cohortextractor and it's dependencies so we can use automated codegen tooling for pages such as the [variable reference](https://docs.opensafely.org/study-def-variables/). This means the dev tooling is tied to cohortextractor's...
#668 updated most of the DataLab references to Bennett Institute. There are still a few remaining: - [ ] `github.com/ebmdatalab` — needs a GitHub organization rename - [x] #676 -...
This setup doesn't currently work because of possible Windows on ARM and driver problems. See https://github.com/opensafely/documentation/discussions/251 Not sure if there's a workaround.
As mentioned in opensafely-core/ehrql#1815 — there are broken links fixed up there, but the link check currently passes. Not sure why: we should try and figure this out.
Everything is largely placed in one directory, in the case of both images and source files. It might be better to organise these into subdirectories.
This doesn't matter too much for an actual build during deployment, but is inconvenient for local editing. This is primarily due to the use of the multirepo plugin. It takes...