Web design

Web design encompasses many different skills and disciplines in the production and maintenance of
websites. The different areas of web design include web graphic design; user interface design (UI design);
authoring, including standardised code and proprietary software; user experience design (UX design); and
search engine optimization. Often many individuals will work in teams covering different aspects of the
design process, although some designers will cover them all.[1] The term "web design" is normally used to
describe the design process relating to the front-end (client side) design of a website including writing
markup. Web design partially overlaps web engineering in the broader scope of web development. Web
designers are expected to have an awareness of usability and if their role involves creating markup then
they are also expected to be up to date with web accessibility guidelines.

Contents
History
1988–2001
The start of the web and web design
Evolution of web design
End of the first browser wars
2001–2012
2012 and later
Tools and technologies
Skills and techniques
Marketing and communication design
User experience design and interactive design
Progressive enhancement
Page layout
Typography
Motion graphics
Quality of code
Generated content
Static websites
Dynamic websites
Homepage design
Occupations
See also
See also
Related disciplines
Notes
External links
History

1988–2001

Although web design has a fairly recent history. It can be linked to

other areas such as graphic design, user experience, and multimedia
arts, but is more aptly seen from a technological standpoint. It has
become a large part of people's everyday lives. It is hard to imagine
the Internet without animated graphics, different styles of
typography, background, videos and music. Web design books in a store

The start of the web and web design

In 1989, whilst working at CERN Tim Berners-Lee proposed to create a global hypertext project, which
later became known as the World Wide Web. During 1991 to 1993 the World Wide Web was born. Text-
only pages could be viewed using a simple line-mode browser.[2] In 1993 Marc Andreessen and Eric Bina,
created the Mosaic browser. At the time there were multiple browsers, however the majority of them were
Unix-based and naturally text heavy. There had been no integrated approach to graphic design elements
such as images or sounds. The Mosaic browser broke this mould.[3] The W3C was created in October
1994 to "lead the World Wide Web to its full potential by developing common protocols that promote its
evolution and ensure its interoperability."[4] This discouraged any one company from monopolizing a
propriety browser and programming language, which could have altered the effect of the World Wide Web
as a whole. The W3C continues to set standards, which can today be seen with JavaScript and other
languages. In 1994 Andreessen formed Mosaic Communications Corp. that later became known as
Netscape Communications, the Netscape 0.9 browser. Netscape created its own HTML tags without regard
to the traditional standards process. For example, Netscape 1.1 included tags for changing background
colours and formatting text with tables on web pages. Throughout 1996 to 1999 the browser wars began,
as Microsoft and Netscape fought for ultimate browser dominance. During this time there were many new
technologies in the field, notably Cascading Style Sheets, JavaScript, and Dynamic HTML. On the whole,
the browser competition did lead to many positive creations and helped web design evolve at a rapid
pace.[5]

Evolution of web design

