Website Architecture

Report
Administration Of A Website
Site Architecture
October 20, 2010
This session covers
What is site architecture
 Planning site architecture
 Components of site architecture
 Benefits of a site architecture
 Other considerations

What is Site Architecture?
How your site is structured from the
top down.
 Built while keeping growth,
maintenance and content in mind
 The home, not the contents of the
home
 What is it NOT - Information
Architecture (IA) (content structure)

Example of Site Architecture

Using SharePoint technologies as the example, this is an example
of county site who provides hosting and management to not only
county departments but other entities/agencies.
Example of Site Architecture

When you expand a site, you see the organized subsites as they
relate to that categorical structure.
Planning Site Architecture

Assuming it’s a redesign, first things
first, what information do you have
on your current site, such as:
 Stakeholders
 Analytics
(commonly visited pages)
 Current topology or site map
 Technical information (integration to
other systems)
Planning Methods
Card sorting
 Content inventories
 Paper and sketch boards
 Site map diagrams

Which Planning Method to Choose?
How big is the website?
 What type of website is it?
 Who is your stakeholders?
 Consider your workflow.

Planning Tips
Organize based on user needs
 Use clear naming conventions
 Think like a typical user of your site
 Plan architecture around the content
 Ensure all stakeholders agree on the
goal of the website
 Think about the best way to display
content.

Components of Site Architecture




Brand / Design
Navigation
Information
Architecture (IA)
Services /
Features




Workflow /
Automation
Search Engine
Optimization
Security Model
Website
Governance
Component: Brand/Design
A brand is the identity of a specific
product, service, or business.
 A brand can take many forms,
including a name, sign, symbol, color
combination or slogan.

Component: Navigation
Navigation is one outcome of
designing your site architecture AND
information architecture.
 Good navigation will reflect the
content (IA) and purpose of your site
 Good navigation will be relative to
the structure of your website (site
architecture.)

Component: Information Architecture





The way you organize information on
your site (within your site architecture)
Relates to the content itself
Decision to use or not to use metadata
Who and how the information is
accessed on your website
Gets to the heart of the end-user
experience
Component: Services and Features
Relational Databases
 Features, such as on-line forms or
on-line payments
 Decision to use XML
 Service-oriented architecture (SOA)
 Features such as lists or targeted
data options (SharePoint example)

Component: Workflow or Automation
A workflow is a sequence of
connected steps (think of this as a
systematic / automated business
process.)
 Workflows can be used for various
pre-defined tasks to increase
efficiencies.

Component: Search Engine Optimization

Search Engine Optimization (SEO)
ties into the site and information
architecture through items such as:
 Home
Page
 Site Map
 Navigation
 Error Trapping
 Layers of directories in the site
Component: Security Model

Security ties directly into all the
planning of site architecture by:
 Determining
who is accessing what information
and to what level (administrator, editor,
anonymous user, other group member, etc.)
 What information is being processed on-line
and where does that information get stored?
 How do you keep the integrity of your
information/content?
Component: Governance
The purpose of Website Governance
is to ensure appropriate policies are
in place for managing a site in a
controlled and orderly way.
 Governance can and should affect
every aspect of your website.
 Sites that lack governance, show it.

More on Governance
Establishing a authoritative team
 Set standards, priorities and goals
 Develop policies

 Management
 Maintenance
 Design

Manage change
Benefits of Site Architecture




Agile, no need for
redesign to add new
features, sites or
components.
Consistent user
experience
Topic or Site Map
Improved content
searching



Cohesive website
supportive to both
administrators and
content managers
Minimize duplication
of efforts/information
Reflects the business
not the organizational
chart
Other considerations
Network scalability
 Host your own or have another entity
host?
 Host others?
 24x7 up time?

Reference Resources

All sources used in this presentation
are on the notes page of this slide.
Questions and Answers
Thank You for Attending!
If you have questions, please feel
free to call or e-mail:

Kathie Glassel
Technology Programs Administrator
717-526-1010 X 3353
[email protected]

Nic Poague
Database / Web Specialist
717-526-1010 X 3354
[email protected]

similar documents