WIP: adding community tags to images

server_development/topics/user-storage/configuration.adoc

@@ -123,9 +123,13 @@ unique per provider instance.  We move this logic to the `create()` method.
 This logic, is of course, is really inefficient as every different transaction will read the entire user property file from disk,
 but hopefully this illustrates, in a simple way, how to hook in configuration variables.
 
-==== Configure in Admin Console
+==== Configuring the Provider in Admin Console
 
 Now that the configuration is enabled, you can set the `path` variable when you configure the provider in the admin console.
 
+{% if book.community %}
+
 .Configured Provider
 image:../../{{book.images}}/storage-provider-with-config.png[]
+
+{% end if %}

server_development/topics/user-storage/simple-example.adoc

@@ -306,19 +306,25 @@ or using the JBoss CLI.
 
 You enable user storage providers per realm within the `User Federation` page in the admin console.
 
+{% if book.community %}
 .User Federation
 image:../../{{book.images}}/empty-user-federation-page.png[]
+{% endif %}
 
 Select the provider we just created from the list: `readonly-property-file`.  It brings you to the configuration
-page for our provider.  We don't have anything to configure, so just click the `Save` button.
+page for our provider.  We don't have anything to configure, so click *Save*.
 
+{% if book.community %}
 .Configured Provider
 image:../../{{book.images}}/storage-provider-created.png[]
+{% endif %}
 
-When you go back to the main `User Federation` page, you'll now see your provider listed.
+When you go back to the main `User Federation` page, you now see your provider listed.
 
+{% if book.community %}
 .User Federation
 image:../../{{book.images}}/user-federation-page.png[]
+{% endif %}
 
 You will now be able to log in with a user declared in the `users.properties` file.  Of course, this user will have
 zero permissions to do anything and will be read only.  You can though view the user on its account page after you