In 1996, Microsoft released its first competitive browser, which was complete with its own features and
HTML tags. It was also the first browser to support style sheets, which at the time was seen as an obscure
authoring technique and is today an important aspect of web design.[5] The HTML markup for tables was
originally intended for displaying tabular data. However designers quickly realized the potential of using
HTML tables for creating the complex, multi-column layouts that were otherwise not possible. At this time,
as design and good aesthetics seemed to take precedence over good mark-up structure, and little attention
was paid to semantics and web accessibility. HTML sites were limited in their design options, even more so
with earlier versions of HTML. To create complex designs, many web designers had to use complicated
table structures or even use blank spacer .GIF images to stop empty table cells from collapsing.[6] CSS was
introduced in December 1996 by the W3C to support presentation and layout. This allowed HTML code to
be semantic rather than both semantic and presentational, and improved web accessibility, see tableless web
design.
In 1996, Flash (originally known as FutureSplash) was developed. At the time, the Flash content
development tool was relatively simple compared to now, using basic layout and drawing tools, a limited
precursor to ActionScript, and a timeline, but it enabled web designers to go beyond the point of HTML,
animated GIFs and JavaScript. However, because Flash required a plug-in, many web developers avoided
using it for fear of limiting their market share due to lack of compatibility. Instead, designers reverted to gif
animations (if they didn't forego using motion graphics altogether) and JavaScript for widgets. But the
benefits of Flash made it popular enough among specific target markets to eventually work its way to the
vast majority of browsers, and powerful enough to be used to develop entire sites.[6]

End of the first browser wars

In 1998, Netscape released Netscape Communicator code under an open source licence, enabling
thousands of developers to participate in improving the software. However, these developers decided to
start a standard for the web from scratch, which guided the development of the open source browser and
soon expanded to a complete application platform.[5] The Web Standards Project was formed and promoted
browser compliance with HTML and CSS standards. Programs like Acid1, Acid2, and Acid3 were created
in order to test browsers for compliance with web standards. In 2000, Internet Explorer was released for
Mac, which was the first browser that fully supported HTML 4.01 and CSS 1. It was also the first browser
to fully support the PNG image format.[5] By 2001, after a campaign by Microsoft to popularize Internet
Explorer, Internet Explorer had reached 96% of web browser usage share, which signified the end of the
first browsers wars as Internet Explorer had no real competition.[7]

2001–2012

Since the start of the 21st century the web has become more and more integrated into peoples lives. As this
has happened the technology of the web has also moved on. There have also been significant changes in
the way people use and access the web, and this has changed how sites are designed.

Since the end of the browsers wars new browsers have been released. Many of these are open source
meaning that they tend to have faster development and are more supportive of new standards. The new
options are considered by many to be better than Microsoft's Internet Explorer.

The W3C has released new standards for HTML (HTML5) and CSS (CSS3), as well as new JavaScript
API's, each as a new but individual standard. While the term HTML5 is only used to refer to the new
version of HTML and some of the JavaScript API's, it has become common to use it to refer to the entire
suite of new standards (HTML5, CSS3 and JavaScript).

2012 and later

With the improvement of 3G and LTE internet coverage, large part of website traffic became mobile-
generated. This affected the web design industry, pushing it towards minimalistic, lightened and simplistic
style. In particular, the "Mobile first" approach emerged, which implies creating website design with
mobile-oriented layout first, and then adapting it to higher screen dimensions.

Tools and technologies

Web designers use a variety of different tools depending on what part of the production process they are
involved in. These tools are updated over time by newer standards and software but the principles behind
them remain the same. Web designers use both vector and raster graphics editors to create web-formatted
imagery or design prototypes. Technologies used to create websites include W3C standards like HTML
and CSS, which can be hand-coded or generated by WYSIWYG editing software. Other tools web
designers might use include mark up validators[8] and other testing tools for usability and accessibility to
ensure their websites meet web accessibility guidelines.[9]

Skills and techniques

Marketing and communication design

Marketing and communication design on a website may identify what works for its target market. This can
be an age group or particular strand of culture; thus the designer may understand the trends of its audience.
Designers may also understand the type of website they are designing, meaning, for example, that (B2B)
business-to-business website design considerations might differ greatly from a consumer targeted website
such as a retail or entertainment website. Careful consideration might be made to ensure that the aesthetics
or overall design of a site do not clash with the clarity and accuracy of the content or the ease of web
navigation,[10] especially on a B2B website. Designers may also consider the reputation of the owner or
business the site is representing to make sure they are portrayed favourably.

User experience design and interactive design

User understanding of the content of a website often depends on user understanding of how the website
works. This is part of the user experience design. User experience is related to layout, clear instructions and
labeling on a website. How well a user understands how they can interact on a site may also depend on the
interactive design of the site. If a user perceives the usefulness of the website, they are more likely to
continue using it. Users who are skilled and well versed with website use may find a more distinctive, yet
less intuitive or less user-friendly website interface useful nonetheless. However, users with less experience
are less likely to see the advantages or usefulness of a less intuitive website interface. This drives the trend
for a more universal user experience and ease of access to accommodate as many users as possible
regardless of user skill.[11] Much of the user experience design and interactive design are considered in the
user interface design.

Advanced interactive functions may require plug-ins if not advanced coding language skills. Choosing
whether or not to use interactivity that requires plug-ins is a critical decision in user experience design. If
the plug-in doesn't come pre-installed with most browsers, there's a risk that the user will have neither the
know how or the patience to install a plug-in just to access the content. If the function requires advanced
coding language skills, it may be too costly in either time or money to code compared to the amount of
enhancement the function will add to the user experience. There's also a risk that advanced interactivity
may be incompatible with older browsers or hardware configurations. Publishing a function that doesn't
work reliably is potentially worse for the user experience than making no attempt. It depends on the target
audience if it's likely to be needed or worth any risks.

Progressive enhancement

Progressive enhancement is a strategy in web design that puts emphasis on web content first, allowing
everyone to access the basic content and functionality of a web page, whilst users with additional browser
features or faster Internet access receive the enhanced version instead.
In practice, this means serving content through HTML and
applying styling and animation through CSS to the technically
possible extent, then applying further enhancements through
JavaScript. Pages' text is loaded immediately through the HTML
source code rather than having to wait for JavaScript to initiate and
load the content subsequently, which allows content to be readable
with minimum loading time and bandwidth, and through text-based
browsers, and maximizes backwards compatibility.[12]

As an example, MediaWiki-based sites including Wikipedia use

progressive enhancement, as they remain usable while JavaScript
and even CSS is deactivated, as pages' content is included in the The order of progressive
page's HTML source code, whereas counter-example Everipedia enhancement
relies on JavaScript to load pages' content subsequently; a blank
page appears with JavaScript deactivated.

Page layout

Part of the user interface design is affected by the quality of the page layout. For example, a designer may
consider whether the site's page layout should remain consistent on different pages when designing the
layout. Page pixel width may also be considered vital for aligning objects in the layout design. The most
popular fixed-width websites generally have the same set width to match the current most popular browser
window, at the current most popular screen resolution, on the current most popular monitor size. Most
pages are also center-aligned for concerns of aesthetics on larger screens.

Fluid layouts increased in popularity around 2000 to allow the browser to make user-specific layout
adjustments to fluid layouts based on the details of the reader's screen (window size, font size relative to
window etc.). They grew as an alternative to HTML-table-based layouts and grid-based design in both
page layout design principle and in coding technique, but were very slow to be adopted.[note 1] This was
due to considerations of screen reading devices and varying windows sizes which designers have no
control over. Accordingly, a design may be broken down into units (sidebars, content blocks, embedded
advertising areas, navigation areas) that are sent to the browser and which will be fitted into the display
window by the browser, as best it can. Although such a display may often change the relative position of
major content units, sidebars may be displaced below body text rather than to the side of it. This is a more
flexible display than a hard-coded grid-based layout that doesn't fit the device window. In particular, the
relative position of content blocks may change while leaving the content within the block unaffected. This
also minimizes the user's need to horizontally scroll the page.

