diff --git a/basics/writing-a-skin.md b/basics/writing-a-skin.md index 26ad350..ab310f0 100644 --- a/basics/writing-a-skin.md +++ b/basics/writing-a-skin.md @@ -24,7 +24,7 @@ The skin system is also a great way to get familiar with CSS in general or the A Here we'll walk through a simple skin that modifies the Archive's default appearance by changing fonts and colors, adding images, and adjusting margins and borders. - + For our colors and images, we'll be using a stripe pattern called [sing together](https://www.colourlovers.com/pattern/850926/sing_together) and its color palette, [like fireflies](https://www.colourlovers.com/palette/1172215/like_fireflies), both of which are by [electroCUTE!](https://www.colourlovers.com/lover/electroCUTE%21). You'll need to save and upload the background image to an image host, but because you are the only one seeing your skin, you probably don't need to worry about running out of bandwidth. diff --git a/classes-taxonomy.md b/classes-taxonomy.md index 3ba5951..0cde16b 100644 --- a/classes-taxonomy.md +++ b/classes-taxonomy.md @@ -121,6 +121,8 @@ We can divide types into two abstract classes: The abstract class `.object` encompasses classes that correspond with database records. These are typically a *type* of record that corresponds with a model name, such as `.work` or `.user`, but sometimes they're *specific* records, such as the `.rating-teen` class that corresponds with the [Teen and Up Audiences rating tag](https://archiveofourown.org/tags/Teen%20And%20Up%20Audiences). +These class names are almost always singular, with the exception of `tags`. + * .user * .work * .chapter @@ -160,6 +162,7 @@ The abstract class `.object` encompasses classes that correspond with database r * .prompt * .item * .signup + * .assignment ### data @@ -181,6 +184,7 @@ The abstract class `.data` encompasses classes that describe the type or format * .notice * .error * .icon +* .rss * .symbol * .help * .question diff --git a/patterns/blurb.md b/patterns/blurb.md index 41177db..330fa80 100644 --- a/patterns/blurb.md +++ b/patterns/blurb.md @@ -26,7 +26,7 @@ The styles for blurbs are located in [the stylesheet named 13-group-blurb.css](h The work blurb is the most used chunk of HTML code in the Archive, so we've revised it a lot. It has to contain lots of information and allow different ways of accessing its material. The blurb is flexible, accessible, and has multiple redundancies (says the same thing in different ways). - + Since we usually have many blurbs listed together, the index page that holds the blurbs is coded as an HTML list, and each blurb is coded as a list item. If a page will only ever contain one blurb (e.g., the adult content warning), the blurb can be coded as a different element, such as a `div`. @@ -217,7 +217,7 @@ While the HTML structure of the blurb is incredibly important and should not be Here you see two different examples of the work blurb from the AO3, one using the default CSS and one using a skin, which have some of their fields mapped to the blurb diagram to help give you the idea. - + These blurbs use *the same HTML*. The only thing different is the CSS. diff --git a/patterns/comments.md b/patterns/comments.md index 5930ff1..c310cb4 100644 --- a/patterns/comments.md +++ b/patterns/comments.md @@ -80,7 +80,7 @@ An individual comment is always a `li` contained within an `ol`. These comment l To illustrate the HTML for threads, we'll diagram the following example. Each `li` with the `comment` class contains the HTML diagramed in the previous section. - +