For creating my artist website I have done some research on Web 2.0. When I did my online questionaire over half of the 20 people I asked said they expected an indie genre artists website to be in a blogging format so I started thinking about Web 2.0.
A third important part of Web 2.0 is the social Web, which is a fundamental shift in the way people communicate. The social web consists of a number of online tools and platforms where people share their perspectives, opinions, thoughts and experiences. Web 2.0 applications tend to interact much more with the end user. As such, the end user is not only a user of the application but also a participant by:
- Contributing to RSS
- Social bookmarking
- Social networking
For marketers, Web 2.0 offers an opportunity to engage consumers. A growing number of marketers are using Web 2.0 tools to collaborate with consumers on product development, service enhancement and promotion. Companies can use Web 2.0 tools to improve collaboration with both its business partners and consumers. Among other things, company employees have created wikis—Web sites that allow users to add, delete, and edit content — to list answers to frequently asked questions about each product, and consumers have added significant contributions. So this type of website really would be ideal for a band as it would encourage an online community and forums on the artists website creating more hits.
WEB APPLICATION FRAMEWORK – ARCHITECTURE
Most web application frameworks are based on the model–view–controller (MVC) architectural pattern. The model-view-controller is a software architecture,currently considered an architectural pattern used in software engineering. The pattern isolates “domain logic” (the application logic for the user) from the user interface (input and presentation), permitting independent development, testing and maintenance of each (separation of concerns).
THE MODEL – VIEW – CONTROLLER (MVC) ARCHITECTURE
Many frameworks follow the model–view–controller (MVC) architectural pattern to separate the data model with business rules from the user interface. This is generally considered a good practice as it modularizes code, promotes code reuse, and allows multiple interfaces to be applied. In Web applications, this permits different views to be presented, such as web pages for humans, and web service interfaces for remote applications.
Web typography refers to the use of fonts on the World Wide Web. When HTML was first created, font faces and styles were controlled exclusively by the settings of each Web browser. There was no mechanism for individual Web pages to control font display until Netscape introduced the
<font> tag in 1995, which was then standardized in the HTML 2 specification. However, the font specified by the tag had to be installed on the user’s computer or a fallback font, such as a browser’s default sans-serif or monospace font, would be used. The first Cascading Style Sheets specification was published in 1996 and provided the same capabilities.
A common hurdle in Web design is the design of mockups that include fonts that are not Web-safe. There are a number of solutions for situations like this. One common solution is to replace the text with a similar Web-safe font or use a series of similar-looking fallback fonts.
Here is a list of web safe fonts I have the option of chosing: WINDOW FONTS/ MAC FONTS/ FONT FAMILY
Arial, Arial, Helvetica, sans serif
Comic Sans MS, Comic Sans MS 5, cursive
Courier New, Courier New, monospace
Georgia 1, Georgia, serif
Impact, Impact 5, Charcoal 6, sans-serif
Lucida Console, Monaco 5, monospace
Lucida Sans Unicode, Lucide Grande, sans-serif
Palatino Linotype, Book Antiqua 3, Palatino, serif
Tahoma, Geneva, sans-serif
Time New Roman, Times New Roman, Times, serif
Trebuchet MS 1, Trebuchet MS, sans-serif
Verdana, Verdana, Geneva, sans-serif
Symbol, Symbol (Symbol 2, Symbol 2)
Webdings, Webdings (Webdings 2, Webdings 2)
Wingdings, Zapf Dingbats (Wingdings 2, Zapf Dingbats 2)
MS Sans Serif 4, Geneva, sans-serif
MS Serif 4, New York 6, serif
I have decided I will use: Palatino Lunotype, Book Antiqua 3, Palatino, serif
A website wireframe, also known as a page schematic or screen blueprint, is a visual guide that represents the skeletal framework of a website. The wireframe depicts the page layout or arrangement of the website’s content, including interface elements and navigational systems, and how they work together. The wireframe usually lacks typographic style, color, or graphics, since the main focus lies in functionality, behavior, and priority of content. In other words, it focuses on “what a screen does, not what it looks like.”
- Wireframes focus on
- The kinds of information displayed
- The range of functions available
- The relative priorities of the information and functions
- The rules for displaying certain kinds of information
- The effect of different scenarios on the display
- The website wireframe connects the underlying conceptual structure, or information architecture, to the surface, or visual design of the website. Wireframes help establish functionality, and the relationships between different screen templates of a website. An iterative process, creating wireframes is an effective way to make rapid prototypes of pages, while measuring the practicality of a design concept. Wireframing typically begins between “high-level structural work—like flowcharts or site maps—and screen designs.” Within the process of building a website, wireframing is where thinking becomes tangible.