Responsive web design is a newer approach, based on CSS3, and a deeper level of per-device specification
within the page's style sheet through an enhanced use of the CSS @media rule. In March 2018 Google
announced they would be rolling out mobile-first indexing.[13] Sites using responsive design are well
placed to ensure they meet this new approach.

Typography

Web designers may choose to limit the variety of website typefaces to only a few which are of a similar
style, instead of using a wide range of typefaces or type styles. Most browsers recognize a specific number
of safe fonts, which designers mainly use in order to avoid complications.
Font downloading was later included in the CSS3 fonts module and has since been implemented in Safari
3.1, Opera 10 and Mozilla Firefox 3.5. This has subsequently increased interest in web typography, as well
as the usage of font downloading.

Most site layouts incorporate negative space to break the text up into paragraphs and also avoid center-
aligned text.[14]

Motion graphics

The page layout and user interface may also be affected by the use of motion graphics. The choice of
whether or not to use motion graphics may depend on the target market for the website. Motion graphics
may be expected or at least better received with an entertainment-oriented website. However, a website
target audience with a more serious or formal interest (such as business, community, or government) might
find animations unnecessary and distracting if only for entertainment or decoration purposes. This doesn't
mean that more serious content couldn't be enhanced with animated or video presentations that is relevant
to the content. In either case, motion graphic design may make the difference between more effective
visuals or distracting visuals.

