Terms of Service
These terms of service are between ITECS and _______________________________ (the customer). Because ITECS is mainly funded by student fees, academic sites are our first priority. Support for research-centered sites is limited to consultation.
- Brand Compliance: The customer agrees to the amount of brand compliance according to their NC State affiliation as indicated below. Brand guidelines and recommendations can be found at https://brand.ncsu.edu.
Full Compliance: The site must follow guidelines as published at brand.ncsu.edu.
- An Academic Department with a domain name ending in ncsu.edu. Exception is made for the Department of Biomedical Engineering which is joint with UNC-Chapel Hill.
- A Research Group associated with one or more departments with a domain name ending in ncsu.edu.
Partial Compliance: Site should follow guidelines as published at brand.ncsu.edu. Sites in place as of July 2016 may grandfather their known logos otherwise logos are not permitted.
- A Research Center with a domain name ending in ncsu.edu and no affiliation to any other university.
Acknowledgement of Hosting: The site footer must contain “This site is hosted by the College of Engineering at NC State University.” or some equivalent text approved by ITECS.
- A Research Center with a domain name ending in ncsu.edu and at least one affiliation to another university.
- An Academic or Professional Organization with a domain name ending in .org directly affiliated with a faculty member in the College of Engineering.
- Themes: The customer agrees to deploy a vetted theme that meets their appropriate level of brand compliance and that works in the environment provided by ITECS.
- ITECS supported themes: ITECS will maintain and support only those themes that ITECS authors.
- Standard themes: Customers may use standard themes from the WordPress.org website that have been validated by the ITECS vetting process. The customer is responsible for the on-going support of the theme. The theme must have the ability to automatically update. If there is no built-in update mechanism, it must be added to the NC State Plugin/Theme Repository to enable automatic updates.
- Custom Themes: The customer is responsible for ensuring that any contract for custom theme development includes ongoing support so that their theme is kept secure and continues to work as WordPress upgrades are applied.
- UX Standards
- Static images only: University brand requirements recommend single images over image collections/composites. Likewise, scrollbars, sliders and carousels are proscribed because they interfere with display responsiveness across browsers and devices. For more information see brand.ncsu.edu/imagery/.
- Plugins: WordPress core functionality can be enhanced by the addition of special software components called plugins.
- Vetting: All plugins must pass a four-step vetting process before they are deployed to live services.
- Business value: The plugin must have a business value that furthers the mission of NC State and College of Engineering. To reach a sufficient return on investment it must be of value to a significant portion of users in the WordPress environment.
- Licensing: The ITECS software licensing manager must get purchase approval from Security and Compliance in OIT.
- Technical: The plugin must be secure. The plugin must have the ability to automatically update. If there is no built-in update mechanism, it must be added to the NC State Plugin/Theme Repository to enable automatic updates.
- Testing: The plugin must function as advertised and without fault in the ITECS test environment.
- Maintenance: Plugins must be maintained by their authors.
- Any plugin found to have security holes will be temporarily patched. The author of the plugin must agree to provide a permanent patch within one month or the plugin will be removed.
- In the rare case that ITECS cannot make a temporary security patch, the plugin will be removed immediately.
- Content: Site content belongs to site authors
- At its discretion, ITECS may provide limited help with porting content from an established site in AFS to a WordPress site using the Riddick theme.
- It is the responsibility of the customer to make all content changes on live sites.