Skip to main content

WVU Design System FAQs

Below is a list of common questions and answers about the WVU Design System. If you have a question that is not listed, file an issue, and be sure to label it as a question.

  1. What if my theme is based on an old version of Super Theme? How do I get the new components?
  2. If I submit a new component, how does it get included in the Design System?
  3. Do I need to build the partial when submitting a component for the Super Theme? Shared partials are too complicated.
  4. I’ve created my pages but nothing shows up between the masthead and footer when I go to edit my page. Why?
  5. Some regions have no content in them, but display anyways, breaking my site. What’s up with that?
  6. What if I want to use the Super Theme, but have a couple custom components I also want to use?
  7. I'm using a featurettes component and I think I have my pages labeled correctly, but they aren’t showing up. What’s up?
  8. Why is the content in my editable region disappearing after I publish?

What if my theme is based on an old version of Super Theme? How do I get new versions of components?

If you have an older version of the theme, and want to reference newer versions of components, you can edit your theme’s custom data. This is how your theme knows which components are available. You can keep old versions of components and/or include new ones. For more on this, see our tutorial on Retrofitting an Old Theme with a New Component.

If I submit a component, how does it get included in the Design System?

Just follow the instructions on our Contribute page.

Do I need to build the partial when submitting a component for Super Theme? Shared partials are too complicated.

No. Just submit the HTML and Sass and we can take care of the rest.

After you’ve created a new page, you might have to re-open the page’s properties and re-save them before any default content regions will display on your pages. This is a bug on older versions of the theme.

Some regions have no content in them, but display anyways, breaking my site. What’s up with that?

Some content regions display depending on whether a specified editable region contains content. So if you don’t want them to display, you leave the region blank. But sometimes you think you are leaving it blank when it’s really not. For example, if there is a nonbreaking space, or an empty HTML tag in the region, it will not be visible, but nevertheless can “trick” the region into thinking content exists, and will show the region anyways. To fix this, go into the HTML view of your editable region, manually remove any extra spaces or empty HTML tags, and re-publish the page.

Note that some browsers, for example Firefox, like to add spaces to empty editable regions. Firefox is therefore not a preferred browser for editing in CleanSlate if your site utilizes the type of content-dependent element described above.

What if I want to use the Super Theme, but have a couple custom components I also want to use?

Sometimes you start with a Super Theme and realize the available components don’t do exactly what you want. No problem. You can always add custom partials to your theme. You might copy one of our shared partials and tweak it, or create something new from scratch.

See our section on Adding Custom Components at the bottom of the Using Slots with Super Theme for more info.

I'm using a featurettes component and I think I have my pages labeled correctly, but they aren’t showing up. What’s up?

Did you check the instance number? Sometimes people forget to include the instance number when they label pages that contain content they wish to displpay. For example, if you have a page with the slug home, and are using a featurettes component with an instance number of 2 on this page, you must use home-featurettes-2 to label any pages with content you wish to display.

Why is the content in my editable region disappearing after I publish?

This is usually due to 2 or more of the same type of component having the same instance number. If this is the case, both components will have the same editable region names, and the content in the last instance of the component will override any previous instance. Just change the instance number of one of the components.