Motion graphics that are not initiated by the site visitor can produce accessibility issues. The World Wide
Web consortium accessibility standards require that site visitors be able to disable the animations.[15]

Quality of code

Website designers may consider it to be good practice to conform to standards. This is usually done via a
description specifying what the element is doing. Failure to conform to standards may not make a website
unusable or error prone, but standards can relate to the correct layout of pages for readability as well
making sure coded elements are closed appropriately. This includes errors in code, more organized layout
for code, and making sure IDs and classes are identified properly. Poorly coded pages are sometimes
colloquially called tag soup. Validating via W3C[8] can only be done when a correct DOCTYPE
declaration is made, which is used to highlight errors in code. The system identifies the errors and areas that
do not conform to web design standards. This information can then be corrected by the user.[16]

Generated content

There are two ways websites are generated: statically or dynamically.

Static websites

A static website stores a unique file for every page of a static website. Each time that page is requested, the
same content is returned. This content is created once, during the design of the website. It is usually
manually authored, although some sites use an automated creation process, similar to a dynamic website,
whose results are stored long-term as completed pages. These automatically created static sites became
more popular around 2015, with generators such as Jekyll and Adobe Muse.[17]

The benefits of a static website are that they were simpler to host, as their server only needed to serve static
content, not execute server-side scripts. This required less server administration and had less chance of
exposing security holes. They could also serve pages more quickly, on low-cost server hardware. These
advantage became less important as cheap web hosting expanded to also offer dynamic features, and virtual
servers offered high performance for short intervals at low cost.
Almost all websites have some static content, as supporting assets such as images and style sheets are
usually static, even on a website with highly dynamic pages.

Dynamic websites

Dynamic websites are generated on the fly and use server-side technology to generate webpages. They
typically extract their content from one or more back-end databases: some are database queries across a
relational database to query a catalogue or to summarise numeric information, others may use a document
database such as MongoDB or NoSQL to store larger units of content, such as blog posts or wiki articles.

In the design process, dynamic pages are often mocked-up or wireframed using static pages. The skillset
needed to develop dynamic web pages is much broader than for a static pages, involving server-side and
database coding as well as client-side interface design. Even medium-sized dynamic projects are thus
almost always a team effort.

When dynamic web pages first developed, they were typically coded directly in languages such as Perl,
PHP or ASP. Some of these, notably PHP and ASP, used a 'template' approach where a server-side page
resembled the structure of the completed client-side page and data was inserted into places defined by 'tags'.
This was a quicker means of development than coding in a purely procedural coding language such as Perl.

Both of these approaches have now been supplanted for many websites by higher-level application-focused
tools such as content management systems. These build on top of general purpose coding platforms and
assume that a website exists to offer content according to one of several well recognised models, such as a
time-sequenced blog, a thematic magazine or news site, a wiki or a user forum. These tools make the
implementation of such a site very easy, and a purely organisational and design-based task, without
requiring any coding.

Editing the content itself (as well as the template page) can be done both by means of the site itself, and
with the use of third-party software. The ability to edit all pages is provided only to a specific category of
users (for example, administrators, or registered users). In some cases, anonymous users are allowed to edit
certain web content, which is less frequent (for example, on forums - adding messages). An example of a
site with an anonymous change is Wikipedia.

Homepage design
Usability experts, including Jakob Nielsen and Kyle Soucy, have often emphasised homepage design for
website success and asserted that the homepage is the most important page on a website.[18]Nielsen, Jakob;
Tahir, Marie (October 2001), Homepage Usability: 50 Websites Deconstructed (https://archive.org/details/h
omepageusabilit00jako_0), New Riders Publishing, ISBN 978-0735711020[19][20] However practitioners
into the 2000s were starting to find that a growing number of website traffic was bypassing the homepage,
going directly to internal content pages through search engines, e-newsletters and RSS feeds.[21] Leading
many practitioners to argue that homepages are less important than most people think.[22][23][24][25] Jared
Spool argued in 2007 that a site's homepage was actually the least important page on a website.[26]

