Standards for content published on ELCA.org
The suggestions and requirements set forth in this document reflect those standards the staff of the ELCA Communication Services
and Information Technology
feel are necessary for adequate maintenance and uniformity throughout the ELCA Web site, as affirmed by the churchwide organization's TechnoTeam.
- All pages are to be fully viewable at 1024x768 screen resolution without a horizontal scroll. The established page layout in Sitecore Content Management System (Sitecore) is 980 pixels wide. Page layouts must be able to be maintained in Sitecore, the standard table should not exceed 528 pixels if used in a 3 column (nav, body, sidebar) layout. Download a PDF of the 4 types of page layouts with pixel measurements.
- Essential content from Web pages should not be cut off when printed on an 8.5"x11" portrait page.
- The use of frames is prohibited.
- Page developers should test pages in Microsoft Internet Explorer, Apple Safari and Mozilla Firefox before publishing.
- All images used as navigation are required to have alternative text describing the link. Graphics loaded into Sitecore's Media Library are required to have ALT text as well. ALT text should also be copied into the TITLE field in Sitecore's Media Library so it displays in Firefox.
- The use of both "keywords" and "description" meta tags is required on all sites' entry point.
- Descriptive titles are required on all pages -- they are generated in Sitecore automatically.
- No contract web designer advertising, taglines, copyrights, or vendor page links are allowed on any page on the ELCA site.
- New pages should be developed in Sitecore. Any exception must be approved by the ELCA.org Managing Editor and the ELCA Web Manager.
- Navigation should clearly indicate the choice being selected by the browser (example: roll-over highlight or arrow).
- All unit or workgroup "sub-sites" must contain at least one easily accessible e-mail link to someone within the unit who is responsible for the information presented. For this purpose, units should consider a unit e-mail box with appropriate procedures in place to be sure the mail is read and responded to daily. An e-mail form on the page is an ideal way to encourage feedback and facilitate response, units should use this link format for e-mail addresses within the ELCA churchwide office LAN network:
- When providing an e-mail link on a Web page, the link should be from the person’s full name. If the e-mail address needs to be spelled out, please do not hyperlink it, so that any underlines in e-mail addresses are clearly understandable.
- Material on the ELCA site is copyrighted and owned by the sponsoring unit, use of any materials by a third party should be addressed by that unit and Communication Services.
- When referring to Adobe Acrobat (PDF) files, use the icon found at www.elca.org/~/media/images/common%20images/pdficon.gif. If this page contains multiple PDFs, consider including the "Get Adobe Acrobat Reader" sidebar (located in Sidebars > Standard > Get Adobe Acrobat Reader) for up-to-date download instructions.
- The project manager or producer of pages contemplating use of plug-in technology other than Adobe Acrobat (i.e. RealAudio, QuickTime, Shockwave, Flash, etc.) is required to notify the ELCA Web Manager before making any decisions, in order to assure compatibility with ELCA servers and support.
- Visible page hit counters are not allowed.
- Visible "Last Modified..." dates are not allowed.
- Projects that require the use of a server-side database engine or application must be developed in cooperation with ELCA IT programming staff.
- Keep image files sizes to a minimum while preserving image quality. Images displayed on the Web should be saved at screen resolution (72 dpi).
- Images should not be resized using HTML height and width attributes. Instead, resize images in your image-editing application (i.e. Photoshop Elements) and place them into the HTML page at their exact size.
- Font considerations for HTML text is pre-determined by the Cascading Style Sheet associated with Sitecore and is limited to Helvetica or Arial (sans serif). This does not include fonts that are used for graphic files.
- Add redundant text links when using an image map.
- Refrain from using a real person's signature represented in a graphic format for security reasons.
- Additional information for Sitecore editors on best practices, Sitecore training and tips is available on the ELCA Intranet under "Sitecore Training Information."
- Advanced Sitecore coding and formatting techniques can be found at http://www.elca.org/sitecorestyle.
Questions? Contact the ELCA Web Manager. Contact the Managing Editor, ELCA.org.