added modules

Author: Mariya Pershina

docs/topics/proc_accessing-analysis-report.adoc

@@ -0,0 +1,28 @@
+:_newdoc-version: 2.18.5
+:_template-generated: 2025-06-16
+:_mod-docs-content-type: PROCEDURE
+
+[id="accessing-analysis-report_{context}"]
+= Accessing an analysis report
+
+When you run an application analysis, a report is generated in the output directory that you specify by using the `--output` argument in the command line.
+
+.Procedure
+
+* Copy the path of the `index.html` file from the analysis output and paste it in a browser of your choice:
++
+[subs="+quotes"]
+----
+Report created: _<output_report_directory>_/index.html
+          	Access it at this URL: file:///_<output_report_directory>_/index.html
+----
++
+Alternatively, press *Ctrl* and click on the path of the `index.html` file.
+
+
+
+
+[role="_additional-resources"]
+.Additional resources
+* xref:running-cli[Running the CLI]
+

docs/topics/ref_analysis-report-sections.adoc

@@ -0,0 +1,32 @@
+:_newdoc-version: 2.18.5
+:_template-generated: 2025-06-16
+:_mod-docs-content-type: REFERENCE
+
+[id="analysis-report-sections_{context}"]
+= Analysis report sections
+
+The following are sections of the analysis report that you can review after an application analysis is complete. These sections contain additional details about the migration of an application.
+
+NOTE: You can only review the report applicable to the current application.
+
+:FeatureName: Insights
+include::snippets/technology-preview-admonition.adoc[]
+
+
+
+.Analysis report sections
+[options="header"]
+|====
+|Section|Description
+|Dashboard|An overview of the incidents and total story points sorted by category.
+|Issues|A concise summary of all issues and their details that require attention.
+|Dependencies|All Java-packaged dependencies found within the application. 
+|Technologies|All embedded libraries grouped by functionality. Use this report to display the technologies used in each application. 
+|Insights|Information about a violation generated by a rule with zero effort. Issues are generated by general rules, whereas string tags are generated by tagging rules. String tags indicate the presence of a technology but do not show the code location. Insights contain the information about the technologies used in the application and their usage in the code.
+
+Insights do not impact the migration. For example, a rule searching for deprecated API usage in the code that does not impact the current migration but can be tracked and fixed when needed in the future. 		
+
+Unlike issues, insights do not need to be fixed for a successful migration. They are generated by any rule that does not have a positive effort value and category assigned. They might have a message and tag.
+|====
+
+