In 2012 and 2013, carousels (also called 'sliders' and 'rotating banners') have become an extremely popular
design element on homepages, often used to showcase featured or recent content in a confined
space.[27][28] Many practitioners argue that carousels are an ineffective design element and hurt a website's
search engine optimisation and usability.[28][29][30]

Occupations
There are two primary jobs involved in creating a website: the web designer and web developer, who often
work closely together on a website.[31] The web designers are responsible for the visual aspect, which
includes the layout, coloring and typography of a web page. Web designers will also have a working
knowledge of markup languages such as HTML and CSS, although the extent of their knowledge will
differ from one web designer to another. Particularly in smaller organizations, one person will need the
necessary skills for designing and programming the full web page, while larger organizations may have a
web designer responsible for the visual aspect alone.

Further jobs which may become involved in the creation of a website include:

Graphic designers to create visuals for the site such as logos, layouts and buttons
Internet marketing specialists to help maintain web presence through strategic solutions on
targeting viewers to the site, by using marketing and promotional techniques on the internet
SEO writers to research and recommend the correct words to be incorporated into a
particular website and make the website more accessible and found on numerous search
engines
Internet copywriter to create the written content of the page to appeal to the targeted viewers
of the site[1]
User experience (UX) designer incorporates aspects of user-focused design considerations
which include information architecture, user-centered design, user testing, interaction
design, and occasionally visual design.

See also

See also
Aesthetics Graphic art software Style guide
Color theory Graphic design Web 2.0
Composition (visual arts) occupations Web colors
Cross-browser Graphics Web safe fonts
Design education Information graphics Web usability
Design principles and List of graphic design Web application framework
elements institutions
Website builder
Drawing List of notable graphic Website wireframe
designers
Dark pattern
European Design Awards Logotype
Outline of web design and
First Things First 2000
manifesto web development
Progressive Enhancement

Related disciplines
Communication design Information design Technical Writer
Copywriting Light-on-dark color scheme Typography
Desktop publishing Marketing communications User experience
Digital illustration Motion graphic design User interface design
Graphic design New media Web development
 Interaction design Search engine optimization Web animations
(SEO)

