add screenshots, reflow text

tex/part-practical.tex

@@ -1473,7 +1473,7 @@ and the results can be seen in Figure~\ref{fig:ssllabs}, confirming that HSTS
 Authority Authorisation (CAA) is configured for the domain, with the overall
 grade being A+.
 
-\obr{Quallys SSL Labs scan}{fig:ssllabs}{.75}{graphics/screen-sslLabs}
+\obr{Quallys SSL Labs scan}{fig:ssllabs}{.90}{graphics/screen-sslLabs}
 
 
 
@@ -1482,48 +1482,41 @@ grade being A+.
 Figure~\ref{fig:homepage} depicts the initial page that a logged-out user is
 greeted with when they load the application.
 
-\obr{Homepage}{fig:homepage}{.84}{graphics/screen-homepage}
+\obr{Homepage}{fig:homepage}{.83}{graphics/screen-homepage}
 
-Figure~\ref{fig:signup} can be seen showing a registration page with input
-fields turned green after basic validation. Visiting this page with
-registration disabled in settings would yield a 404.
+Figure~\ref{fig:signup} is showing a registration page with input fields turned
+green after basic validation. Visiting this page with registration disabled in
+settings would yield a 404.
 
-\obr{Registration page}{fig:signup}{.65}{graphics/screen-signup}
+\obr{Registration page}{fig:signup}{.40}{graphics/screen-signup}
 
-\newpage
+% \newpage
 
 \obr{Registration page email
-error}{fig:signupEmailError}{.54}{graphics/screen-signup-emailError}
+error}{fig:signupEmailError}{.40}{graphics/screen-signup-emailError}
 
 A sign-up form error telling the user to provide a valid email address is shown
 in Figure~\ref{fig:signupEmailError}.
 
-
-\obr{Sign-in page}{fig:signin}{.55}{graphics/screen-signin}
+\obr{Sign-in page}{fig:signin}{.40}{graphics/screen-signin}
 
 Figure~\ref{fig:signin} depicts a sign-in form similar to the sign-up one.
 
 \obr{Short password error on
-sign-in}{fig:signinShortPasswd}{.55}{graphics/screen-signin-shortPasswordError}
+sign-in}{fig:signinShortPasswd}{.40}{graphics/screen-signin-shortPasswordError}
 
 An error in Figure~\ref{fig:signinShortPasswd} prompts the user to lengthen the
 content of the password field from 3 to at least 20 characters.
 
-\newpage
-
-\obr{Admin homepage}
-{fig:adminHome}{.25}
-{graphics/screen-adminHome}
-
-Figure~\ref{fig:adminHome} displays a simple greeting and a logout button.
-
 \obr{User management screen}
-{fig:adminUserManagement}{.85}
+{fig:adminUserManagement}{.90}
 {graphics/screen-adminUserManagement}
 
 Figure~\ref{fig:adminUserManagement} shows the user management screen, which
 provides links to view user details page, start creating a new user.
 
+% \newpage
+
 % \obr{User creation screen}
 % {fig:adminUserCreate}{.35}
 % {graphics/screen-adminUserCreate}
@@ -1541,18 +1534,18 @@ WebAssembly) to check uniqueness of the username on user's \emph{key-up}.
 
 \newpage
 
-\obr{Creation of user `demo'}
-{fig:adminUserCreateDemo}{.75}
+\obr{`demo' user creation post-hoc}
+{fig:adminUserCreateDemo}{.85}
 {graphics/screen-adminUserCreateDemo}
 
+
 The user management screen is again shown in
 Figure~\ref{fig:adminUserCreateDemo} after user `demo' was created. An
 informative \emph{flash} message is printed near the top of the page
 immediately after the action and not shown on subsequent page loads.
 
-
 \obr{User details screen}
-{fig:adminUserDetail}{.65}
+{fig:adminUserDetail}{.75}
 {graphics/screen-adminUserDetail}
 
 The user details page is depicted in Figure~\ref{fig:adminUserDetail}. The
@@ -1560,8 +1553,10 @@ interface presents key information about the user such as ID, username and
 admin status. Additionally, it provides a link back to the previous page and
 two buttons: one for editing the user and one for user deletion.
 
+\newpage
+
 \obr{User edit screen}
-{fig:adminUserEdit}{.65}
+{fig:adminUserEdit}{.45}
 {graphics/screen-adminUserEdit}
 
 Figure~\ref{fig:adminUserEdit} shows the form for user editing with a button
@@ -1569,8 +1564,6 @@ Figure~\ref{fig:adminUserEdit} shows the form for user editing with a button
 `admin' and `active' state of the user. Above those, there are input fields for
 `username', `email', `password' and the confirmation of the password.
 
-\newpage
-
 \obr{User deletion confirmation}
 {fig:adminUserDeleteConfirm}{.55}
 {graphics/screen-adminUserDeleteConfirmation}
@@ -1585,21 +1578,15 @@ management page, and the `Back to detail' one that simply brings the
 administrator one step back to the user details page.
 
 \obr{User deletion post-hoc}
-{fig:adminUserDeletePostHoc}{.55}
+{fig:adminUserDeletePostHoc}{.65}
 {graphics/screen-adminUserDemoDeletion}
 
+\newpage
+
 After successful user deletion, the administrator is redirected back to user
 management page and a flash message confirming the deletion is printed near the
 top of the page, as shown in Figure~\ref{fig:adminUserDeletePostHoc}.
 
-\obr{Log-out message}
-{fig:logout}{.20}
-{graphics/screen-logout}
-
-Figure~\ref{fig:logout} shows the message printed to users on logout.
-
-\newpage
-
 \obr{Manage API keys}
 {fig:manageAPIKeys}{.65}
 {graphics/screen-manageAPIKeys}
@@ -1617,6 +1604,26 @@ the requests on \emph{behalf} of the users.
 Figure~\ref{fig:localImport} depicts how formatted breach data can be imported
 into the program's database using the CLI.
 
+Figure~\ref{fig:hibp-nobreach} displays the result of a search using the online
+data source. The account was not found to be a part of any of the available
+breaches.
+
+\newpage
+
+\obr{Compromise monitoring using online sources - no breach found}
+{fig:hibp-nobreach}{.60}{graphics/screen-hibp-nobreach}
+
+Figure~\ref{fig:hibp-breach3Accts} depicts the result of a search using
+the online API, providing a message and list of links to breach details.
+
+\obr{Compromise listing using online API (and a test account)}
+{fig:hibp-breach3Accts}{.54}{graphics/screen-hibp-breach3Accts}
+
+\obr{Stratfor breach details page}
+{fig:hibp-breachDetails}{.74} {graphics/screen-hibp-breachDetails}
+
+Figure~\ref{fig:hibp-breachDetails} shows the \emph{Stratfor} breach details
+page, with the data sourced from an online API.