Access and Features
Questions about desirable options or expected behavior
Customizing Your Site
Questions about adding new styles and/or functionality to your site
Questions about launching your site and the days leading up to the launch
Questions about the best ways to build your site
UW Theme Concerns
Questions relating to the design and functionality of the UW Theme
- Why does the UW Theme not have the same functionality as the wisc.edu site?
- I’m frustrated that my request hasn’t been adapted into the UW theme yet. How soon will that happen?
- If I want to contribute to the theme, how would I do that? I have little technical knowledge.
- I don’t like the design of the theme. How can I change it?
Why don’t my hero images auto-rotate?
We get this question a lot. Our old OpenText customers used to have the ability to set their image carousels to automatically scroll through photos every few seconds. The UW Theme does not provide this functionality and there are two reasons for this:
- Image carousels aren’t accessible for users navigating the site with a screen reader.
- Extensive research has shown carousels are actually not nearly as engaging for users as we assumed.
What is the difference between "Draft" and "Published" pages and posts?
Pages and posts that are saved in Draft mode are assumed to be “in development” and therefore, will not show on the site. This is not a problem when the page or post has never been published but if they have, it will be removed from the website entirely until you re-publish.
We recommend that you do not ever set your pages or posts to Draft if you do not wish for them to be removed from the site until publish. Instead, create a copy and do your edits there. Then, when you are ready to publish, put up the copy version and take down the other OR paste the contents of the copied page into your existing page and publish right away.
Why can’t I use the password option on a WordPress page or post
WordPress offers a rudimentary password protection option for pages and posts. This can be set with an admin-designated password in the Publishing region of the page (under Visibility). Typically, this is a pretty simple way for site administrators to lock down a specific page or post without having to download a page-lock plugin (or lock down the entire site with a Manifest Group). However, this feature is currently not functional for users of WiscWeb as it conflicts with the campus Shibboleth technology. Please note that we are working on this and hope to have a solution very soon.
When should I use posts versus pages?
WordPress is different from a lot of other content management systems because it started as a blogging tool and then grew into a tool that was used world-wide for the building and maintenance of regular websites. As a blogging tool, it was assumed that users were mostly generating content via posts (like news articles) and that’s the basis for how this tool was structured. Therefore, everything in WordPress is technically a post – even pages! Confused yet?
The biggest thing to remember is that you should use “Posts” (in the left nav options) when you are focusing on news or blog content that you’d like to feed into a post list. This is usually the only way that true Posts are used in the UW Theme. You should use “Pages” to build out the content that will go in the navigation of your site. To reiterate: Pages are the main content holders while Posts are just for articles.
Why does the UW Theme not have the same functionality as the wisc.edu site?
The answer to this question requires some background info:
- The wisc.edu site was updated with new campus branding in January of 2016.
- Mid-way through 2016, other campus sites started requesting this same template (look and feel) and University Marketing decided to build out the UW Theme Lite theme for use by WordPress users on campus.
- In the summer of 2016, DoIT developers (in collaboration with University Marketing) began working on building out the UW Theme for WordPress
- In January, 2017, the WiscWeb team started offering WordPress websites using the UW Theme
The biggest thing to note from this timeline is that the wisc.edu site was not actually built with the UW Theme. Instead, the UW Theme was designed to look like the styles that were introduced on the wisc.edu site back in 2016. Therefore, just because something appears on the wisc.edu site, does not mean it is automatically added as an option in your WiscWeb site via the UW Theme.
The answer to this is equally complicated and really depends on the functionality.
For the most part, if something appears on the wisc.edu site and it is not available in the UW Theme, there are three likely reasons:
- The UW Theme developers have not finished building it yet.
This does not happen often but the UW Theme developers do try to incorporate wisc.edu functionality when it makes sense to do so and it will benefit the masses.
- This functionality is not easily or adequately implemented by the average campus web editor.
Some of the functionality on the wisc.edu site is just so specific that campus editors would require much more advanced web development or design skills in order to properly implement them. The UW Theme is meant to be easily digested by a large portion of campus editors from all different skill levels so adding this type of functionality would mean more support and maintenance than what can feasibly be provided.
- The functionality is meant for a specific purpose that is unique to the kinds of marketing and promotional needs that the wisc.edu site requires.
The wisc.edu site, unlike most campus websites, is both an informational page as well as a marketing tool. Therefore, the kinds of functionality they need on their site differs greatly from what the average campus website needs.
Request New Functionality
If you are interested in certain features of the wisc.edu page because you think it will fulfill a specific need that you have for displaying information on your site, we want to hear about it. This will allow us to gauge how many users on campus have the same need and we can deliver something that will be targeted for campus informational sites. Please fill out our Feature Request Form and let us know what kind of needs you are trying to accommodate.
Why can't I have FTP access to my site?
There are several reasons for this. WiscWeb is a multisite instance of WordPress. As such, providing you FTP access would grant you access to all WiscWeb sites – not just your own. We really do not want users to have the ability to change projects that are not their own and therefore, FTP access is not allowed. We also have strict version control processes in place to maintain the stability of the multisite for all customers. Allowing folks access to make changes via FTP could jeopardize this stability and result in site or entire service outages.
Please note that Amazon Web Services (AWS) does not facilitate FTP access.
Why can't I add plugins to my site?
WiscWeb is a controlled and supported multisite environment. All plugins go through a vetting process prior to addition to the multisite to ensure that they will not jeopardize the stability of the service. This vetting process can be reviewed here: https://wiscweb.wisc.edu/plugin-review-process/.
Once plugins are added, the WiscWeb team supports them. This requires regular testing of each plugin anytime there are updates to the plugin itself, the UW Theme, or WordPress. It also involves a significant amount of testing on individual sites to ensure that customizations, styles, and functionality are rendering correctly after plugins are activated or updated. We vet and limit the plugins so that we can continue to maintain this level of security and service integrity.
Who do I ask to have a plugin added to my site?
While we cannot allow you to add your own plugins to your site, we do offer several plugins under our service. Our full list of available plugins can be found here: https://wiscweb.wisc.edu/plugins/.
Some of these plugins will not be activated in your project by default. To request that one of our plugins be activated, please send an email to email@example.com. Please include:
- Your project name
- A link to your website
- The name of the plugin you’d like for us to activate
Why don't I see the option to add "Additional CSS" in my theme Customizer?
Under the WiscWeb service, the “Additional CSS” field is not available to admins and editors of the site. We require that all CSS updates are added directly to your project’s child theme. This is to prevent new UW Theme updates from potentially overwriting the changes that have already been made to your site styles.
WiscWeb has a process for child theme updates and code reviews that are performed on a cost-recovery basis. If you would like to request a quote for this, please complete and submit this form: https://wiscweb.wisc.edu/customizing-the-uw-theme/.
Please note: any custom CSS or logo changed to the UW Theme in WiscWeb must be approved by UW Marketing. To facilitate this process, please complete and submit this form: https://wiscweb.wisc.edu/header-redesigns-and-color-changes/. This will send an email to UW Marketing, who will either approve or deny your request.
How can I show my team changes that I've made to the live site before they go live?
Before Launching Your Site
Prior to launching your new website, you can publish and view all changes at your sitename.wiscweb.wisc.edu URL. This is a shareable link and the site’s contents will only be visible to those who have this URL.
After Launching Your Site
You have two options for this:
- You could build out the pages and save them in Draft and then login to show them to a group. Users who did not have access to the site would not be able to preview these pages so you would not be able to send a link to a page that is in Draft. However, you could show them on your own computer.
- You could publish the pages but not link them from anywhere on the live site. You would access them by going directly to the URL.
How do I structure my (really complicated) categories and tags for posts?
If there is ever a time when you aren’t sure the best way to present information on your site, we recommend attending one of our Open Labs to speak directly with a member of our team. They can meet with you to learn more about the issue you are experiencing and can offer suggestions based on your unique case. More information about our Open Labs, including a full schedule of upcoming sessions, can be found here: https://wiscweb.wisc.edu/open-labs/.
Can I add my own code to a project?
At this time all customizations to sites in WiscWeb must be done by a WiscWeb developer, in order to ensure the stability of the entire multisite. There is a charge for customizations because this type of work is not covered by the campus funding. If you are interested in meeting with a developer to discuss customizations to your child theme in WiscWeb, please email us at firstname.lastname@example.org so that we can setup a time. We will likely want to sit down with you at an Open Lab but will need to know which one you will be attending (schedule here).
In your email, please include:
- Your project name
- A link to your website
- A description of what you are looking to do on your site
- The date/time of the open lab that you can attend
Why can't I work on the test site in order to preview my content?
The test site that WiscWeb offers is strictly for testing (plugins, WordPress, and plugin updates), and is not meant for content creation before releasing it to a published site. We do not offer a sandbox area for customers. This is to save overall costs for the campus.
I see that site X has a particular functionality. Why doesn't mine?
The customizations that you see on other sites are customizations that were paid for by the customer. This payment includes the ongoing maintenance and support of those customizations.
There are some customizations that you see that may be related to plugins that are available but are not activated for every site (i.e. publications). All plugins that are available to Wiscweb sites are listed at https://wiscweb.wisc.edu/plugins/. If you see functionality on another site that you like, check the plugins page to see if it is something that can be added to your site.
Additionally, we receive a lot of questions about why their site doesn’t have the same functionality as the main wisc.edu site. For more insight into why that is, please refer to our other FAQ here: https://wiscweb.wisc.edu/faq/#uwthemevswiscsite.
How can I use the MailChimp plugin with my site?
MailChimp is currently not an approved plugin under the WiscWeb service. If you would like to request a plugin review, please complete and submit the following form: https://wiscweb.wisc.edu/plugin-request/.
I’m frustrated that my request hasn’t been adapted into the UW theme yet. How soon will that happen?
We have many requests for UW Theme updates. They are prioritized by the following criteria:
- Existing functions/features are broken
- Would the requested functionality benefit the majority of campus?
- Does the benefit to campus justify the cost to create the functionality?
If it meets these requirements, then resources can be allocated to the updates, testing and support.
If you have a particular request that you have made, and you haven’t received an update, please contact us at email@example.com to ask for a status.
Can I change my site font from Verlag to something else?
In WiscWeb, all requests for changing the UW Theme must first be approved by UW Marketing. You can submit your request using this form: https://wiscweb.wisc.edu/header-redesigns-and-color-changes/. Once your request has been approved, please email firstname.lastname@example.org and the WiscWeb team will set up a time to discuss the desired changes with you. Please note that there may be a small fee for this customization.
If I want to contribute to the theme, how would I do that? I have little technical knowledge.
There is information on how to contribute to the UW Theme located at: https://uwtheme.wordpress.wisc.edu/about/. Please note that if you have little technical knowledge, this process may prove challenging. If there is something you have questions about, please make some time to attend one of our open lab sessions: https://wiscweb.wisc.edu/open-labs/. A discussion of your needs will allow us to best assist you so be prepared to answer questions about what you are looking to do.
I don’t like the design of the theme. How can I change it?
In WiscWeb, all requests for changing the UW Theme must first be approved by UW Marketing. You can submit your request using this form: https://wiscweb.wisc.edu/header-redesigns-and-color-changes/. Once your request has been approved, please email email@example.com and the WiscWeb team will set up a time to discuss the desired changes with you. Please note that we have an hourly rate that we charge for this work. If you would like to receive a quote for the development changes, please fill out and submit the following form: https://wiscweb.wisc.edu/customizing-the-uw-theme/.
How do I structure my site content?
We have the ability to do some initial consultation about the structure and layout of your site’s contents. DoIT also offers a full UX and Content Strategy evaluation service (fee based) for more complex requirements. If you are interested in these services, please contact firstname.lastname@example.org.
I was told my content would be better as a Custom Post Type, but we don’t have the budget for custom development. What can I do?
If you do not have money for custom development, you will need to rethink your requirements for the content. Please come to an Open Lab and work with our team to come up with a different option. We can help look for different ways within the UW Theme to display the content.