docs: fix broken images/links, wrong download workflow, and stale tooling references

README.md

@@ -297,7 +297,7 @@ This diagram depicts how the process works:
 * First, you'll need to create the multi-account config file. Run the following command:
 
 ```bash
-cloudsplaining create-multi-account-config-file \ 
+cloudsplaining create-multi-account-config-file \
     -o multi-account-config.yml
 ```
 
@@ -325,7 +325,7 @@ Using the data above, you can run the following command:
 cloudsplaining scan-multi-account \
     -c multi-account-config.yml \
     --profile scanning-user \
-    --role-name CommonSecurityRole \ 
+    --role-name CommonSecurityRole \
     --output-bucket my-results-bucket
 ```
 

docs/contributing/documentation.md

@@ -20,8 +20,8 @@ python3 -m venv ./venv && source venv/bin/activate
 uv sync --frozen
 
 # Create the HTML files
-make build-docs
-make serve-docs
+just build-docs
+just serve-docs
 
 # The above will open the built documentation in your browser
 ```

docs/contributing/javascript.md

@@ -36,7 +36,7 @@ We've already preconfigured several `npm` commands to be run inside the package.
 # Option 1: npm, as defined in package.json
 npm run serve
 # Option 2: Makefile
-make serve-js
+just serve-js
 ```
 
 You can then access the application over [http://localhost:8080](http://localhost:8080).
@@ -47,7 +47,7 @@ You can then access the application over [http://localhost:8080](http://localhos
 # Option 1: npm, as defined in package.json
 npm run test
 # Option 2: Makefile
-make test-js
+just test-js
 ```
 
 * Build the most updated Javascript bundle
@@ -56,7 +56,7 @@ make test-js
 # Option 1: npm, as defined in package.json
 npm build
 # Option 2: Makefile
-make build-js
+just build-js
 ```
 
 ### Adding new JavaScript utility functions: Checklist

docs/contributing/python.md

@@ -12,26 +12,26 @@ uv sync --frozen
 ```
 
 
-### Makefile
+### Just
 
 * Python commands:
 
 ```bash
 # Set up your local development environment
-make setup-env
+uv sync --frozen
 
 # Auto format and lint the python code with `ruff`
 prek run -a
 
 # Run unit tests with pytest
-make test
+just unit-tests
 ```
 
 * Javascript/UI commands
 
 ```bash
 # Run Javascript unit tests
-make test-js
+just test-js
 
 # Generate the updated Javascript bundle
 make build-js

docs/contributing/report.md

@@ -3,7 +3,7 @@
 To test the report, run the following from the root directory:
 
 ```bash
-make generate-report
+just generate-report
 ```
 
 That will generate the example report, without having to go through the full scan.

docs/contributing/testing.md

@@ -2,21 +2,21 @@
 
 ##  Local Unit Testing and Integration Testing
 
-We highly suggest that you run all the tests before pushing a significant commit. It would be painful to copy/paste all of those lines above - so we’ve compiled a test script in the utils folder.
+We highly suggest that you run all the tests before pushing a significant commit. The [just](https://github.com/casey/just) recipes below are the same ones the GitHub Actions build runs.
 
-Just run this from the root of the repository:
+Run them from the root of the repository:
 
 
 ```bash
 # Run Python unit tests
-make test
+just unit-tests
 
 # Run Javascript unit tests
-make test-js
+just test-js
 
 # Run Python security tests
