List of documentation problems
See original GitHub issueThis is a special issue for collecting minor errors, conflicts, inconsistencies etc. in the documentation that may not have merit to become their own issue/task. The errors, since small, can be fixed as part of other tasks.
After fixing an item on the list, check the checkbox and add the PR number of the change containing the fix after the item title/description.
Not done ( to be completed independently )
Fixed Problems
- Registering bundles #995
- Missing step:
porter build
needs to be run before runningpublish_register_bundle.sh
script - The API for registering bundles is different than what is shown in the docs
- Several typos/grammar mistakes
- Missing step:
- JSON schema for base workspace creation is wrong (see Guy’s comment below) #995
- Swagger UI screenshot for
/api/workspace-template
is not up to date (see Guy’s comment below) #995 - Guacamole image tag environment variable is missing in the docs at Guacamole workspace-service (see Guy’s comment below) #995
- Example of a fixed item #370
- Consider moving all TRE Developer centric docs into the source tree (away from /docs), for example
testing.md
. - E2E tests
.env.sample
containsSCOPE
, but the variable is not documented intesting.md
#844 - E2E app registration API permissions need to have Granted for [directory name] status, which is not documented in
auth.md
#844 -
deployment-quickstart.md
andmanual-deployment.md
contain way too much duplicate information - this will result in outdated, confusing and possibly conflicting documentation - E2E tests README lacks prerequisites
- Remove logical-data-model from docs folder
- Remove Index.md and move repo structure to the readme.md in the root
- Move API and resource processor from Azure TRE Overview/composition service to TRE Developers
- Do a pass through the docs for a readability and consistency - what do we mark as ticks, what do we mark as bold, what is uppercase etc.
- Remove the Developer Guide - everything is covered elsewhere
- Rename Development Environment to Developer Guide
- Change hcl to terraform everywhere in code quotes for proper code highlighting (ex. firewall rules)
- Paths in InnerEye workspace service docs’ build and install step are wrong: should be
./templates/workspace_services/innereye
, not./templates/workspace_services/innereye_deeplearning
#989 - The redirect URLs (2 in
auth.md
and 1 inpre-deployment-steps.md
) all differ and none of them look correct - Setup Instructions - Installing Base Workspace: #989
- The first command
register-bundle DIR=./templates/workspaces/base
is wrong - The Swagger UI URL is wrong
- The first command
- Internal links from workspace/workspace services broken e.g., prerequisites link at https://microsoft.github.io/AzureTRE/tre-templates/workspace-services/inner-eye/ #989
- Auth docs should explain what “admin consent” is and what it means #989
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top Results From Across the Web
8 Project Documentation Challenges You Need to ... - Scribe
8 project documentation management challenges you need to know · 1. Unauthorized content changes · 2. Lack of accessibility · 3. Unauthorized ...
Read more >Eight Common Issues Managing Project Documentation
Eight Common Issues Managing Project Documentation · Incorrect Template Usage · Unauthorized Content Changes · Information Omission · Incorrect ...
Read more >Enhancing problem list documentation in electronic health ...
In this paper, we explore the synergy of these two strategies, targeting the problem of procedure documentation for patients with a history of...
Read more >Problem List Guidance in the EHR - AHIMA Body of Knowledge
Major challenges associated with managing problem lists include policy development, policy compliance, and difficulty maintaining an accurate, current, ...
Read more >Improving Documentation of Inpatient Problem List ... - PubMed
Background: The problem list is critical in electronic documentation. It is a powerful tool for clinical decision-making because it provides ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
GUACAMOLE_IMAGE_TAG is missing in the docs: https://github.com/microsoft/AzureTRE/blob/develop/docs/tre-templates/workspace-services/guacamole.md
screenshot for /api/workspace-template swagger ui is not up to date, it should be “Register Workspace Template” and not “Create Workspace Template”