3 ms·
If you don't know what a "post status" is, you probably are not the sort of person who would be interested in this article. The sub section of the site the arti
by relequestual 15y ago
If you don't know what a "post status" is, you probably are not the sort of person who would be interested in this article. The sub section of the site the article is featured on is all about Wordpress, a CMS designed to publish content. If you worked with Wordpress and didn't know what a post status is, I wouldn't expect you to be very good. Still I see where you are coming from; I may have been better to give an overview of the plugin before a history.
Re level of detail. Thanks, I will take this on board for future articles.
Re narrative. I guess I was drawing on my previous work of reviewing software, trying to give something more than just a problem and how it's solved, more opinion, thoughts, history.
Would, "Do you think I should have given the plugin more of an introduction?" be better? Spelling and grammar have always been a weakness of mine, so I need to improve if I plan on doing more writing.
Thanks for replying.
- ColinWright 15y ago> If you don't know what a "post status" is, > you probably are not the sort of person who > would be interested in this article. Actually, knowing about what plug-ins are available for WP, what they do, and how easy (or not!) they are to use is the sort of thing I do want to know. Your article potentially has a much wider audience than the one you've assumed. It would only take a sentence to create the scene of what a "post status" is and does. I always have an eye on the next widest audience, and it's always useful to set the scene. > The sub section of the site the article is > featured on is all about Wordpress ... Still > I see where you are coming from; I may have > been better to give an overview of the plugin > before a history. It is always important to know your audience, but one can always write for the slightly wider circle. > Re narrative. I guess I was drawing on my > previous work of reviewing software, trying > to give something more than just a problem > and how it's solved, more opinion, thoughts, > history. I guess that depends on the purpose of what you're writing, and it wasn't clear to me. Stating clearly at the beginning that this is a review rather than an explanation, presentation, whatever, might be useful. Again, you were perhaps expecting a much more specific audience, but even so it's worth setting the scene somewhat. It doesn't take many words, and even if someone doesn't need it, it serves to ease them in gently. Just a thought. Again, hope that helps. I can see that we were slightly at cross-purposes, but I hope the unexpected viewpoint has been useful.