Notes
1. <table>-based markup and spacer .GIF images
1. Lester, Georgina. "Different jobs and responsibilities of various people involved in creating a
website" (https://www.arts-wales.co.uk/different-jobs-and-responsibilities-of-various-people-i
nvolved-in-creating-a-website/). Arts Wales UK. Retrieved 2012-03-17.
2. "Longer Biography" (http://www.w3.org/People/Berners-Lee/Longer.html). Retrieved
2012-03-16.
3. "Mosaic Browser" (https://web.archive.org/web/20130902095803/http://www.techopedia.co
m/images/pdfs/history-of-the-internet.pdf) (PDF). Archived from the original (http://www.techo
pedia.com/images/pdfs/history-of-the-internet.pdf) (PDF) on 2013-09-02. Retrieved
2012-03-16.
4. Zwicky, E.D, Cooper, S and Chapman, D.B. (2000). Building Internet Firewalls (https://archiv
e.org/details/buildinginternet00zwic/page/804). United States: O’Reily & Associates. p. 804
(https://archive.org/details/buildinginternet00zwic/page/804). ISBN 1-56592-871-7.
5. Niederst, Jennifer (2006). Web Design In a Nutshell (https://books.google.com/books?id=bdf
4vS2n7N8C&q=history+of+web+design&pg=PT42). United States of America: O'Reilly
Media. pp. 12–14. ISBN 0-596-00987-9.
6. Chapman, Cameron, The Evolution of Web Design (https://web.archive.org/web/201310300
30802/http://sixrevisions.com/web_design/the-evolution-of-web-design/), Six Revisions,
archived from the original (http://sixrevisions.com/web_design/the-evolution-of-web-design/)
on 30 October 2013
7. "AMO.NET America's Multimedia Online (Internet Explorer 6 PREVIEW)" (http://amo.net/NT/
01-30-01MSFTIE6.html). amo.net. Retrieved 2020-05-27.
8. "W3C Markup Validation Service" (http://validator.w3.org/).
9. W3C. "Web Accessibility Initiative (WAI)" (http://www.w3.org/WAI/).
10. THORLACIUS, LISBETH (2007). "The Role of Aesthetics in Web Design" (https://web.archi
ve.org/web/20210224225443/https://www.nordicom.gu.se/en/tidskrifter/nordicom-review-120
07/role-aesthetics-web-design). Nordicom Review. 28 (28): 63–76. doi:10.1515/nor-2017-
0201 (https://doi.org/10.1515%2Fnor-2017-0201). S2CID 146649056 (https://api.semanticsc
holar.org/CorpusID:146649056). Archived from the original (http://www.nordicom.gu.se/en/tid
skrifter/nordicom-review-12007/role-aesthetics-web-design) on 2021-02-24. Retrieved
2014-07-18.
11. Castañeda, J.A Francisco; Muñoz-Leiva, Teodoro Luque (2007). "Web Acceptance Model
(WAM): Moderating effects of user experience". Information & Management. 44 (4): 384–396.
doi:10.1016/j.im.2007.02.003 (https://doi.org/10.1016%2Fj.im.2007.02.003).
12. "Building a resilient frontend using progressive enhancement" (https://www.gov.uk/service-m
anual/technology/using-progressive-enhancement). GOV.UK. Retrieved 27 October 2021.
13. "Rolling out mobile-first indexing" (https://webmasters.googleblog.com/2018/03/rolling-out-m
obile-first-indexing.html). Official Google Webmaster Central Blog. Retrieved 2018-06-09.
14. Stone, John (2009-11-16). "20 Do's and Don'ts of Effective Web Typography" (http://webdesi
gnledger.com/tips/20-dos-and-donts-of-effective-web-typography). Retrieved 2012-03-19.
15. World Wide Web Consortium: Understanding Web Content Accessibility Guidelines 2.2.2:
Pause, Stop, Hide (http://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits-pause.ht
ml)
16. W3C QA. "My Web site is standard! And yours?" (http://www.w3.org/QA/2002/04/Web-Qualit
y). Retrieved 2012-03-21.
17. Christensen, Mathias Biilmann (2015-11-16). "Static Website Generators Reviewed: Jekyll,
Middleman, Roots, Hugo" (https://www.smashingmagazine.com/2015/11/static-website-gen
erators-jekyll-middleman-roots-hugo-review/). Smashing Magazine. Retrieved 2016-10-26.
18. Soucy, Kyle, Is Your Homepage Doing What It Should? (https://web.archive.org/web/201206
08071219/http://www.usableinterface.com/articles/homepage.php), Usable Interface,
archived from the original (http://www.usableinterface.com/articles/homepage.php) on 8
June 2012
19. Nielsen, Jakob (10 November 2003), The Ten Most Violated Homepage Design Guidelines
(https://web.archive.org/web/20131005150112/http://www.nngroup.com/articles/most-violate
d-homepage-guidelines/), Nielsen Norman Group, archived from the original (http://www.nng
roup.com/articles/most-violated-homepage-guidelines/) on 5 October 2013
20. Knight, Kayla (20 August 2009), Essential Tips for Designing an Effective Homepage (http
s://web.archive.org/web/20130821151637/http://sixrevisions.com/web_design/essential-tips-
for-designing-an-effective-homepage/), Six Revisions, archived from the original (http://sixre
visions.com/web_design/essential-tips-for-designing-an-effective-homepage/) on 21 August
2013
21. Spool, Jared (29 September 2005), Is Home Page Design Relevant Anymore? (https://web.a
rchive.org/web/20130916092857/http://www.uie.com/brainsparks/2005/09/29/is-home-page-
design-relevant-anymore/), User Interface Engineering, archived from the original (http://ww
w.uie.com/brainsparks/2005/09/29/is-home-page-design-relevant-anymore/) on 16
September 2013
22. Chapman, Cameron (15 September 2010), 10 Usability Tips Based on Research Studies (ht
tps://web.archive.org/web/20130902031226/http://sixrevisions.com/usabilityaccessibility/10-
usability-tips-based-on-research-studies/), Six Revisions, archived from the original (http://si
xrevisions.com/usabilityaccessibility/10-usability-tips-based-on-research-studies/) on 2
September 2013
23. Gócza, Zoltán, Myth #17: The homepage is your most important page (https://web.archive.or
g/web/20130602172028/http://uxmyths.com/post/717779908/myth-the-homepage-is-your-m
ost-important-page), archived from the original (http://uxmyths.com/post/717779908/myth-the
-homepage-is-your-most-important-page) on 2 June 2013
24. McGovern, Gerry (18 April 2010), The decline of the homepage (https://web.archive.org/web/
20130524221238/http://giraffeforum.com/wordpress/2010/04/18/the-decline-of-the-homepag
e/), archived from the original (http://giraffeforum.com/wordpress/2010/04/18/the-decline-of-th
e-homepage/) on 24 May 2013
25. Porter, Joshua (24 April 2006), Prioritizing Design Time: A Long Tail Approach (https://web.a
rchive.org/web/20130514075119/http://www.uie.com/articles/prioritizing_design_time/), User
Interface Engineering, archived from the original (http://www.uie.com/articles/prioritizing_des
ign_time/) on 14 May 2013
26. Spool, Jared (6 August 2007), Usability Tools Podcast: Home Page Design (https://web.arch
ive.org/web/20130429113949/http://www.uie.com/brainsparks/2007/08/06/usability-tools-po
dcast-home-page-design/), archived from the original (http://www.uie.com/brainsparks/2007/
08/06/usability-tools-podcast-home-page-design/) on 29 April 2013
27. Bates, Chris (9 October 2012), Best practices in carousel design for effective web marketing
(https://web.archive.org/web/20130403013507/http://www.smartinsights.com/conversion-opti
misation/home-page-optimisation/carousels-design-best-practice/), Smart Insights, archived
from the original (http://www.smartinsights.com/conversion-optimisation/home-page-optimisa
tion/carousels-design-best-practice/) on 3 April 2013
28. Messner, Katie (22 April 2013), Image Carousels: Getting Control of the Merry-Go-Round (htt
ps://web.archive.org/web/20131010094459/http://www.usability.gov/get-involved/blog/2013/
04/image-carousels.html), Usability.gov, archived from the original (https://www.usability.gov/
get-involved/blog/2013/04/image-carousels.html) on 10 October 2013
29. Jones, Harrison (19 June 2013), Homepage Sliders: Bad For SEO, Bad For Usability (http
s://web.archive.org/web/20131122031942/http://searchengineland.com/homepage-sliders-a
re-bad-for-seo-usability-163496), archived from the original (http://searchengineland.com/ho
mepage-sliders-are-bad-for-seo-usability-163496) on 22 November 2013
30. Laja, Peep (8 June 2019), Image Carousels and Sliders? Don't Use Them. (Here's why.) (htt
ps://web.archive.org/web/20191210184941/https://cxl.com/blog/dont-use-automatic-image-sl
iders-or-carousels/), CXL, archived from the original (https://cxl.com/blog/dont-use-automatic
-image-sliders-or-carousels/) on 10 December 2019
31. Oleksy, Walter (2001). Careers in Web Design (https://archive.org/details/careersinwebdesi0
000olek). New York: The Rosen Publishing Group, Inc. pp. 9 (https://archive.org/details/care
ersinwebdesi0000olek/page/9)–11. ISBN 9780823931910.

External links
W3C consortium for web standards (http://www.w3.org/standards/webdesign/)
Web design and development (https://curlie.org/Computers/Internet/Web_Design_and_Dev
elopment) at Curlie

Retrieved from "https://en.wikipedia.org/w/index.php?title=Web_design&oldid=1073532394"

This page was last edited on 23 February 2022, at 06:01 (UTC).

Text is available under the Creative Commons Attribution-ShareAlike License 3.0;

additional terms may apply. By
using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the
Wikimedia Foundation, Inc., a non-profit organization.