• RichardWantsToKnow

    (@richardwantstoknow)


    This may be a GREAT plugin…..

    But without documentation I’m finding it to be an install nightmare.

    Why is it that developers won’t take the time to write documentation???

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author mvied

    (@mvied)

    The FAQ serves as documentation. If it is not sufficient, start a support topic.

    Thread Starter RichardWantsToKnow

    (@richardwantstoknow)

    No, you’re not getting it.
    You are the plug-in author. You understand it. Not everyone can read your mind.
    I would guarantee you your donations would rise if you simply took an hour and wrote an install guide that explains what you mean by the one or two-word field labels you have.
    I donate a lot. But haven’t on this one because your labels can be interpreted (or in this case, ‘guessed at’) in more than one way. Our hosting company (a major one) can’t even understand what you mean by the configuration inputs!
    Raise the bar.

    Thread Starter RichardWantsToKnow

    (@richardwantstoknow)

    As you wrote in the ‘About Me’ section of your website:
    “I am deeply passionate about the work I do and take pride in every line of code I write.”

    Then if that’s the case, write a damn install guide.

    Plugin Author mvied

    (@mvied)

    I’m sorry, but I believe the descriptions of the settings on the screen to be sufficient. If you would ask specific questions, I could clarify. Through your questions I could better understand what is unclear about what I have in place and maybe change it to make it clearer? In the latest update I did add a little meat to the Installation guide to cover some basic use cases and common issues.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Docs????’ is closed to new replies.