post-page

How to write a good plugin review

5
responses
heading
heading
heading
5
Responses

 

Comments

  1. Matt (2 comments.) says:

    What is the problem with having a post dedicated to the plugin?

    In my case I use a post, but have a page listing all of the plugins and linking them to my posts.

    • Ajay (209 comments.) says:

      There is not a “problem” but a post is specific to a particular time period, while a page is perennial.

      Again, this isn’t a requirement but definitely makes things a lot easier. I’ve seen plugin authors dedicating a separate post for each release of the plugin with a separate download link for each release. You’re just creating confusion for the visitor on your blog, hunting for your plugin.

      Keeping a plugin page ensures a kind of a flow and a more organized structure / distribution.

  2. Martin says:

    How to talk about something? First decide what you want to talk about, then…

    Gee, this post is reaching new heights!

  3. tekzt (1 comments.) says:

    I usually do not browse the authors page before reviewing a plugin, except there is a very visible “how to install”-link right next to the download button. it´s because a part of my review process is how much i can do with something without having read about it before. I think the best plugins don´t need any explanation and should just work intuitive or have explanations build in their admin options. Another part would be how fast i could find help on the authors page if I experienced some issues and this would be very random if i browsed the authors page a lot before, because i already know the site and know or even already saw where to find the solution.

  4. Mark Ghosh (386 comments.) says:

    This is a test



Obviously Powered by WordPress. © 2003-2013

page counter
css.php