WILSOL LLC



Great Links . . .
Constant Contact(R)
Trusted Email Marketing & Online Surveys
Speakeasy Speed Test
GETTING STARTED

Three basic things

First, you'll need an actual 'Website'
Commonly this would include any communication media that can be read and/or interacted with via a Web Browser. A simple example could be a series 'hyper-linked' web pages with text and images (like this site).
Second, you'll need a 'Domain Name'
A domain name is a unique web address that gives the 'location', to any Web enabled device, on where to find your website. The 'Domain Name' is the address everybody types in their web browser to go to a particular website. Examples would be; 'www.oxfam.org' or 'www.google.com'. We can assist with the purchase and maintenance Domain Names
Lastly, you need a 'Host'
A 'host' is essentially just a computer configured to 'serve' web pages?

All your email, letter and digital photograph files are stored on your own computer's hard drive (JPG, BMP, TXT, DOC). Web page files are no different (HTML, PHP, CSS, JS), they can also reside on your hard drive along with everything else. All the files that are stored on your computer could be said to be 'hosted' by your computer.

You could, if you really wanted, 'host' your website from your own computer. This would mean though, having your computer turned on 24 hours a day.. every day. In most cases this is not practical, unless you're a very large organization.

Most people choose instead to 'rent' some space on someone else's computer. This is what is meant by someone 'hosting' your website. Terms like 'your host', 'hosting package', 'web space' are all references to the idea of your website files being stored on someone else's computer.

It is this 'remote' computer that sends your webpage's to those who wish to see them. The technical term is that the remote computer 'serves' the web pages to the user. Computers that store and send web pages are therefore often referred to as 'servers'.

So there are the basic necessities for having a website, but there are still many things that need to be considered in preparation. Contact us or follow the rest of the links on this site to help you make the right preparation and avoid the many common pitfalls. So next to: Web Site Planning


Web Site Design...
Needs analysis
To start, a brief discovery phase identifies the website's marketing goals, technical requirements, branding strategy and measurements of success. Careful attention is paid to market competitors, customer feedback (when available), and input from client team members.

WILSOL design then works with the client to identify a delivery date and implementation timeline, after which an extranet site for the project is established to make project deliverables available to the client.		 Architecture
Existing and proposed content, functional/navigational elements, and inter-site promotions are all factored into the site's information architecture. Ideally, the sitemap maintains a balance between breadth and depth, requiring as few clicks as possible to any given piece of content, while not overwhelming the user with too many choices at once.

Content that may be featured on the site's home page is identified, as is lead-generating "premium content" and any related forms. 		Design
Once an information architecture has been finalized, the site's page layout, look and feel, and branding are designed through a series of Photoshop screen mockups. Typically, three or four mockups are produced for a given design, including the site's home page and two or three prominent content pages.

Feedback is solicited from the client, after which one or more rounds of iteration are made to the design. Depending on the project's scope and timetable, multiple design directions may be produced.		 Production
With a final design in hand, cascading style sheets are written to define text formatting, screen layout, and navigation elements. Content pages are authored in HTML/PHP, and images are optimized for efficient download times.

Throughout production, SEO best practices are followed to ensure the site's code is optimized for search engines. WILSOL design will work with the client to identify opportunities within the site where search keywords can be applied and optimized.
QA & launch
The website is tested and debugged on the latest general-release version of Internet Explorer, Firefox, Chrome and Safari, along with any additional browsers and versions identified by the client during the needs analysis phase.

Once all revisions, additions, and testing are completed, the site is uploaded to the client's production server for public deployment. WILSOL design will then work with the client to ensure a clean site launch, identifying and correcting any issues that may arise.
Options such as an interactive database & much more...
Needs analysis
Discussions are held with the client's project managers to identify the goals, technical requirements, and measurements of success for the application's user interface. A usage model is mapped out, existing user feedback (when available) is reviewed, and navigation alternatives are considered.

WILSOL design then works with the client to identify a delivery date and implementation timeline, after which an extranet site for the project is established, though which project deliverables available to the client. 		Specification
The application's features and functionality are mapped to an information architecture, defining the navigation pathways throughout the user interface. Ideally, the architecture strikes a balance between breadth and depth, minimizing clicks to commonly-used features, without bombarding the user with too many options at once.

Where possible, redundant means of accessing commonly used features are built into the information archicture, accounting for differences in usage patterns among users.		 Design
Once an information architecture is finalized, the application's screen layout, look and feel, and navigation are designed through a series of Photoshop screen mockups. Typically, 3-4 mockups are initially produced, focusing on unique screen types or high-value functionality.

Feedback is solicited from the project team, after which one or more rounds of iteration are made to the design. Depending on the project's scope and timetable, additional screens may be mocked up prior to prototyping.		 Prototyping
With a final design in hand, a clickable model of the application's user interface is prototyped. CSS is written to define text formatting, screen layout, and navigation elements such as menus and dialogs. Key screens are authored in HTML/PHP, while custom icons are designed for inclusion in the user interface. If desired, end-user testing is conducted to validate navigation and usability.

Depending on the scope of the web application, all or some of its features and functionality may be prototyped, at the discretion of the client.
Integration
The application prototype is tested and debugged on the latest general-release version of Internet Explorer, Firefox, Chrome and Safari, along with any additional browser versions identified by the client during the needs analysis phase.

As application modules and discreet UI components are finalized, prototype code is delivered to the client's production engineers for integration. WILSOL design will then work with the client to ensure the UI is grafted onto the application framework, identifying and correcting any issues that may arise.





























































Sign up for PayPal and start accepting credit card payments instantly.