summaryrefslogtreecommitdiff
path: root/_posts/2008-10-10-mastering-content.markdown
diff options
context:
space:
mode:
authorJosé Mota <josemota.net@gmail.com>2012-04-08 20:32:15 +0100
committerJosé Mota <josemota.net@gmail.com>2012-04-08 20:32:15 +0100
commitc9acd467e38fa267db5972de02a3615ff6998355 (patch)
tree8959cf7099de692f33a48bfebe022c5de67e03c5 /_posts/2008-10-10-mastering-content.markdown
parent6ce6a1f1f45889acf68ad2fd0ee5a5a39d8ca9ba (diff)
Update some more posts.
Diffstat (limited to '_posts/2008-10-10-mastering-content.markdown')
-rw-r--r--_posts/2008-10-10-mastering-content.markdown42
1 files changed, 42 insertions, 0 deletions
diff --git a/_posts/2008-10-10-mastering-content.markdown b/_posts/2008-10-10-mastering-content.markdown
new file mode 100644
index 0000000..ce7d8eb
--- /dev/null
+++ b/_posts/2008-10-10-mastering-content.markdown
@@ -0,0 +1,42 @@
+---
+layout: post
+title: Mastering content
+tags: [ design, development ]
+published: true
+---
+
+Many times I wonder why there are such brilliant websites and the people behind
+them are such great masterminds. I'm already assuming there needs to have a bit
+of genius, not just creativity. I'm talking about the core of _every_ website:
+**content.**
+
+Imagine you care about content already, but in what way? Do you design for the
+content or the other way around? Do you create a layout based on the
+information/content you have or do you try and generate content based on the
+lovely yet empty work of art you've created with Photoshop?
+
+Every piece of content has its weight inside a website, acknowledging that is a
+major step towards balance and success. I took this into consideration when
+building my last project with a local client, in which he asked for many many
+chunks of information all organized across pages. Measuring each chunk of
+information takes credit in the definition of a proper layout in which each
+portion can be more relevant or not through width, height, color, typography,
+everything.
+
+_Content, not data!_ It is our job as designers/engineers to make content out
+of data that a client gives us. No matter how much a client sees _their
+content,_ it's still **data** for us and it's also our job to
+help the client understand what data should be like in a website and what
+importance it should have to achieve better results. I'm not saying we should
+override their needs, we actually need to listen to what they want, we're not
+wizards :P We can even pretend we're a regular user of theirs and play the
+game, a lot of results come from such an approach concerning usability and
+accesibility.
+
+End of story
+------------
+
+Content is what grabs people's attention on a website and the way it's
+explicit. You can even have a beautiful background and today's grungy trends
+and everything, but if your content is not meaningful and well marked up then
+something's definitely wrong.