Hero banner

This is a short summary. To keep the hero banner from being too tall, avoid having a long passage of text in the body text here. It makes the banner too tall and out of proportion with the rest of the page. Also, if you add an illustration, the illustration will be too big. 

Before you start

We often use "Before you start" styled as "Title" here in the body copy for any information you need to know before starting a step by step.

If the hero banner has too much body text, or alerts or bulleted lists, move them down here.

Having text in this body text area also creates a buffer for the print/share buttons to the right.

How to do content QA on SRL pages

  • Check the top of the page

    • Check the title of the page: Is it in in sentence case rather than Title Case? If it starts with a gerund (a "ing" word like Getting or Filing) edit it to eliminate the gerund. (They are hard to translate.)
    • Does an illustration make sense here?
    • Is the hero too tall? Move text into the body text area instead.
    • If it's appropriate to the content, add "Before you start" as a header (Title style) on the body text.
    • Check the top of the step container. Remove anything in the Brow field. (We don't use that component.) Also remove anything from the description field and move it to the body text. (We tend not to use that component either.)
    • Check the title of the step container. The text should begin with "How to..."
  • Check the page for extra spaces

    It's very easy to end up with extra spaces between lines of text and components.

     

    For example, there's a line return in the WYSIWYG that looks fine when you see it there, but it's creating an extra space between this line and the line above.

    You may also need to remove extra spaces between components. 

     

    You may find extra spaces above or below an alert or detail. This one has an extra space above. You know you've removed them if there's no space between the bottom of the component and the yellow line in the WYSIWYG editor
     

    Check for pesky extra spaces between paragraphs, between sentences (one space - not two - after a period), and between words. 

  • Check text styling and case

    Use sentence case for headers and titles

    All titles, names of steps, and headers should be in sentence case

    How to style terms

    Terms and emphasized phrases in bold (not italic or in quotes). For example:

    • The person who started the case (the petitioner) files the form with the court clerk.

    How to style form names

    Form names should be in italic, form numbers in parentheses (linked when associated with an action). For example:

    • After you file your Responsive Declaration (form FL-320), you must have someone deliver a copy of the papers to your spouse or the other parent. 

    Sometimes you make subsequent or short-hand references to forms after giving the full name. In this case use upper case and italics. For example:

    • Serving means another adult, not you, mails or hands a copy of your Responsive Declaration to your spouse. 

    When to use quotes

    Reserve the use of quotes for when literally quoting text that's on a document or form. For example:

    • At the top of the form, write your name where it says "Petitioner."

    How to style bulleted lists

    Check bulleted lists to make sure that:

    • Each item begins with an upper case letter  

    • All list items have a parallel grammatical structure 

    • List items don’t have punctuation at the end unless the item has more than one sentence. This is an example of that.

    • Any lead-in phrase (like the one above) includes a colon if the bullets complete the phrase

  • Check the formatting of details and alerts

    Learn more details are made up of a "teaser" sentence and end with “Learn more” and no period.  

    Details provide extra information that applies to a subset of SRLs. 
    • They address less common but important exceptions​

    • They address variation in procedure​

    • Usually the content in a detail would make the text less readable or too lengthy if it were included in the main text​

    Question details are made up of a question asked from the SRL point of view. No "Learn more" at the end.

    They anticipate and address common questions​. Think of them as addressing the "anxious ifs" that might come up for SRLs​. They are phrased in the voice of the SRL rather than the voice of the court​.

    Use the "Warning" (yellow) version of the alert to emphasize important information.

    Text styling in alerts is tricky.

    It can be effective to use bold for the first sentence, but make sure that all of the text in an alert doesn't turn bold. When it does, it can mess up the kerning and generally looks inelegant.
     

     

  • Check link styling

    Links to pages outside the SRL portal use “Button external” 

    Find Your Court

     

    Links that appear on their own line or are intended as navigation that supplements or substitutes for “what’s next” use “Button primary” styling 

    Learn how to ask for a temporary order

     

    Incidental or referential links use inline hyperlinks

    • You must share your financial information if you filed a Response. If you did not file a Response, but you want the court to approve an agreement (called a default with agreement) you also must share your financial information.

     

case type or phase

What's next?

Check to make sure the "What's next" navigation footer includes the case type or phase in the Brow and uses "What's next?" as the title.

 

There should also be body text in this space that gives the user some context for the choices they are seeing in the tiles. (The amount of body text in this example is too long, by the way. It should be 1-3 sentences.)

 

Each tile should have a forward or back arrow. The "Mark my place component" should be in the middle on a forward/back version of the "What's next?"

 

Unlike the other body text fields, you have to actually add line breaks in the WYSIWYG editor to have them show up in the What's next body text.

success alert banner:

Have a question about Content Reference Guide?

Look for a "Chat Now" button in the right bottom corner of your screen. If you don’t see it, disable any pop-up/ad blockers on your browser.