remove unused alert block and add hugo_stats to gitignore

DefectDojo · Nov 8, 2024 · c579b0c · c579b0c
1 parent f89e16d
commit c579b0c
Show file tree

Hide file tree

Showing 8 changed files with 2 additions and 23 deletions.
diff --git a/.gitignore b/.gitignore
@@ -135,3 +135,4 @@ helm/defectdojo/charts
 docs/public
 docs/node_modules
 docs/resources
+docs/hugo_stats.json
diff --git a/docs/content/en/contributing/how-to-write-a-parser.md b/docs/content/en/contributing/how-to-write-a-parser.md
@@ -5,9 +5,7 @@ draft: false
 weight: 1
 ---
 
-{{% alert title="Information" color="info" %}}
 All commands assume that you're located at the root of the django-DefectDojo cloned repo.
-{{% /alert %}}
 
 ## Pre-requisites
 
@@ -276,9 +274,7 @@ Example for the blackduck hub parser:
 $ docker-compose exec uwsgi bash -c 'python manage.py test unittests.tools.test_blackduck_csv_parser.TestBlackduckHubParser -v2'
 {{< /highlight >}}
 
-{{% alert title="Information" color="info" %}}
 If you want to run all unit tests, simply run `$ docker-compose exec uwsgi bash -c 'python manage.py test unittests -v2'`
-{{% /alert %}}
 
 ### Endpoint validation
 

diff --git a/docs/content/en/getting_started/running-in-production.md b/docs/content/en/getting_started/running-in-production.md
@@ -25,9 +25,7 @@ Media files for uploaded files, including threat models and risk acceptance, are
 
 ### Instance size
 
-{{% alert title="Information" color="info" %}}
 Please read the paragraphs below about key processes tweaks.
-{{% /alert %}}
 
 
 With a separate database, the minimum recommendations

diff --git a/docs/content/en/getting_started/upgrading/_index.md b/docs/content/en/getting_started/upgrading/_index.md
@@ -13,11 +13,8 @@ should not lose any data.
 
 ### Using docker images provided in DockerHub
 
-{{% alert title="Information" color="info" %}}
 If you\'re using `latest`, then you need to pre pull the `latest` from
 DockerHub to update.
-{{% /alert %}}
-
 
 The generic upgrade method for docker-compose are as follows:
 -   Pull the latest version

diff --git a/docs/content/en/integrations/parsers/file/aws_scout2.md b/docs/content/en/integrations/parsers/file/aws_scout2.md
@@ -4,14 +4,11 @@ toc_hide: true
 ---
 JS file in scout2-report/inc-awsconfig/aws\_config.js.
 
-{{% alert title="Warning" color="warning" %}}
 AWS Scout2 Scanner is deprecated and has been replaced with ScoutSuite (https://github.com/nccgroup/ScoutSuite) upstream.
 Please switch to the new parser for ScoutSuite.
-{{% /alert %}}
 
-{{% alert title="Warning" color="warning" %}}
 This parser is disactivated by default in releases >= 2.3.1 and will be removed in release >= 3.x.x.
-{{% /alert %}}
+
 
 ### Sample Scan Data
 Sample AWS Scout2 Scanner (deprecated) scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/aws_scout2).
diff --git a/docs/content/en/integrations/parsers/file/sarif.md b/docs/content/en/integrations/parsers/file/sarif.md
@@ -6,14 +6,10 @@ OASIS Static Analysis Results Interchange Format (SARIF). SARIF is
 supported by many tools. More details about the format here:
 <https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif>
 
-{{% alert title="Information" color="info" %}}
 SARIF parser customizes the Test_Type with data from the report.
 For example, a report with `Dockle` as a driver name will produce a Test with a Test_Type named `Dockle Scan (SARIF)`
-{{% /alert %}}
 
-{{% alert title="Warning" color="warning" %}}
 Current implementation is limited and will aggregate all the findings in the SARIF file in one single report.
-{{% /alert %}}
 
 ##### Support for de-duplication (fingerprinting)
 

diff --git a/docs/content/en/usage/features.md b/docs/content/en/usage/features.md
@@ -456,11 +456,9 @@ The `SLA_NOTIFY_POST_BREACH` lets you define in days how long you want
 to be kept notified about findings that have breached the SLA. Passed
 that number, notifications will cease.
 
-{{% alert title="Warning" color="warning" %}}
 Be mindful of performance if you choose to have SLA notifications on
 non-verified findings, especially if you import a lot of findings
 through CI in \'active\' state.
-{{% /alert %}}
 
 
 ### What notification channels for SLA notifications?
@@ -492,11 +490,9 @@ modify this schedule to your context.
 }
 {{< / highlight >}}
 
-{{% alert title="Information" color="info" %}}
 The celery containers are the ones concerned with this configuration. If
 you suspect things are not working as expected, make sure they have the
 latest version of your settings.py file.
-{{% /alert %}}
 
 
 You can of course change this default by modifying that stanza.

diff --git a/docs/content/en/usage/permissions.md b/docs/content/en/usage/permissions.md
@@ -122,6 +122,4 @@ Many configuration dialogues and API endpoints can be enabled for users or group
 * Notifications on system level
 * Configuration permissions for users and groups
 
-{{% alert title="Warning" color="warning" %}}
 These configuration settings are a powerful tool and should be used with great care.
-{{% /alert %}}