separate class for images which fill full span

This commit is contained in:
Adam Wiggins
2011-10-20 15:43:41 -06:00
parent cbf6b3c7a2
commit 6e618209ce
2 changed files with 8 additions and 3 deletions
+1 -1
View File
@@ -9,7 +9,7 @@ Backing services like the database are traditionally managed by the same systems
Each distinct backing service is a *resource*. For example, a MySQL database is a resource; two MySQL databases (used for sharding at the application layer) qualify as two distinct resources. The twelve-factor app treats these databases as *attached resources*, which indicates their loose coupling to the deploy they are attached to.
<img src="/images/attached-resources.png" style="float: none" alt="A production deploy attached to four backing services." />
<img src="/images/attached-resources.png" class="full" alt="A production deploy attached to four backing services." />
Resources can be attached and detached to deploys at will. For example, if the app's database is misbeaving due to a hardware issue, the app's administrator might spin up a new database server restored from a recent backup. The current production database could be detached, and the new database attached -- all without any code changes.
+7 -2
View File
@@ -31,7 +31,7 @@ header a {
section {
padding-top: 16pt;
text-align: center;
min-width: 70em;
min-width: 65em;
}
section h1 {
font-size: 19pt;
@@ -43,7 +43,7 @@ article {
article, nav {
margin: 0 auto;
text-align: justify;
width: 60em;
width: 55em;
}
article p a, article li a {
text-decoration: none;
@@ -136,3 +136,8 @@ article img {
float: right;
margin-left: 32pt;
}
article img.full {
float: none;
margin-left: 0;
}