TTUHSC IT Policies
9. WEB STANDARDS
With the proliferation of Internet use and given the importance of the Internet as a communications forum, it is increasingly important to establish guidelines that protect the Institution from liability while extending the Institution’s visual identity to include online publishing. All web and application development must comply with the security guidelines and coding practices set forth in Sections 1.4.20, 9.3, 9.4, and 9.5.
9.1. STUDENT WEB PUBLISHING STANDARDS
TTUHSC recognizes the value of publishing on the Internet and supports students in creating personal or curricular web sites and/or web pages. Free personal student accounts are available through the I.T. Division and are allocated 40MB of server space per account. Students needing help setting up their web site and/or web page can contact the TTUHSC Information Services in Lubbock at (806) 743-2870 for assistance. For more information and/or instructions on obtaining student web space, go to the Student Web Server page.
While student web sites and/or web pages are considered “unofficial,” the quality of the information published will still affect the reputation and image of TTUHSC. To prevent any negative impact to the Institution, the following web publishing standards have been established for student web sites and/or web pages:
- All student web sites and/or web pages must comply with the TTUHSC Acceptable Use Policy.
- TTUHSC will maintain and support the central web environment. Students are responsible for editing, uploading, debugging, and maintaining the content of their own sites and/or page.
- Texas Tech logotypes and any other official logos may only be used in web documents by schools, departments, and administrative areas. Unofficial web sites and/or web pages are not allowed to display any official logotypes.
- All web publishers/authors must abide by the copyright laws, regardless of whether the site/page is an official or unofficial one. Refer to the Web Use and Copyright Section for more detailed guidelines.
- Student web sites and/or web pages are considered “unofficial” and must be identified as such with disclaimer notices. All unofficial web sites and/or web pages must prominently display the Notice of Disclaimer for Unofficial Web Sites/Pages.
- To avoid unnecessary scrolling, all web sites and/or web pages should be sized no larger than 1024 x 768 pixels. The best practice is to design the page no larger than 900 pixels wide.
- Graphics should be in the GIF, JPEG/JPG, or PNG format with a maximum resolution of 72 dpi/ppi. Higher resolution graphics will make the site/page unnecessarily slow to load. If the graphic needs to be resized or resampled, a graphic program should be used rather than manipulating it through the HTML graphics size elements to ensure that the graphic will remain clear, crisp, and fast to download. For the best quality, it is recommended using the original graphic to modify then re-export as a GIF or JPG as necessary.
- Include Alt Tag descriptions when using graphics to ensure persons unable to view the graphic or persons using a text browser will be able to understand and navigate the site and/or page.
-
All student web sites and/or web pages should include a footer section that provides:
- A link to the TTUHSC home page
- The site/page owner’s name and email address
- Notice of Disclaimer For Unofficial Pages
These necessary footer codes may be found at Student Web Server page.
- Personal sites and/or pages will be removed 6 months after a student’s last semester at TTUHSC, unless special arrangements are made between the student and Information Services.
For questions or comments regarding these requirements, contact it.webmaster@ttuhsc.edu.
Below is a list of recommended design and procedural standards for student web sites and/or web pages:
- Before making any document public, spell check, and proof read first.
- Update contents regularly and check all links to ensure they are in working order.
- Avoid using large graphics. It will make the page load time unnecessarily long. Consider, instead, using a thumbnail where appropriate. If linking to large files or graphics, add a warning statement to prepare the user for the extended load time.
- Use a template or style sheet to ensure visual consistency across the web site and/or web page.
- Provide a link to the parent page on all supporting pages.
- Avoid browser-specific elements.
All web accounts will be subject to monitoring and audits by the I.T. Division for compliance with the policies contained herein. TTUHSC reserves the right to remove any web site and/or web page found to be in violation of TTUHSC, Federal, State, and/or local rules, policies, or procedures. A removal notification will be sent out to the registered web publisher 30 days before the site and/or page is removed and a second notice will follow 10 days prior to the removal date. However, a site and/or page may be removed immediately with the approval of the CIO.
9.2. TTUHSC WEB PUBLISHING STANDARDS
Web content should be in the best interest of TTUHSC and not conflict with the mission of the Institution. TTUHSC encourages its schools, departments, and administrative areas to utilize web publishing whenever possible to accomplish their goals and support the mission of the Institution.
The quality of the information published on the web directly affects the reputation and image of TTUHSC. In order to prevent any negative impact to the Institutional reputation and image, the following Institutional web publishing standards should be observed:
- The department head or their designee within the school, department, or administrative area must approve all official web publications prior to publication.
- The content and links of all web sites and/or web pages are the responsibility of the web author and their respective departments and/or organizations and should be reviewed/updated on a recurring basis according to the guidelines set forth by the Web Strategy Council to ensure their accuracy.
Sites and/or pages that are not regularly maintained or whose content is deemed outdated by the Assistant VP of Information Services may be subject to removal. A removal notification will be sent out to the registered web publisher 30 days before the site and/or page is removed and a second notice will follow 10 days prior to the removal date. However, a site and/or page may be removed immediately with the approval of the CIO.
- Texas Tech logos are legally protected trademarks and unauthorized use of these trademarks is prohibited. The use of Texas Tech logotypes must remain consistent to provide a strong Institutional identity across the Internet. All TTUHSC Official Seals and Logos for the website and web pages are implemented in the templates and layouts of the Luminis Content Management System. Altering the logos and lock-ups are prohibited.
- Web publishers/authors must take into account and abide by the appropriate copyright laws. Refer to the Web Use And Copyright Section for more detailed guidelines.
- Official web sites and/or web pages should not contain links to sites and/or pages devoted to individual hobbies or interests.
- TTUHSC encourages students and student organizations to publish web sites and/or web pages. These web sites and/or web pages are considered unofficial and must be identified as such by displaying the Notice of Disclaimer for Unofficial Web Sites/Pages in the footer section on the site/page.
- When implementing frames-based web sites and/or web pages, a text or non-frames version of the web site and/or web page shall also be implemented. The entry point shall contain the option to view the frames or text/non-frames version of the web site and/or web page. The text/non-frames version content must be updated prior to updating the frames-based version.
In accordance with the State of Texas Web Publishing Standards, framed sites and/or pages must not contain any Priority 1 or Priority 2 errors. See the State of Texas Web Publishing Standards for more information.
Additionally, web sites and/or web pages must not contain any Priority 1 or Priority 2 errors and must comply with the W3C Guidelines for HTML Usage.
- The following elements are required for all Texas Tech University Health Sciences Center web sites and/or web pages:
- Official sites and/or pages must include an identifier that associates it with TTUHSC which includes the TTUHSC logo, title text that identifies the site and/or page. Refer to the Web Site Visual Elements Standards for more information.
- Unofficial web sites and/or web pages, such as student organization or student personal sites and/or pages must be identified as "unofficial” and must display the Notice of Disclaimer for Unofficial Web Sites/Pages.
- Web sites and/or web pages must identify a contact person who is responsible for the content of the material. That person's name, e-mail address and school, department, or administrative area should be included at the bottom of the web site and/or web page.
- Official web sites and/or web pages must display the Notice of Disclaimer of Liability for Official Web Sites/Pages and comply with the requirement listed in the Web Site Visual Elements Standards.
- For additional requirements, see Section 9.8 for the State of Texas Web Publishing Standards.
9.3. WEB SITE VISUAL ELEMENTS STANDARDS
All TTUHSC web sites and/or web pages are expected to adhere to the highest level of quality and abide by these web publishing guidelines.
- TTUHSC web sites are expected to follow the zone layout guidelines presented in Section 9.4 and comply with the color and typography standards for web sites that are outlined in the Visual Identity Guidelines. For the text on the web sites, the font should be Arial. The Visual Identity Guidelines are implemented in the templates and layouts of the Luminis Content Management System.
- TTUHSC web sites and web pages should be designed to fit a 1024 x 768-screen resolution. In order to comfortably fit this size screen with no side scrolling, it is recommended that the layout should fit within the width of 900 pixels.
- All graphics that are used on the web sites and/or web pages must be formatted as follows:
- Graphics Interface Format (GIF), PNG, or Joint Photographic Experts Group (JPEG/JPG) file formats only. (GIF is a graphic file format that uses indexed color graphics and supports up to 256 colors with lossless compression. It is best used for flat images. JPEG/JPG is a graphics file format typically used to display photo-realistic pictures that contain thousands or millions of colors.)
- Maximum resolution of 72 dots-per-inch (dpi) or pixels-per-inch (ppi) for each graphic. (DPI and PPI is a measure of sharpness or density of illuminated points on a display screen.) Higher resolution graphics will make the download time unnecessarily long. Alternatively, a thumbnail may be used as a link to a separate higher resolution image.
- All TTUHSC Official Seals and Logos for the website and web pages are implemented in the templates and layouts of the Luminis Content Management System. Altering the logos and lock-ups are prohibited. The logos and lock-ups must be obtained from Official Identities area of the Visual Identity Guideline web site for print and other uses.
- When sizing graphics, a graphic program should be used to resize and resample the graphic file, rather than using the HTML graphic size elements for this purpose. This will ensure that the graphic will be clear, crisp, and does not take an inordinate amount of time to download. For the best quality, it is recommended using the original graphic to modify then re-export as a GIF or JPG as necessary.
9.4. CHANGE MANAGEMENT PROCEDURES FOR OFFICIAL TTUHSC WEB PAGES/SITES
Templates have been used to manage and maintain the website layout and navigation. Within a web page, a specific command can be used that will insert the contents of another file (the include file) into that web page. This is especially useful when template components, such as headers, footers, and navigational elements, are the same on a number of pages throughout a Web site. Using include files allows a programmer to only modify the include file to change a template element, instead of updating every individual Web page. Include files have been used primarily to maintain consistent navigation.
The web design attempts to maintain a consistent navigation. To this end, much of the navigation has been integrated on related pages. Navigational integration exists in situations where a navigational set is deemed important enough to be repeated from page to page. An example of this is the integration of HSC resources and other global navigation into every page. At the department level, integrated navigation exists for that department only. In order to manage and maintain the integrated navigation, include files have been utilized.
Within the templates, areas have been designated as “not editable” and “editable”. “Editable” areas are controlled by the appropriate content managers unless it is noted differently in this procedure. “Not editable” areas and include files that are used for integrated global navigation are controlled primarily by the Web Strategy Council and their appointed work groups unless it is noted differently in this procedure.
Development and Oversight
An integrated information environment that enhances education, research and patient care at TTUHSC requires resources dedicated to the development, implementation, and support of TTUHSC’s Web Presence. The development and oversight of TTUHSC’s Web Presence including the web sites, the portal, and content management will be under the leadership of the Web Strategy Council. One member will be appointed to the Web Strategy Council by the:
- President,
- Executive Vice President for Finance and Administration,
- Executive Vice President for Academic Affairs and Dean of Graduate School of Biomedical Sciences,
- Vice President for Diversity and Multicultural Affairs,
- Vice President for Information Technology and CIO,
- Vice President for Communications and Marketing,
- Vice President for Rural and Community Health,
- Dean of the School of Allied Health Sciences,
- Dean of the School of Medicine,
- Dean of the School of Nursing,
- Dean of the School of Pharmacy,
- Assistant Vice President for Finance and Administration, Amarillo,
- Assistant Vice President for Finance and Administration, El Paso,
- Assistant Vice President for Finance and Administration, Permian Basin, and
- TTUHSC Student Government Association President.
The CIO or his designee will chair the Web Strategy Council. The Web Strategy Council will meet on a quarterly basis or more frequently at the call of the CIO or his designee. The Web Strategy Council will provide the leadership and expertise needed for TTUHSC to develop a coordinated web strategy. Under the direction of the CIO, the Council will serve as the advisory body reporting to the I.T. Board of Directors to:
- Define the goals and objectives for the web site,
- Create web policies and standards,
- Recommend procedures to ensure compliance with web policies and standards,
- Create a strategically integrated web environment for TTUHSC,
- Coordinate web activities throughout TTUHSC,
- Provide seamless access to information and services throughout the web domain,
-
Provide direction and governance for the HSC Luminis Web Portal,
- Recommend new HSC and Texas Tech channels and enhancements to the project prioritization committees
- Recommend new HSC links
- Evaluate other institutions’ Portals on an ongoing basis for content and usage ideas
- Review and approve/deny requests for channels and links within the portal made by HSC entities
- Recommend appointments of specific content organization groups when needed,
- Approve Tier 2 and lower template designs,
- Define site development and maintenance responsibilities for TTUHSC web sites through the recommendation of appointments of content contributors and content managers for each department, school and campus,
- Establish design and content lifecycles, and
- Provide an Institutional approach to skills development and the acquisition of software tools.
The current lifecycles as approved by the Web Strategy Council on June 13, 2006 are:
- Design - The current structure and navigation will begin to be reviewed in 2 years.
- Content - All content will be reviewed at least yearly.
- Central Column - The middle content area on the Institutional home page, that includes the “From Here It’s Possible,” “Prepare for Your Future,” and “Make an Impact” areas, will be reviewed every 6 months.
Modifications To “Not Editable” Areas In All Templates
Modifications to the “not editable” areas of the templates are managed by the following process:
- Design is approved by the President’s Executive Council (PEC), the Web Strategy Council provides leadership in development and oversight, and Information Services maintains design and layout.
- The design of the web site will be reviewed on a recurring basis as defined by the Web Strategy Council.
Institutional And Campus Home Page Management - “Editable” Areas
The current web design for TTUHSC is based upon the zone layouts described in this section of the I.T. Policies.