-make security-test
+just safety-scan
 ```
 
-It will execute all the tests that would normally be run during the GitHub actions build. If you want to see if it will pass the tests in GitHub actions, you can just run that quick command on your machine.
+These execute the tests that run during the GitHub Actions build, so if they pass on your machine the CI test jobs should pass too.
 

docs/index.md

@@ -96,12 +96,12 @@ cloudsplaining scan --exclusions-file exclusions.yml --input-file examples/files
 
 It will create an HTML report like [this](https://opensource.salesforce.com/cloudsplaining/):
 
-> ![](docs/_images/cloudsplaining-report.gif)
+> ![](_images/cloudsplaining-report.gif)
 
 
 It will also create a raw JSON data file:
 
-* `default-iam-results.json`: This contains the raw JSON output of the report. You can use this data file for operating on the scan results for various purposes. For example, you could write a Python script that parses this data and opens up automated JIRA issues or Salesforce Work Items. An example entry is shown below. The full example can be viewed at [examples/files/iam-results-example.json](examples/files/iam-results-example.json)
+* `default-iam-results.json`: This contains the raw JSON output of the report. You can use this data file for operating on the scan results for various purposes. For example, you could write a Python script that parses this data and opens up automated JIRA issues or Salesforce Work Items. An example entry is shown below. The full example can be viewed at [examples/files/iam-results-example.json](https://github.com/salesforce/cloudsplaining/blob/master/examples/files/iam-results-example.json)
 
 ```json
 {
@@ -126,7 +126,7 @@ It will also create a raw JSON data file:
 ```
 
 
-See the [examples/files](examples/files) folder for sample output.
+See the [examples/files](https://github.com/salesforce/cloudsplaining/tree/master/examples/files) folder for sample output.
 
 #### Filtering False Positives
 

docs/report/triage.md

@@ -25,11 +25,11 @@ As such, the tool aims to:
 To recap: you've followed these steps to generate this report:
 
 * Downloaded the Account Authorization details JSON file
-    - `cloudsplaining download --profile default --output default-account-details.json`
+    - `cloudsplaining download --profile default`
 * Generated your custom exclusions file
     - `cloudsplaining create-exclusions-file --output-file exclusions.yml`
 * Scanned the Account authorization details
-    - `cloudsplaining scan --input-file default-account-details.json --exclusions-file exclusions.yml`
+    - `cloudsplaining scan --input-file default.json --exclusions-file exclusions.yml`
     - This generates two files: (1) The single-file HTML report, and (2) The raw JSON data file
 
 ## Triaging workflow

docs/user-guide/overview.md

@@ -14,9 +14,9 @@ You can also specify a custom exclusions file to filter out results that are Fal
 ## Commands
 
 * Download the Account Authorization details JSON file
-    - `cloudsplaining download --profile default --output default-account-details.json`
+    - `cloudsplaining download --profile default`
 * Generate your custom exclusions file
     - `cloudsplaining create-exclusions-file --output-file exclusions.yml`
 * Scan the Account Authorization details
-    - `cloudsplaining scan --input-file default-account-details.json --exclusions-file exclusions.yml`
+    - `cloudsplaining scan --input-file default.json --exclusions-file exclusions.yml`
     - This generates two files: (1) The single-file HTML report, and (2) The raw JSON data file

docs/user-guide/scan-account.md

@@ -10,12 +10,12 @@ cloudsplaining scan --exclusions-file exclusions.yml --input-file examples/files
 
 It will create an HTML report like [this](https://opensource.salesforce.com/cloudsplaining/):
 
-> ![](docs/_images/cloudsplaining-report.gif)
+> ![](../_images/cloudsplaining-report.gif)
 
 
 It will also create a raw JSON data file:
 
-* `default-iam-results.json`: This contains the raw JSON output of the report. You can use this data file for operating on the scan results for various purposes. For example, you could write a Python script that parses this data and opens up automated JIRA issues or Salesforce Work Items. An example entry is shown below. The full example can be viewed at [examples/output/example-authz-details-results.json](examples/files/iam-results-example.json)
+* `default-iam-results.json`: This contains the raw JSON output of the report. You can use this data file for operating on the scan results for various purposes. For example, you could write a Python script that parses this data and opens up automated JIRA issues or Salesforce Work Items. An example entry is shown below. The full example can be viewed at [examples/files/iam-results-example.json](https://github.com/salesforce/cloudsplaining/blob/master/examples/files/iam-results-example.json)
 
 ```json
 {

docs/user-guide/scan-multiple-accounts.md

@@ -12,7 +12,7 @@ This diagram depicts how the process works:
 * First, you'll need to create the multi-account config file. Run the following command:
 
 ```bash
-cloudsplaining create-multi-account-config-file \ 
+cloudsplaining create-multi-account-config-file \
     -o multi-account-config.yml
 ```
 
@@ -42,7 +42,7 @@ Using the data above, you can run the following command:
 cloudsplaining scan-multi-account \
     -c multi-account-config.yml \
     --profile scanning-user \
-    --role-name CommonSecurityRole \ 
+    --role-name CommonSecurityRole \
     --output-bucket my-results-bucket
 ```