Documentation?

  • Revised from ** to ***.

    The documentation needs to be clarified. Additional examples would help. Programmer terminology is great for discussions between programmers, but most WordPress users are not familiar with “slug” and even “use case”.

    You could begin with a few common use cases (but don’t call them that), and just show people step-by-step how to implement them (e.g. what they have to do). Zero assumptions! For example, if the user has to copy an ID number, tell them where that is found.

    A few SnagIt screen captures with annotations should do the job.

Viewing 1 replies (of 1 total)
  • Plugin Author Michael Flynn

    (@mflynn)

    This is exactly the use case that I wrote the plugin for.

    Every post and page in wordpress is given an assigned “ID” by wordpress. You can find it in the url of that post or page when you are editing it, for example: “…/wp-admin/post.php?post=13&action=edit”; where 13 is the post ID.

    The code you would use to include this post is:

    [include id=13]

    I hope this helps you and perhaps persuades you to re-evaluate your review.

Viewing 1 replies (of 1 total)
  • The topic ‘Documentation?’ is closed to new replies.