Because the Institutional and Campus home pages represent the entire TTUHSC community, quality assurance is necessary to retain the integrity of the Institution’s identity. Therefore, modifications to the “editable” areas on these pages are managed by the following process:
Zone 4 - “Prepare for Your Future” and “Make an Impact” and Zone 5 - News and Announcements and Features Areas
The Office of Communications & Marketing (OCM) at the Institution or the campus manages the information and marketing aspect of these areas. All text, photos, and links must be submitted to OCM for approval prior to posting.
All other zones contain “not editable” areas only:
Zone 1 - Logo
Zone 2 - Search
Zone 3 - Audience Menus and Health Science Center Menus
Zone 6 - Footer
Key Public Entry Point Page Management- “Editable” Areas

A key public entry point is defined as a web page that is specifically designed for members of the general public to access official Institution information. TTUHSC has designated the following as key public entry points:
- Audience home pages,
- School home pages, and
- Offices and other administrative areas.
Key public entry points represent high profile areas of the TTUHSC web, thus quality assurance is necessary to retain the integrity of the Institution’s identity. At these levels, upper level navigational elements are interconnected. The interlocking nature of this navigation ensures consistent and up-to-date access to high-profile information. Modifications to “editable” areas on key public entry points are managed by the following process:
-
Zone 3A and 5A - Audience/School/Office or Administrative area navigation
- Each entity is responsible for modifications to their navigation area.
-
Zone 5B - Audience/School/Office or Administrative area Announcements or news
- Each entity is responsible for modifications to their navigation area.
-
Zone 4 - Facts at a Glance
- Each entity is responsible for managing the content of this area. All photos and quotes must be submitted to the respective OCM for approval prior to posting.
-
All other zones contain “not editable” areas only:
- Zone 1 - Logo
- Zone 2 - Blank
- Zone 3B - Audience Menus and Health Science Center Menus
- Zone 5C - Search
- Zone 6 - Footer

