<strong>Is the add-on clearly and accurately described?</strong> It's of the utmost importance to us that users get what they expect when they try a new add-on. Your add-on name should be clear and concise, and you should refrain from using special characters or numbers to get higher search rankings or for decorative purposes. Your description should provide details about what the add-on does, how a user should take advantage of it, and what the user should expect when they install it. Links to external documents for detailed instructions are fine, but the description itself should cover the basics and leave users confident that they know what they'll get. Also, it is important that you maintain version notes appropriately as you improve and change your add-on. Users should be able to see what's new in an add-on they may have tried previously, and should be made aware of changes that might affect their current use of the add-on when they update.
<strong>Je přidatk jasnje a dokładnje wopisany?</strong> Je wosebje wažne za nas, zo wužiwarjo dóstawaja, štož wočakuja, hdyž nowy přidatk wupruwuja. Mjeno wašeho přidatka měło jasne a krótke być a wy njeměł žane wosebite znamješka abo ličby wužiwać, zo byšće wyše rjady docpěł, abo za dekoratiwne zaměry. Waše wopisanje měło podrobnosće wo tym wobsahować, štož přidatk čini, kak wužiwar měł jón wužiwać a štož wužiwar měło wočakować, hdyž jón instaluje. Wotkazy k eksternym dokumentam za podrobne instrukcije su dobre, ale wopisanje same měło zakłady podać a wužiwarjam wěstosć dać, zo bychu wědźeli, štož dóstanu. Je tež wažne, zo wersijowe pokazy wothladujeće, hdyž swój přidatk polěpšujeće a měnjeće. Wužiwarjo měli widźeć móc, štož je nowe w přidatku, kotryž su do toho wupruwowali, a měli tež pokazy na změny dóstać, kotrež móhli aktualne wužiwanje přidatka wobwliwować, hdyž jón aktualizuja.