Twitter | Buscar | |
Mark Baker
Content creation, content design, content engineering. Every Page is Page One.
1.489
Tweets
349
Siguiendo
842
Seguidores
Tweets
Mark Baker retwitteó
Robert Desprez 4 jul.
Preparing Your Content for Bots? I Am Not. via
Reply Retweet Me gusta
Mark Baker 2 jul.
Reply Retweet Me gusta
Mark Baker retwitteó
A. Hexelschneider 7 may.
Reply Retweet Me gusta
Mark Baker retwitteó
dawn stevens 23 abr.
If someone needs to know where the information is stored to use it, someone isn't doing their job.
Reply Retweet Me gusta
Mark Baker 23 abr.
Respondiendo a @halvorson
Everything is Miscellaneous and Too Big to Know by David Weinberger, Made to Stick by Chip and Dan Heath
Reply Retweet Me gusta
Mark Baker retwitteó
Kristina Halvorson 18 abr.
I asked for book recommendations. You delivered.
Reply Retweet Me gusta
Mark Baker retwitteó
Ralf Koller 18 abr.
Respondiendo a @halvorson @carriehd y 6 más
Not named yet: Design Connected Content by & Every Page is Page One by Content Design by Metadata Basics for Web Content by Conversational Design by and Understanding Context by
Reply Retweet Me gusta
Mark Baker 16 abr.
"Structured writing means metadata first, content afterwards; unstructured writing means content first, metadata afterwards."
Reply Retweet Me gusta
Mark Baker 11 abr.
And while we are on the subject of professional ethics...
Reply Retweet Me gusta
Mark Baker retwitteó
Alan J. Porter’s Content Pool 10 abr.
Thanks for the shout out, Mark. Great article, well thought out.
Reply Retweet Me gusta
Mark Baker 10 abr.
Reply Retweet Me gusta
Mark Baker 9 abr.
Respondiendo a @MATCELStudentin @xmlpress
We are crossing the i's and dotting the t's. Exact release date is up to .
Reply Retweet Me gusta
Mark Baker 7 abr.
Respondiendo a @storyneedle
Well, you can't decouple systems without APIs. Many APIs are badly designed, particularly in the content space. But requiring everybody to know everybody else's business is also tight coupling. So we need to get better at content APIs. My book tries to help.
Reply Retweet Me gusta
Mark Baker 7 abr.
Talk to .
Reply Retweet Me gusta
Mark Baker 7 abr.
Respondiendo a @storyneedle
Subject domain structured writing lets us capture the data we need for integration in terms the silo understand, greatly reducing the overhead and discomfort for SMEs. Do this first and what remains is less onerous for all concerned to deal with.
Reply Retweet Me gusta
Mark Baker 7 abr.
Respondiendo a @storyneedle
Agreed, messy and hard to do, which is why we need to focus on ways to minimize the change we ask for. Coherence and loose coupling promote agility. A lot of current tech is tightly coupled and gets in the way. We need a different approach to the tech.
Reply Retweet Me gusta
Mark Baker 7 abr.
Respondiendo a @DaveThackeray @xmlpress
Hopefully the book will help. Structured Writing: Process and Rhetoric coming soon from . But note that just about every form you have filled out in your life is an example of subject domain structured writing.
Reply Retweet Me gusta
Mark Baker 7 abr.
Respondiendo a @storyneedle
The best solution to a communication problem is to minimize the amount of communication that has to take place.
Reply Retweet Me gusta
Mark Baker 7 abr.
Respondiendo a @storyneedle
The real problem is that so many content strategists think everything is a management problem and refuse to learn what it technically possible with the right structured writing approach.
Reply Retweet Me gusta
Mark Baker 7 abr.
Respondiendo a @storyneedle
You can't turn every SME into a writer. Not their skill set. We may need them to have some awareness, but as content pros our study should be to minimize how much awareness they need. The less we ask for, the greater compliance we will get.
Reply Retweet Me gusta