Difference between revisions of "Template:Testchecklist"
Jump to navigation
Jump to search
(Created page with " <noinclude>Een template maken die een parameter mee krijgt? level=basic -> retourneert bulletpoints die dit level in de standaard cheklist behelzen, level=medium -> extra set bu...") |
|||
Line 1: | Line 1: | ||
+ | <noinclude>[[Category:2Value wiki]] {{Ti2w}} [[Category:Template|{{PAGENAME}}]] | ||
+ | </noinclude><!-- | ||
+ | --> | ||
+ | {{#if: {{{level}}}=basic | ||
+ | ==Frontend tests== | ||
+ | : 1) valideert de html en de css | ||
+ | : 2) hoe is de front-end performance | ||
+ | : 3)cms specific test: | ||
+ | :: joomla | ||
+ | :::1) zijn dir rechten goed? | ||
+ | :::2) is htaccess enabled | ||
+ | ::drupal | ||
+ | :::1) geeft status report foutmeldingen? | ||
+ | : 4) kan men inloggen? zijn de userrechten voor tenminste 1 redacteur geregeld | ||
+ | }} | ||
+ | |||
+ | ==Pre-Launch== | ||
+ | ===Content and Style=== | ||
+ | *Typography and layout | ||
+ | **Check for incorrect punctuation marks, particularly apostrophes, quotation marks and hyphens/dashes | ||
+ | **Check headings for where you could potentially use ligatures | ||
+ | **Check for widow/orphan terms in important paragraphs | ||
+ | *Spelling and grammar | ||
+ | *Consistency | ||
+ | **Capitalisation (especially of main headings) | ||
+ | **Tense/Style of writing | ||
+ | **Recurring/common phrases (e.g. ‘More about X’ links) | ||
+ | **Variations in words (e.g. Websites vs Web Sites, or UK vs US spelling) | ||
+ | **Treatment of bulleted lists (e.g. periods or commas at end of each item) | ||
+ | *Check for hard-coded links to staging domain (i.e. ensure all links will change to ‘live’ URL/domain when site is launched) | ||
+ | *Ensure no test content on site | ||
+ | *Check how important pages (e.g. content items) print | ||
+ | *For re-designs, ensure important old/existing URLs are redirected to relevant new URLs, if the URL scheme is changing | ||
+ | *Check all ‘Hidden Copy’ (e.g. alt text, transcriptions, text in JavaScript functions) | ||
+ | ===Standards and Validation=== | ||
+ | {{Who|Developer|Webmaster||||}} | ||
+ | *Accessibility | ||
+ | *HTML validation -> http://validator.w3.org/ | ||
+ | *JavaScript validation | ||
+ | *CSS validation -> http://jigsaw.w3.org/css-validator/ | ||
+ | |||
+ | ===Search Engine Visibility, SEO and Metrics=== | ||
+ | *Page Titles are important; ensure they make sense and have relevant keywords in them. | ||
+ | *Create metadata descriptions for important pages. | ||
+ | *Check for canonical domain issues (e.g. variations in links to http://site.com http://www.site.com http://www.site.com/index.html should be reduced to a single consistent style) | ||
+ | *Ensure content is marked-up semantically/correctly (HTML-tags, etc.) | ||
+ | *Check for target keyword usage in general content | ||
+ | *Check format (user/search engine friendliness) of URLs | ||
+ | *Set up Analytics, FeedBurner, and any other packages for measuring ongoing succes <br/> -> http://www.google.com/analytics (use twovalue@gmail.com as username. See http://service.2value.nl for password) | ||
+ | *Create an XML Sitemap <br/>-> consider the Joomla! extension [http://extensions.joomla.org/extensions/structure-a-navigation/site-map/3066 Xmap] | ||
+ | *Configure Google Webmaster Console and Yahoo! Site Explorer <br/>-> http://www.google.com/webmasters/tools (use twovalue@gmail.com as username. See http://service.2value.nl for password) | ||
+ | |||
+ | ===Functional Testing=== | ||
+ | *Check all bespoke/complex functionality | ||
+ | *Check search functionality (including relevance of results) | ||
+ | *Check on common variations of browser (Internet Explorer, Firefox, Safari, Chrome etc.), version (6, 7, 2.2, 3.1 etc.) and platform (Windows, OSX, Linux) | ||
+ | *Check on common variations of Screen Resolution | ||
+ | *Test all forms (e.g. contact us, blog comments), including anti-spam features, response emails/text, etc. | ||
+ | *Test without JavaScript, Flash, and other plug-ins | ||
+ | *Check all external links are valid -> [[Associate:Checklist/linkcheckers|lees meer]] | ||
+ | |||
+ | ===Security/Risk=== | ||
+ | *Configure backup schedule, and test recovery from backup. | ||
+ | *Protect any sensitive pages (e.g. administration area) | ||
+ | *Use robots.txt where necessary | ||
+ | *Security/Penetration test | ||
+ | *Turn-off verbose error reporting | ||
+ | *Check disk space/capacity | ||
+ | *Set-up email/SMS monitoring/alerts (e.g. for errors, server warnings); consider internal and external monitoring services | ||
+ | ===Performance=== | ||
+ | {{Who|Webmaster|Developer|Templatebuilder||}} | ||
+ | *Load test | ||
+ | *Check image optimisation <br/>-> [http://www.smushit.com/ysmush.it/ All Smush.it] | ||
+ | *Check and implement caching where necessary <br/>-> [http://www.nonumber.nl/extensions/cachecleaner NoNumber Cache Cleaner] | ||
+ | *Check total page size/download time <br/>-> Firefox plugin Yslow | ||
+ | *Minify/compress static (JavaScript/HTML/CSS) files <br/>-> use compress plugins | ||
+ | *Optimise your CSS: use short image paths; make full-use ‘cascading’ nature of CSS, etc. <br/>-> use compress plugins | ||
+ | *Check correct database indexing | ||
+ | *Check configuration at every level (Web server, Database, any other software e.g. Content Management System) | ||
+ | *Configure server-based logging/measurement tools (e.g. database/web server logging) | ||
+ | |||
+ | |||
+ | *Lees meer hierover in de SlideShare presentatie van [[user:hkuijpers|Hans Kuijpers]] over [http://www.slideshare.net/hans2103/site-performance-optimization-joomla Site Performance Optimization] | ||
+ | |||
+ | ===Finishing Touches=== | ||
+ | {{Who|Webmaster|Developer|Templatebuilder||}} | ||
+ | *Create custom 404/error pages <br/>-> consider the Joomla! extension [http://extensions.joomla.org/extensions/site-management/url-redirection/9989 Dynamic404] | ||
+ | *Create a favicon | ||
+ | ===Joomla! specific=== | ||
+ | * Remove testcontent from configuration.php | ||
+ | |||
+ | ==Post-Launch== | ||
+ | ===Marketing=== | ||
+ | {{Who|Marketing|||||}} | ||
+ | *Social Marketing: Twitter, LinkedIn, Digg, Facebook, Stumbleupon, etc. | ||
+ | *Submit to search engines | ||
+ | *Set-up PPC/Google Adwords where necessary | ||
+ | *Check formatting of site results in SERPs | ||
+ | ===Ongoing=== | ||
+ | {{Who|Marketing|Webmaster||||}} | ||
+ | *Monitor and respond to feedback (direct feedback, on Social Media sites, check for chatter through Google, etc.) | ||
+ | *Check analytics for problems, popular pages etc. and adjust as necessary | ||
+ | *Update content | ||
+ | |||
+ | For an updated list check -> http://www.boxuk.com/blog/the-ultimate-website-launch-checklist | ||
<noinclude>Een template maken die een parameter mee krijgt? level=basic -> retourneert bulletpoints die dit level in de standaard cheklist behelzen, level=medium -> extra set bullets per onderdeel, etc</noinclude> | <noinclude>Een template maken die een parameter mee krijgt? level=basic -> retourneert bulletpoints die dit level in de standaard cheklist behelzen, level=medium -> extra set bullets per onderdeel, etc</noinclude> |
Revision as of 15:05, 23 November 2010
Template:Testchecklist (talk, backlinks, edit)
Contents
Pre-Launch
Content and Style
- Typography and layout
- Check for incorrect punctuation marks, particularly apostrophes, quotation marks and hyphens/dashes
- Check headings for where you could potentially use ligatures
- Check for widow/orphan terms in important paragraphs
- Spelling and grammar
- Consistency
- Capitalisation (especially of main headings)
- Tense/Style of writing
- Recurring/common phrases (e.g. ‘More about X’ links)
- Variations in words (e.g. Websites vs Web Sites, or UK vs US spelling)
- Treatment of bulleted lists (e.g. periods or commas at end of each item)
- Check for hard-coded links to staging domain (i.e. ensure all links will change to ‘live’ URL/domain when site is launched)
- Ensure no test content on site
- Check how important pages (e.g. content items) print
- For re-designs, ensure important old/existing URLs are redirected to relevant new URLs, if the URL scheme is changing
- Check all ‘Hidden Copy’ (e.g. alt text, transcriptions, text in JavaScript functions)
Standards and Validation
→Who: - Developer (↔RES) - Webmaster
- Accessibility
- HTML validation -> http://validator.w3.org/
- JavaScript validation
- CSS validation -> http://jigsaw.w3.org/css-validator/
Search Engine Visibility, SEO and Metrics
- Page Titles are important; ensure they make sense and have relevant keywords in them.
- Create metadata descriptions for important pages.
- Check for canonical domain issues (e.g. variations in links to http://site.com http://www.site.com http://www.site.com/index.html should be reduced to a single consistent style)
- Ensure content is marked-up semantically/correctly (HTML-tags, etc.)
- Check for target keyword usage in general content
- Check format (user/search engine friendliness) of URLs
- Set up Analytics, FeedBurner, and any other packages for measuring ongoing succes
-> http://www.google.com/analytics (use twovalue@gmail.com as username. See http://service.2value.nl for password) - Create an XML Sitemap
-> consider the Joomla! extension Xmap - Configure Google Webmaster Console and Yahoo! Site Explorer
-> http://www.google.com/webmasters/tools (use twovalue@gmail.com as username. See http://service.2value.nl for password)
Functional Testing
- Check all bespoke/complex functionality
- Check search functionality (including relevance of results)
- Check on common variations of browser (Internet Explorer, Firefox, Safari, Chrome etc.), version (6, 7, 2.2, 3.1 etc.) and platform (Windows, OSX, Linux)
- Check on common variations of Screen Resolution
- Test all forms (e.g. contact us, blog comments), including anti-spam features, response emails/text, etc.
- Test without JavaScript, Flash, and other plug-ins
- Check all external links are valid -> lees meer
Security/Risk
- Configure backup schedule, and test recovery from backup.
- Protect any sensitive pages (e.g. administration area)
- Use robots.txt where necessary
- Security/Penetration test
- Turn-off verbose error reporting
- Check disk space/capacity
- Set-up email/SMS monitoring/alerts (e.g. for errors, server warnings); consider internal and external monitoring services
Performance
→Who: - Webmaster (↔RES) - Developer - Templatebuilder
- Load test
- Check image optimisation
-> All Smush.it - Check and implement caching where necessary
-> NoNumber Cache Cleaner - Check total page size/download time
-> Firefox plugin Yslow - Minify/compress static (JavaScript/HTML/CSS) files
-> use compress plugins - Optimise your CSS: use short image paths; make full-use ‘cascading’ nature of CSS, etc.
-> use compress plugins - Check correct database indexing
- Check configuration at every level (Web server, Database, any other software e.g. Content Management System)
- Configure server-based logging/measurement tools (e.g. database/web server logging)
- Lees meer hierover in de SlideShare presentatie van Hans Kuijpers over Site Performance Optimization
Finishing Touches
→Who: - Webmaster (↔RES) - Developer - Templatebuilder
- Create custom 404/error pages
-> consider the Joomla! extension Dynamic404 - Create a favicon
Joomla! specific
- Remove testcontent from configuration.php
Post-Launch
Marketing
- Social Marketing: Twitter, LinkedIn, Digg, Facebook, Stumbleupon, etc.
- Submit to search engines
- Set-up PPC/Google Adwords where necessary
- Check formatting of site results in SERPs
Ongoing
→Who: - Marketing (↔RES) - Webmaster
- Monitor and respond to feedback (direct feedback, on Social Media sites, check for chatter through Google, etc.)
- Check analytics for problems, popular pages etc. and adjust as necessary
- Update content
For an updated list check -> http://www.boxuk.com/blog/the-ultimate-website-launch-checklist
Een template maken die een parameter mee krijgt? level=basic -> retourneert bulletpoints die dit level in de standaard cheklist behelzen, level=medium -> extra set bullets per onderdeel, etc