Because the sub pages are connected to their key public entry points, quality assurance is necessary to retain the integrity of the Institution’s identity and navigation. Modifications to the “editable” areas on sub pages are managed by the following process:
-
Zone 3A & 3C - Audience/School/Office or Administrative area navigation
- Includes entities such as Administration, Human Resources, Libraries, News & Events, and Research.
- Each entity is responsible for modifications to their navigation area.
-
Zone 4 –
- This zone is reserved for the page content.
- Content owners are responsible for maintaining the content of each sub page.
- All content must comply with TTUHSC Operating Policies and Procedures.
-
Zone 6A –
- This zone includes the contact information specific to that sub page.
- The contact information portion of this zone is the responsibility of the content owner.
-
Zone 7 –
- This zone includes the Institutional global navigation. An entity may append to the end of the Contact Info and Site Maps lists with links to their respective contact information and site map.
-
Zone 8 –
- This zone is used for navigational breadcrumbs. HSC Home is built in the template to always appear as the first part of breadcrumb navigation on a sub page.
- Subsequent links should reflect the hierarchy of preceding pages, but should never contain the link of the page being displayed.
- Each entity is responsible for maintaining its breadcrumbs.
-
All other zones contain “not editable” areas only:
- Zone 1 - Logo
- Zone 2 - Blank
- Zone 3B - Audience Menus and Health Science Center Menus
- Zone 5C - Search
- Zone 6B - Footer
General Process For Web Content Management
The purpose of web content management is to preserve the integrity of the TTUHSC web site while maintaining accurate and up-to-date subject matter.
Web management is about facilitating and encouraging the use of the web. This means finding a way to enable non-technical staff to publish web-based materials without too much effort, and yet ensuring quality content that will be useful and effective. Web content management addresses the following questions:
-
Who has access to publishing on the web and how is access granted and managed?
- The Deans, Vice Presidents, Chairs, and Department Heads will appoint content managers and identify content contributors for each campus, school, and department. Information Services will maintain a database of all individuals who have been granted access to contribute and manage content on the web. Information Services will also periodically monitor the compliance of the sites on the TTUHSC web to ensure that they are being maintained in a manner that maintains the integrity of the template design. Anyone not maintaining the integrity of the templates or making unauthorized changes to the design may have their access revoked. After the first or second occurrence, a warning will be sent out to the registered individual and retraining will be scheduled if needed. All access will be revoked upon the third occurrence. However, access may be revoked immediately with the approval of the CIO upon consultation with the appropriate Dean or Vice President.
-
What type of materials can be published?
- Generally, materials such as word docs, pdf’s, excel spreadsheets, text and images may be published. However, all content must comply with the standards set forth in this document and with the TTUHSC Operating Policies and Procedures.
-
Who is responsible for content and maintenance?
- Accountability for high quality content on TTUHSC web sites is a shared responsibility. Each academic or administrative unit will be required to develop and maintain high-quality, up-to-date, easily navigated information highlighting its programs, faculty/staff, services, policies, and procedures.
- Designated content managers are responsible for maintaining accurate and up-to-date subject matter for web pages in their area.
- Information Services will periodically conduct reviews to insure that web content and brand identity is being kept up to date. Content managers may be contacted in instances where it is noted that content has not been reviewed in the past 12 months. Sites and/or pages that are not regularly maintained are subject to removal. A removal notification will be sent out to the registered web publisher 30 days before the site and/or page is removed and a second notice will follow 10 days prior to the removal date. However, a site and/or page may be removed immediately with the approval of the CIO upon consultation with the appropriate Dean or Vice President.
-
What tools are used to create and edit web content?
- Non-technical content managers will use the content management system to create and edit web content.
- Technical content managers will also use the content management system to create and edit web content. Technical users are also allowed to use such tools as Macromedia Dreamweaver, Visual Studio.Net, etc.
- All content managers will also be required to use the HSC Web Version Control System for maintenance, publishing, and versioning control of web applications. Database driven applications or content will utilize Microsoft SQL Server databases. No other database systems (MS Access, mySQL, etc.) will be allowed on the production web environment without prior approval of the Assistant Vice President of Information Services.
-
Training and technical support required?
-
Before content managers are given access to their site, they must be trained by Information Services on the following:
- Use of the Content Management System.
- Use of the HSC Web Version Control System and the TTUHSC design templates.
- Use of the Microsoft SQL Server test and production environments, if used.
- Use of the design CSS and properly applying style classes as defined in the design stylesheets.
- Coding valid XHTML.
- Complying with American Disability Act (ADA) standards.
- Texas Administrative Code (TAC) compliance.
-
Before content managers are given access to their site, they must be trained by Information Services on the following:
-
How do I make changes?
-
Definitions:
- Test server - this is the server where all modifications are made and tested prior to moving them to the production server. The test server is only accessible from within the TTUHSC network.
- Production server - this is the live, publicly accessible version of the web site (http://www.ttuhsc.edu)
- All changes to web content are to be made and thoroughly tested on the Institutional test server.
- All content managers must conduct the “Pre-Publishing Checks” listed below prior to publishing any content from test to production.
- Access to content on the test servers and the ability to publish to the production servers will be controlled through authentication that utilizes eRaider.
-
Definitions:
-
Pre-Publishing Checks
-
Before publishing a content modifier must:
- Thoroughly review and test all changes.
- Verify that all links within the content are valid.
- Spell check all pages.
-
Before publishing a content modifier must:
-
After publishing, all modifiers must:
-
Run the web page through Watchfire’s Bobby™ using the Advanced Options setting: http://bobby.watchfire.com/bobby/html/en/advanced.jsp
- Enter the full URL of the page that was published.
- Select Priority 1 Only under the Web Content Accessibility Guidelines 1.0.
- Click Submit.
- If there are any validation errors, correct and republish and validate again. For assistance, please contact your technical content modifier.
- Run the same steps as above but this time with the U.S. Section 508 Guidelines checked instead of Priority 1 Only before submitting.
- Validate the published page for valid XHTML by using the W3C’s Markup Validation Service using default settings: http://validator.w3.org/detailed.html.
-
Run the web page through Watchfire’s Bobby™ using the Advanced Options setting: http://bobby.watchfire.com/bobby/html/en/advanced.jsp
-
Publishing from Test to Production
- The HSC Web Version Control System will be used to publish content from Test to Production.
- Training on the use of this system will be provided by Information Services.
9.5. INFORMATION SERVICES CODING STANDARDS, SECURITY, AND AUDIT CONTROLS
- All application development including web applications will have audit capabilities that will allow the construction of a transaction record of activities.
-
All developers will be familiar with and follow the standards and practices outlined in the following Microsoft Developers Network Resources:
- Building Secure ASP.NET Applications: Authentication, Authorization, and Secure Communication
- Building Secure ASP.NET Applications: Authentication, Authorization, and Secure Communication – Data Access Security
- Improving Web Application Security: Threats and Countermeasures
- Patterns & Practices Security Guidance for Applications Index
- An Overview of Security in the .NET Framework
- Defend Your Apps and Critical User Info with Defensive Coding Techniques
- .NET Security
-
All developers will periodically review the materials at the following sites as part of their training and skills development.
- MSDN Security Site - http://msdn.microsoft.com/security/
- TechNet Security Site - http://www.microsoft.com/technet/security/default.mspx
- All developers will periodically participate in Microsoft Security Training Events as part of the on-going training and skills development. Available events can be located at: http://www.microsoft.com/events/security/default.mspx.
-
Typical Development Phases and Steps to follow (SDLC):
-
Planning
- Meet with department
- Gather requirements
-
Analysis/Design
- Content gathering by department
- Content organization
- Navigation organization
- Application design (User interface, etc.)
- Database design
-
Development/Testing
- Create content pages
- Content graphics
- Navigation implementation
- Application programming
- Database development
- IS testing
- Department testing
- Edits/modifications
- Re-test
-
Implementation
- IS approval
- Department approval
-
Move to production
- Content Pages
- Graphics
-
Database
- Database schema
- Data migration/creation
- Application pages
- Implement SSL (if applicable)
- Implement authentication (if applicable)
- Compliance review (TAC, accessibility, etc.)
- Security code review
- Post implementation testing/review
- Post implementation edits/modifications
- Final testing/review
- Final IS approval
- Final department approval
- Support/Maintenance
-
Planning
-
All developers will utilize the following tools:
- Test Environment -
Dreamweaver Check In/Check Out for static web page development/maintenance; and Visual Studio with Visual Source Safe for web application development/maintenance. - Production Environment -
All developers will publish to the production environment using the HSC Web Version Control System. - Luminis Content Management System -
All content contributors and managers will use this system to develop, maintain, and publish static content to the TTUHSC web sites.
- Test Environment -
-
Prior to writing any code or purchasing any software/system at TTUHSC, all developers will:
- Document the requirements and functionality of a development project.
- Review the documented requirements and functionality with the individual(s) or department requesting the development project.
- Insure that they have a thorough understanding of the development project requirements and functionality.
- Obtain central IS administrative approval to begin the coding process.
- All developers will thoroughly test all code prior to implementation.
- All developers will require the requesting individual(s) or department to perform extensive testing of all code prior to implementation.
-
Developed projects or purchased software/systems will not be moved into the production environment until:
- All code has been thoroughly reviewed and tested. This includes conducting compliance and security code reviews.
- Approval has been obtained from the requesting individual(s) or department and a time frame for production implementation has been agreed upon.
-
Production implementation procedures and requirements have been outlined. These include, but are not limited to:
- Changes to IIS.
- Database structure and data migration.
- Access privileges
- Approved by central IS Management.
-
Web publishing from Test to Production
- The HSC Web Version Control System will be used to publish content from Test to Production for web applications.
- The content management system will be used to publish static content from Test to Production.
- Training on the use of these systems will be provided by Information Services.
9.6. E-COMMERCE APPLICATIONS
- All e-Commerce applications must be approved by the Assistant Vice President for Information Services.
- All e-Commerce applications must utilize the Texas Tech University System eCommerce framework.
- All TTUHSC web pages that access the Texas Tech University System e-Commerce framework must be hosted in the central Data Center and will undergo periodic PCI compliance scanning.
- The development of all e-Commerce applications will follow the applicable guidelines outlined in Sections 1.4.20 and 9.5.
9.7. WEB USE AND COPYRIGHT STANDARD
The use of TTUHSC web and computing resources is a privilege granted by TTUHSC and the State of Texas and is intended to further the educational missions of the Institution. Each school, department, administrative area, and user is responsible for using the TTUHSC web and computing resources ethically, courteously, and lawfully in accordance with the Acceptable Use Policy.
This Institution is committed to making the TTUHSC web a premier part of the Internet that upholds the highest ethical standards and abides by Institutional policies and State and Federal statutes regulating the use of the Internet and protecting the copyrights of others. Web authors are responsible for ensuring the information they publish is free from copyright restrictions and complies with the guidelines set forth in this document.
9.8. STATE OF TEXAS WEB PUBLISHING STANDARDS
All official TTUHSC web sites and/or web pages must comply with the Texas Administrative Code Section 206 - State Web Sites. In September 2002, the Governor's Office announced the launch of a Texas Homeland Security web site which provides Texans with links to specialized homeland defense-related Internet resources operated by state agencies and the federal government. The Governor's office has requested that all state agency web sites link to the new Texas Homeland Security web site. This site is also part of the HSC footer.
The composition of the footer on the TTUHSC web site is incorporated into the Luminis Content Management System. Information Services will maintain the links within the footer.
Information pertaining to TAC § 206 - State Web Sites and the links that are required for the TTUHSC footer are available on the TTUHSC TAC Information page.