Gospel information architecture site

The purpose of this article is to create an occasion for discussion and the formation, following the results of disputes, of a generally accepted guide for designing a scheme of the information architecture of a site or other information system.

In the current situation, it is not possible to systematically work with this kind of source material, since it is beautiful to give the Customer such a varied set of design approaches that forbids us the designer’s internal moral code.



In the future, we all need the ability to use information architecture schemes not only as initial presentations, but also as the final description of the case, placed in the portfolio on third-party resources, so that image quality requirements are created with a reserve for the future and imply adaptability to different tasks and style .

Persistent convictions and all sorts of particularly strong arguments that such a scheme in TK must be preceded by a detailed analysis and optimization of the customer’s business processes; as well as listing the rules for their decomposition in IDEF0, UML, or whatever, is beyond the scope of this essay. Simply put, if your product, the designer and the designer are only involved in shorthand writing verbatim and endless edits from the customer, without the slightest opportunity to influence the logic and concept of the project (and the business), then it will soon be prepared another article, “Free Checkout, or Why You Wasted Out of McDonald's.”

image

For all the other two and a half people who, in their daily work, have a real, rather than ephemeral, ability to influence the formation of the logic and principles of interaction between the system and the user and owner, we continue:

Declaration of Intent

after it has become impossible to tolerate a careless attitude some executors of Terms of Reference for the design and design of so-called schemes with a list of pages and sections, it was decided to draw up a clear and understandable guide on drawing information schemes th architecture of the information system.

As you understand, such schemes of the internal logic of the project are needed not just for internal analytics, they are viewed by the customer. And the customer also confirms the correctness and correctness of the logic, the clarity of the concept and the perfect selection of colors.

This article should set a precedent for the creation of a single guide to bring a fragmented daub to a single common denominator.

A single format will make it possible to use competently designed information architecture schemes to create any sites, including state ones, and also simplify the process of migration to new versions of sites.

Rules

In order to comply with all these conditions, strict rules will be introduced:

  • All pages and sections on the diagram are drawn in the form of rectangles with the aspect ratio of any squares should be 1: 1 (square)
  • The allowable block size varies from maximum (512 by 512 pixels) to the minimum allowable for use (32 by 32 pixels)
  • The general scheme with all the branches should fit into the circle without losing important details
  • Explanatory text inside the block should not occupy more than 80% of the height of the square
  • Possible fonts for signatures: Helvetica, Roboto.
  • The background can be any. There is no need to make it homogeneous or transparent, a gradient or even a photo in HD quality is allowed.
  • It is unacceptable to overlap arrows arrows on each other.
  • Each described business process should visually convey naturalness, confidence, a positive and open attitude.
  • It is important to make any scheme accessible to the maximum number of people, including those with mental disabilities, using special software and technologies for viewing websites.


It is also proposed to join our development team for iPhones on a voluntary basis today for quick and high-quality rendering of any information architecture schemes for typical sites and mobile applications.

Also popular now: