The argument for developing content before design for a new website is nothing new. I just want to explain why, showing what can happen when the content is defined later.
“Let’s build a website to talk about our company. What’s it going to contain? Ummm, you know, the usual: some images, video and text. We’ll think about it and let you know.”
So the website is designed around a rough idea of the content it needs to contain, but perhaps without knowing its exact function, what it’s communicating or how much of it there is.
You could end up with this:
The website works, but doesn’t quite serve the function it needs to, or perform as well as it should.
And depending on the amount of information you want to add in the end, you could find your content squeezed in or looking empty. You don’t want blisters, do you?
Disclaimer: That is not my foot. My foot is not hairy.