{"id":1401,"date":"2020-08-10T13:28:28","date_gmt":"2020-08-10T13:28:28","guid":{"rendered":"https:\/\/space.xtemos.com\/demo\/neptun\/?p=1401"},"modified":"2020-08-10T14:36:14","modified_gmt":"2020-08-10T14:36:14","slug":"online-commerce-booms-amid-shifting","status":"publish","type":"post","link":"https:\/\/space.xtemos.com\/demo\/neptun\/2020\/08\/10\/online-commerce-booms-amid-shifting\/","title":{"rendered":"Online commerce booms amid shifting"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Authorities in our business will tell in no uncertain terms that Lorem Ipsum is that huge, huge no no to forswear forever. Not so fast, I’d say, there are some redeeming factors in favor of greeking text, as its use is merely the symptom of a worse problem to take into consideration. You begin with a text, you sculpt information<\/a>, you chisel away what’s not needed, you come to the point, make things clear, add value, you’re a content person, you like words.<\/p>\n

Anyway, you still use Lorem Ipsum and rightly so, as it will always have a place in the web workers toolbox, as things happen, not always the way you like it, not always in the preferred order. Even if your less into design and more into content strategy you may find some redeeming value with, wait for it, dummy copy, no less. Consider this: You made all the required mock ups for commissioned layout, got all the approvals, built a tested code base or had them built, you decided on a content management system, got a license for it or adapted open source software for your client’s needs.<\/i><\/p>\n

Presentation software like keynote or pages<\/h3>\n

Then the question arises: where’s the content? Not there yet? That’s not so bad, there’s dummy copy to the rescue. But worse, what if the fish doesn’t fit in the can, the foot’s to big for the boot? Or to small? To short sentences, to many headings, images too large for the proposed design, or too small, or they fit in but it looks iffy for reasons the folks in the meeting can’t quite tell right now, but they’re unhappy, somehow.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t

\n\t\t\t\tI\u2019ve heard the argument that \u201clorem ipsum\u201d is effective in wireframing or design because it helps people focus on the actual layout, or color scheme, or whatever. What kills me here is that we\u2019re talking about creating a user experience that will (whether we like it or not) be DRIVEN by words.\t\t\t<\/p>\n\n\t\t\t\t\t\t\t\n\t\t\t\t\tWinston Churchill\t\t\t\t<\/cite>\n\t\t\t\t\t<\/blockquote>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t

A client that’s unhappy for a reason is a problem, a client that’s unhappy though he or her can’t quite put a finger on it is worse. Chances are there wasn’t collaboration, communication, and checkpoints, there wasn’t a process agreed upon or specified with the granularity required. It’s content strategy gone awry right from the start. Forswearing the use of Lorem Ipsum<\/a> wouldn’t have helped, won’t help now. It’s like saying you’re a bad designer<\/a>, use less bold text, don’t use italics in every other paragraph. True enough, but that’s not all that it takes to get things back on track.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t