<commit_before>= Heroku User Journey
:author: <NAME>, <NAME>
:email: <EMAIL>, <EMAIL>
:revnumber: {codekvastVersion}
:revdate: {gitTime}
:revremark: {gitId}
:imagesdir: images
:data-uri:
:numbered:
:linkattrs:
:toc: left
:toclevels: 3
:icons: font
:source-highlighter: prettify
:attribute-missing: warn

[abstract]
== Introduction
The Heroku User Journey describes our vision of the user experience
when monitoring a Heroku application for truly dead code.

Setting is someone that have an Heroku application already and wish
to find its truly dead code.

== The Journey

=== Discovering Codekvast
In the Heroku console, our user is looking for tools that can improve their code
and finds Codekvast. Removing truly dead code sounds intriguing so our user set out
try Codekvast.

=== Registering at codekvast.io

=== Adding Codekvast to their app

[source,bash,subs="attributes,verbatim"]
----
heroku addons:create codekvast:priceplan
----
=== Adding Codekvast to their Maven pom

=== Build

User runs the Heroku build that deploys a new version of their app which has
been instrumented for the Codekvast agent.

=== Check their dashboard at codekvast.io

The app will report usage constantly to the Codekvast web. Our user will can see
methods that are never used.<commit_msg>Heroku user journey: wrote about registering.<commit_after>= Heroku User Journey
:author: <NAME>, <NAME>
:email: <EMAIL>, <EMAIL>
:revnumber: {codekvastVersion}
:revdate: {gitTime}
:revremark: {gitId}
:imagesdir: images
:data-uri:
:numbered:
:linkattrs:
:toc: left
:toclevels: 3
:icons: font
:source-highlighter: prettify
:attribute-missing: warn

[abstract]
== Introduction
The Heroku User Journey describes our vision of the user experience
when monitoring a Heroku application for truly dead code.

Setting is someone that have an Heroku application already and wish
to find its truly dead code.

== The Journey

=== Discovering Codekvast
In the Heroku console, our user is looking for tools that can improve their code
and finds Codekvast. Removing truly dead code sounds intriguing so our user set out
try Codekvast.

=== Registering at codekvast.io

To use Codekvast, you need a api-key so that your app can connect to the dashboard.

Our user gets redirected from the Heroku website to codekvast.io website where they
are asked to sign up.

=== Adding Codekvast to their app

[source,bash,subs="attributes,verbatim"]
----
heroku addons:create codekvast:priceplan
----
=== Adding Codekvast to their Maven pom

Our user reads on codekvast.io how to modify their pom so that the app gets instrumented
by Codekvast.

=== Build

User runs the Heroku build that deploys a new version of their app which has
been instrumented for the Codekvast agent.

=== Check their dashboard at codekvast.io

The app will report usage constantly to the Codekvast web. Our user will can see
methods that are never used.
{'fraction_non_alphanumeric': 0.07465277777777778, 'fraction_numerical': 0.0006944444444444445, 'mean_word_length': 4.903688524590164, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 11, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2137291', 'n_tokens_mistral': 858, 'n_tokens_neox': 819, 'n_words': 396}