{"id":42119,"date":"2019-03-18T00:00:00","date_gmt":"2019-03-17T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/polzovatelskaya-dokumentatsiya-chto-delaet-eyo-plohoj-i-kak-eto-ispravit"},"modified":"2020-02-18T13:44:55","modified_gmt":"2020-02-18T10:44:55","slug":"polzovatelskaya-dokumentatsiya-chto-delaet-eyo-plohoj-i-kak-eto-ispravit","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/news\/polzovatelskaya-dokumentatsiya-chto-delaet-eyo-plohoj-i-kak-eto-ispravit","title":{"rendered":"Dokumentacioni i p\u00ebrdoruesit: \u00e7far\u00eb e b\u00ebn at\u00eb t\u00eb dob\u00ebt dhe si ta rregullojm\u00eb","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Dokumentacioni i p\u00ebrdoruesit: \u00e7far\u00eb e b\u00ebn at\u00eb t\u00eb dob\u00ebt dhe si ta rregullojm\u00eb\" src=\"\/wp-content\/uploads\/2019\/03\/4381d63e81fbb299384255cb54dd34b5.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDokumentacioni p\u00ebr softin \u00ebsht\u00eb thjesht nj\u00eb grup artikujsh. Por edhe ata mund t\u00eb t\u00eb shqet\u00ebsojn\u00eb. Fillimisht k\u00ebrkon gjat\u00eb p\u00ebr udh\u00ebzimin e duhur. Pastaj p\u00ebrpiqesh t\u00eb kuptosh tekstin e paqart\u00eb. B\u00ebn ashtu si\u00e7 \u00ebsht\u00eb shkruar, por problemi nuk zgjidhet. K\u00ebrkon nj\u00eb artikull tjet\u00ebr, nervozohesh... Pas nj\u00eb ore heq dor\u00eb dhe largohesh. K\u00ebshtu funksionon dokumentacioni i keq. \u00c7far\u00eb e b\u00ebn at\u00eb t\u00eb till\u00eb, dhe si mund ta rregullosh \u2014 lexoni m\u00eb posht\u00eb.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<blockquote><p>N\u00eb dokumentacionin ton\u00eb t\u00eb vjet\u00ebr kishte shum\u00eb disavantazhe. Tani e gati nj\u00eb vit po e riparojm\u00eb at\u00eb, n\u00eb m\u00ebnyr\u00eb q\u00eb skenari i p\u00ebrshkruar m\u00eb sip\u00ebr t\u00eb mos prekte klient\u00ebt tan\u00eb. Shikoni, <noindex><a rel=\"nofollow\" href=\"https:\/\/doc.ispsystem.ru\/index.php\/\">si ishte<\/a><\/noindex> dhe <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.ispsystem.ru\/\">si \u00ebsht\u00eb<\/a><\/noindex>.<\/p><\/blockquote>\n<p><\/p>\n<h2>Problemi 1. Artikuj t\u00eb paqart\u00eb, t\u00eb shkruar keq<\/h2>\n<p>\nN\u00ebse nuk mund t\u00eb kuptosh dokumentacionin, \u00e7far\u00eb kuptimi ka? Por askush nuk shkruan artikuj t\u00eb paqart\u00eb me t\u00eb keq. Ato e fitojn\u00eb k\u00ebt\u00eb status kur autori nuk mendon p\u00ebr audienc\u00ebn dhe q\u00ebllimin, derdh uj\u00eb dhe nuk e kontrollon tekstin p\u00ebr gabime.<\/p>\n<ul>\n<li><b>Audienca<\/b>. Para se t\u00eb shkruash nj\u00eb artikull, duhet t\u00eb mendosh p\u00ebr nivelin e p\u00ebrgatitjes s\u00eb lexuesit. \u00cbsht\u00eb logjike q\u00eb n\u00eb nj\u00eb artikull p\u00ebr fillestar\u00ebt, nuk duhet t\u00eb lihet pa p\u00ebrmendur hapat bazik\u00eb dhe t\u00eb lini terma teknik\u00eb pa shpjegim, nd\u00ebrsa n\u00eb nj\u00eb artikull p\u00ebr nj\u00eb karakteristik\u00eb t\u00eb rrall\u00eb, t\u00eb nevojshme vet\u00ebm p\u00ebr profesionist\u00ebt, duhet t\u00eb shpjegosh kuptimin e fjal\u00ebs PHP.<\/li>\n<li><b>Q\u00ebllimi<\/b>. Gjithashtu, nj\u00eb gj\u00eb tjet\u00ebr p\u00ebr t\u00eb cil\u00ebn \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb mendosh p\u00ebrpara \u00ebsht\u00eb q\u00eb autori duhet t\u00eb vendos\u00eb nj\u00eb q\u00ebllim t\u00eb qart\u00eb, t\u00eb p\u00ebrcaktoj\u00eb veprimin e dobish\u00ebm t\u00eb artikullit, dhe t\u00eb vendos\u00eb se \u00e7far\u00eb do t\u00eb b\u00ebj\u00eb lexuesi pas leximin. N\u00ebse nuk b\u00ebhet kjo, do t\u00eb rezultoj\u00eb nj\u00eb p\u00ebrshkrim p\u00ebrshkrimi. <\/li>\n<li><b>Uji dhe gabimet<\/b>. Informacioni i tep\u00ebrt dhe burokracit\u00eb, gabimet dhe shtypjet e gabuara e pengojn\u00eb perceptimin. Edhe n\u00ebse lexuesi nuk \u00ebsht\u00eb nj\u00eb grammer-nazi, neglizhenca n\u00eb tekst mund ta shqet\u00ebsoj\u00eb at\u00eb.<\/li>\n<\/ul>\n<p>\nKonsideroni k\u00ebshillat e m\u00ebsip\u00ebrme dhe artikujt do t\u00eb b\u00ebhen m\u00eb t\u00eb qart\u00eb \u2014 e garantuar. P\u00ebr ta b\u00ebr\u00eb edhe m\u00eb mir\u00eb, merrni parasysh pyetjet tona <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ispsystem\/blog\/431456\/\"> 50 pyetje kur punoni mbi dokumentacionin teknik<\/a><\/noindex>.<\/p>\n<h2>Problemi 2. Artikujt nuk p\u00ebrgjigjen t\u00eb gjitha pyetjeve<\/h2>\n<p>\n\u00cbsht\u00eb keq kur dokumentacioni nuk ndjek zhvillimin, nuk p\u00ebrgjigjet ndaj pyetjeve reale, gabimet n\u00eb t\u00eb nuk korrigjohen p\u00ebr vite. K\u00ebto jan\u00eb probleme m\u00eb shum\u00eb t\u00eb autorit, sesa t\u00eb organizimit t\u00eb proceseve brenda kompanis\u00eb.<\/p>\n<h3>Dokumentacioni nuk ndjek zhvillimin<\/h3>\n<p>\nFunkcioni \u00ebsht\u00eb tashm\u00eb n\u00eb lansim, marketingu planifikon ta p\u00ebrmend\u00eb at\u00eb, dhe k\u00ebtu del se nuk ka ende artikuj t\u00eb rinj ose p\u00ebrkthimesh n\u00eb dokumentacion. P\u00ebr shkak t\u00eb k\u00ebsaj, na ka ndodhur t\u00eb shtyjm\u00eb lansimin. Mund t\u00eb k\u00ebrkojm\u00eb pafund\u00ebsisht nga t\u00eb gjith\u00eb q\u00eb t\u00eb transmetojn\u00eb detyrat n\u00eb koh\u00eb te shkrimtar\u00ebt teknik\u00eb, por kjo nuk do t\u00eb funksionoj\u00eb. N\u00ebse procesi nuk automatizohet, situata do t\u00eb p\u00ebrs\u00ebritet.<\/p>\n<p>Ne kemi b\u00ebr\u00eb ndryshime n\u00eb YouTrack. Detyra p\u00ebr t\u00eb shkruar nj\u00eb artikull mbi funksionin e ri i bie shkrimtarit teknik n\u00eb t\u00eb nj\u00ebjtin moment kur mund\u00ebsit\u00eb fillojn\u00eb t\u00eb testohen. Atyher\u00eb, marketingu b\u00ebn t\u00eb ditur p\u00ebr t\u00eb, q\u00eb t\u00eb p\u00ebrgatitet p\u00ebr promovim. Njoftimet arrijn\u00eb gjithashtu n\u00eb mesazherin korporativ Mattermost, k\u00ebshtu q\u00eb \u00ebsht\u00eb e pamundur t\u00eb humbas\u00ebsh lajme nga zhvilluesit.<\/p>\n<h3>Dokumentacioni nuk pasqyron k\u00ebrkesat e p\u00ebrdoruesve<\/h3>\n<p>\nNe jemi m\u00ebsuar t\u00eb punojm\u00eb k\u00ebshtu: funksioni doli, ne treguam p\u00ebr t\u00eb. E p\u00ebrshkruam si t\u00eb aktivizohet, t\u00eb \u00e7aktivizohet, dhe si t\u00eb b\u00ebhen rregullime t\u00eb imta. Por \u00e7far\u00eb ndodh n\u00ebse klienti p\u00ebrdor softuerin ton\u00eb ndryshe nga sa ne e kishim parashikuar? Ose ka gabime p\u00ebr t\u00eb cilat ne nuk kemi menduar?<\/p>\n<p>P\u00ebr t\u00eb siguruar q\u00eb dokumentacioni t\u00eb jet\u00eb sa m\u00eb i plot\u00eb, k\u00ebshillojm\u00eb t\u00eb analizoni ankesat n\u00eb suport, pyetjet n\u00eb forume t\u00eb tematik\u00ebs, k\u00ebrkesat n\u00eb motor\u00ebt e k\u00ebrkimit. Temat m\u00eb t\u00eb popullarizuara t'i d\u00ebrgoni shkrimtar\u00ebve teknik\u00eb, q\u00eb ata t\u00eb plot\u00ebsojn\u00eb artikujt ekzistues ose t\u00eb shkruajn\u00eb t\u00eb rinj.<\/p>\n<h3>Dokumentacioni nuk p\u00ebrmir\u00ebsohet<\/h3>\n<p>\n\u00cbsht\u00eb e v\u00ebshtir\u00eb t\u00eb b\u00ebsh gjith\u00e7ka perfekte nga fillimi, gabime do t\u00eb ket\u00eb p\u00ebrher\u00eb. Mund t\u00eb shpresojm\u00eb n\u00eb reagime nga klient\u00ebt, por pak i ndihmojn\u00eb ata q\u00eb t\u00eb raportojn\u00eb p\u00ebr \u00e7do gabim shtypi, pasakt\u00ebsi, artikuj t\u00eb paqart\u00eb ose t\u00eb paq\u00ebn\u00eb. P\u00ebrve\u00e7 klient\u00ebve, dokumentacionin e lexojn\u00eb edhe punonj\u00ebsit, k\u00ebshtu q\u00eb ata shohin t\u00eb nj\u00ebjtat gabime. Kjo mund t\u00eb p\u00ebrdoret! Duhet thjesht t\u00eb krijoni kushte ku do t\u00eb jet\u00eb e leht\u00eb t\u00eb raportosh p\u00ebr nj\u00eb problem.<\/p>\n<p>Ne kemi nj\u00eb grup n\u00eb portalin e brendsh\u00ebm, ku punonj\u00ebsit l\u00ebn\u00eb v\u00ebrejtje, sugjerime dhe ide p\u00ebr dokumentacionin. Sapo mb\u00ebshtetjes i nevojitet nj\u00eb artikull dhe ai nuk ekziston? Nj\u00eb testues vuri re nj\u00eb pasakt\u00ebsi? Nj\u00eb partner u ankuar menaxher\u00ebve t\u00eb zhvillimit p\u00ebr gabime? Gjith\u00e7ka shkon n\u00eb k\u00ebt\u00eb grup! Shkrimtar\u00ebt teknik\u00eb korrigjojn\u00eb disa gj\u00ebra menj\u00ebher\u00eb, disa i transferojn\u00eb n\u00eb YouTrack, disa i marrin p\u00ebr t'u menduar. Q\u00eb tema t\u00eb mos shuhet, her\u00eb pas here ne i kujtojm\u00eb ekzistenc\u00ebn e grupit dhe r\u00ebnd\u00ebsin\u00eb e reagimeve.<\/p>\n<h2>Problemi 3. Artikulli i nevojsh\u00ebm \u00ebsht\u00eb i v\u00ebshtir\u00eb p\u00ebr t'u gjetur<\/h2>\n<p>\nNj\u00eb artikull q\u00eb nuk mund t\u00eb gjendet, nuk \u00ebsht\u00eb m\u00eb i mir\u00eb se nj\u00eb artikull q\u00eb nuk ekziston. Motoja e dokumentacionit t\u00eb mir\u00eb duhet t\u00eb jet\u00eb fraza \"Leht\u00eb p\u00ebr t'u k\u00ebrkuar, leht\u00eb p\u00ebr t'u gjetur\". Si mund ta arrijm\u00eb k\u00ebt\u00eb?<\/p>\n<p><b>Organizoni struktur\u00ebn dhe p\u00ebrcaktoni parimin e zgjedhjes s\u00eb temave<\/b>. Struktura duhet t\u00eb jet\u00eb sa m\u00eb e qart\u00eb, q\u00eb lexuesi t\u00eb mos pyetet \"Ku mund ta gjej k\u00ebt\u00eb artikull?\". N\u00ebse e p\u00ebrmbledhim, ekzistojn\u00eb dy qasje: nga nd\u00ebrfaqja dhe nga detyrat.<\/p>\n<ol>\n<li>Nga nd\u00ebrfaqja. P\u00ebrmbajtja p\u00ebrputhet me seksionet e panelit. K\u00ebshtu ka qen\u00eb n\u00eb dokumentacionin e vjet\u00ebr t\u00eb ISPsystem.<\/li>\n<li>Nga detyrat. Titujt e artikujve dhe seksioneve reflektojn\u00eb detyrat e p\u00ebrdoruesve; n\u00eb tituj pothuajse gjithmon\u00eb ka folje dhe p\u00ebrgjigje ndaj pyetjes \"si t\u00eb b\u00ebsh\". Tani po kalojm\u00eb n\u00eb nj\u00eb format t\u00eb till\u00eb.<\/li>\n<\/ol>\n<p>\nPavar\u00ebsisht se cila qasje zgjidhni, sigurohuni q\u00eb tema p\u00ebrputhet me k\u00ebrkesat e p\u00ebrdoruesve dhe \u00ebsht\u00eb trajtuar n\u00eb m\u00ebnyr\u00ebn q\u00eb p\u00ebrdoruesi t\u00eb zgjidh\u00eb sakt\u00ebsisht pyetjen e tij.<\/p>\n<p><b>T\u00eb vendosni nj\u00eb k\u00ebrkim t\u00eb centralizuar<\/b>. N\u00eb nj\u00eb bot\u00eb ideale, k\u00ebrkimi duhet t\u00eb funksionoj\u00eb, edhe kur b\u00ebni nj\u00eb gabim n\u00eb shkronja ose n\u00eb gjuh\u00eb. K\u00ebrkimi yn\u00eb n\u00eb Confluence ende nuk mund t\u00eb ofroj\u00eb k\u00ebt\u00eb. N\u00ebse keni shum\u00eb produkte, dhe dokumentacioni \u00ebsht\u00eb i p\u00ebrbashk\u00ebt, p\u00ebrshtatni k\u00ebrkimin sipas faqes ku ndodhet p\u00ebrdoruesi. N\u00eb rastin ton\u00eb, k\u00ebrkimi n\u00eb krye punon p\u00ebr t\u00eb gjitha produktet, dhe n\u00ebse jeni tashm\u00eb n\u00eb nj\u00eb seksion t\u00eb caktuar, at\u00ebher\u00eb vet\u00ebm p\u00ebr artikujt n\u00eb t\u00eb.<\/p>\n<p><b>Shtoni p\u00ebrmbajtje dhe \"buk\u00eb me krimba\"<\/b>. \u00cbsht\u00eb mir\u00eb kur n\u00eb \u00e7do faqe ka nj\u00eb menu dhe buk\u00eb me krimba \u2014 rruga e p\u00ebrdoruesit deri n\u00eb faqen aktuale me mund\u00ebsin\u00eb p\u00ebr t\u00eb rikthyer n\u00eb \u00e7do nivel. N\u00eb dokumentacionin e vjet\u00ebr t\u00eb ISPsystem, duhej t\u00eb dilje nga artikulli p\u00ebr t\u00eb hyr\u00eb n\u00eb p\u00ebrmbajtje. Ishte e pak\u00ebndshme, prandaj n\u00eb t\u00eb reja e kemi korrigjuar k\u00ebt\u00eb.<\/p>\n<p><b>Vendosni lidhje n\u00eb produkt<\/b>. N\u00ebse njer\u00ebzit vazhdojn\u00eb t\u00eb vij\u00eb n\u00eb mb\u00ebshtetje me t\u00eb nj\u00ebjtin pyetje, \u00ebsht\u00eb e arsyeshme t\u00eb shtoni nj\u00eb sugjerim me zgjidhjen e tij n\u00eb nd\u00ebrfaqe. N\u00ebse keni t\u00eb dh\u00ebna ose kuptim, p\u00ebr momentin kur p\u00ebrdoruesi p\u00ebrballet me problemin, mund t\u00eb njoftoni gjithashtu me nj\u00eb newsletter. Do t'i tregoni kujdes dhe do t\u00eb leht\u00ebsoni ngarkes\u00ebn nga mb\u00ebshtetja.<\/p>\n<p><img decoding=\"async\" alt=\"Dokumentacioni i p\u00ebrdoruesit: \u00e7far\u00eb e b\u00ebn at\u00eb t\u00eb dob\u00ebt dhe si ta rregullojm\u00eb\" src=\"\/wp-content\/uploads\/2019\/03\/ddf030647cf3271e0e34924ff5c8116f.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>N\u00eb an\u00ebn e djatht\u00eb n\u00eb dritaren e ngjitur, lidhja p\u00ebr artikullin mbi konfigurimin e DNSSEC n\u00eb seksionin e menaxhimit t\u00eb domain-eve ISPmanager<\/i><\/p>\n<p><b>Konfiguroni lidhje kry crosses brenda dokumentacionit<\/b>Artikujt q\u00eb jan\u00eb t\u00eb lidhur mes tyre duhet t\u00eb jen\u00eb \"t\u00eb lidhur\". N\u00ebse artikujt p\u00ebrb\u00ebjn\u00eb nj\u00eb seri, sigurohuni q\u00eb t\u00eb shtoni n\u00eb fund t\u00eb \u00e7do teksti shigjeta p\u00ebrpara dhe prapa.<\/p>\n<blockquote><p>Me siguri, nj\u00eb person fillimisht do t\u00eb shkoj\u00eb t\u00eb k\u00ebrkoj\u00eb p\u00ebrgjigjen p\u00ebr pyetjen e tij, jo te ju, por n\u00eb motorin e k\u00ebrkimit. \u00cbsht\u00eb e m\u00ebrzitshme n\u00ebse nuk ka lidhje me dokumentacionin p\u00ebr shkak t\u00eb arsyeve teknike. Pra, kujdesuni p\u00ebr optimizimin e motor\u00ebve t\u00eb k\u00ebrkimit.<\/p><\/blockquote>\n<p><\/p>\n<h2>Problemi 4. Dizajni i vjet\u00ebr pengon perceptimin<\/h2>\n<p>\nP\u00ebrve\u00e7 teksteve t\u00eb k\u00ebqija, dizajni mund t\u00eb prish\u00eb dokumentacionin. Njer\u00ebzit jan\u00eb m\u00ebsuar t\u00eb lexojn\u00eb materiale t\u00eb hartuara mir\u00eb. Bloget, rrjetet sociale, median - gjith\u00eb p\u00ebrmbajtja paraqitet jo vet\u00ebm bukur, por edhe n\u00eb m\u00ebnyr\u00eb t\u00eb leht\u00eb p\u00ebr lexim, e k\u00ebndshme p\u00ebr sy. Prandaj, \u00ebsht\u00eb e leht\u00eb t\u00eb kuptohet dhimbja e atij q\u00eb sheh tekstin si n\u00eb screenshotin m\u00eb posht\u00eb. <\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/hsto.org\/webt\/en\/8-\/3q\/en8-3qj_jpwfiie91efwo_igqtk.png\"><img decoding=\"async\" alt=\"Dokumentacioni i p\u00ebrdoruesit: \u00e7far\u00eb e b\u00ebn at\u00eb t\u00eb dob\u00ebt dhe si ta rregullojm\u00eb\" src=\"\/wp-content\/uploads\/2019\/03\/0a0762670770950d062e1cd4c0f33f1d.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n<i>N\u00eb k\u00ebt\u00eb artikull jan\u00eb kaq shum\u00eb screenshot-e dhe theksime saq\u00eb ato nuk ndihmojn\u00eb, por vet\u00ebm pengojn\u00eb perceptimin (imazhi \u00ebsht\u00eb i klikuesh\u00ebm)<\/i><\/p>\n<p>Nuk \u00ebsht\u00eb e nevojshme t\u00eb b\u00ebni nga dokumentacioni nj\u00eb l\u00ebnd\u00eb t\u00eb gjat\u00eb me shum\u00eb efekte, por rregullat bazike duhet t\u00eb merren parasysh. <\/p>\n<p><b>Dizajni<\/b>P\u00ebrcaktoni gjer\u00ebsi e tekstit kryesor, fontin, madh\u00ebsin\u00eb, titujt dhe hap\u00ebsirat. Angazhoni nj\u00eb dizajner, dhe p\u00ebr t\u00eb pranuar pun\u00ebn ose p\u00ebr t'u p\u00ebrballur vet\u00eb, lexoni librin e Artem Gorbunov \"Tipografia dhe dizajni\". N\u00eb t\u00eb paraqitet vet\u00ebm nj\u00eb nga pik\u00ebpamjet p\u00ebr dizajnin, por kjo \u00ebsht\u00eb mjaft e mjaftueshme.<\/p>\n<p><b>Theksimet<\/b>P\u00ebrcaktoni se \u00e7far\u00eb k\u00ebrkon theksim n\u00eb tekst. Zakonisht, kjo \u00ebsht\u00eb rruga n\u00eb nd\u00ebrfaqe, butonat, shkurtimet e kodit, skedar\u00ebt konfiguruese, blloqet \"Kujdesi ju lutem\". Vendosni se si do t\u00eb jen\u00eb theksimet e k\u00ebtyre elementeve dhe vendosni at\u00eb n\u00eb rregullore. Mbani n\u00eb mend se sa m\u00eb pak theksime, aq m\u00eb mir\u00eb. Kur ka shum\u00eb, teksti \"b\u00ebn\u00eb zhurm\u00eb\". Zhurma krijohet madje edhe nga thonjt\u00eb, n\u00ebse p\u00ebrdoren shum\u00eb shpesh.<\/p>\n<p><b>Screenshot-e<\/b>Bashk\u00ebpunoni me ekipin tuaj p\u00ebr t\u00eb p\u00ebrcaktuar se n\u00eb cilat raste nevojiten screenshot-e. Ilustruar \u00e7do hap n\u00eb m\u00ebnyr\u00eb t\u00eb sakt\u00eb nuk \u00ebsht\u00eb e nevojshme. Nj\u00eb num\u00ebr i madh screenshot-esh, p\u00ebrfshir\u00eb butonat e ve\u00e7ant\u00eb, pengon perceptimin, prish dizajnin. P\u00ebrcaktoni madh\u00ebsin\u00eb, si dhe format e theksimeve dhe n\u00ebnshkrimeve n\u00eb screenshot-e, regulloni ato n\u00eb rregullore. Kujdesuni q\u00eb ilustarimet gjithmon\u00eb t\u00eb p\u00ebrputhen me at\u00eb q\u00eb \u00ebsht\u00eb shkruar dhe t\u00eb jen\u00eb aktuale. S\u00ebrish, n\u00ebse produkti p\u00ebrdit\u00ebsohet rregullisht, ndjekja e \u00e7do ndryshimi do t\u00eb jet\u00eb e v\u00ebshtir\u00eb.<\/p>\n<p><b>Gjat\u00ebsia e tekstit<\/b>. Shmangni mbi artikujt shum\u00eb t\u00eb gjat\u00eb. Ndajini ata n\u00eb pjes\u00eb, dhe n\u00ebse nuk \u00ebsht\u00eb e mundur, shtoni nj\u00eb p\u00ebrmbajtje me lidhje ankolike n\u00eb fillim t\u00eb artikujve. Nj\u00eb m\u00ebnyr\u00eb e thjesht\u00eb p\u00ebr ta b\u00ebr\u00eb artikullin t\u00eb duket vizualisht m\u00eb i shkurt\u00ebr \u00ebsht\u00eb t\u00eb fshihet detajet teknike, t\u00eb cilat jan\u00eb t\u00eb nevojshme p\u00ebr nj\u00eb grup t\u00eb ngusht\u00eb lexuesish, n\u00ebn nj\u00eb spoiler.<\/p>\n<p><b>Formate<\/b>. Kombinoni disa formate n\u00eb artikuj: tekst, video dhe imazhe. Kjo do ta p\u00ebrmir\u00ebsoj\u00eb perceptimin. <\/p>\n<blockquote><p>Mos u p\u00ebrpiqni t\u00eb mbuloni problemet me dizajn t\u00eb bukur. Sinqerisht, ne vet\u00eb shpresonim se \"pakoja\" do ta shp\u00ebtonte dokumentacionin e vjetruar - por nuk ndodhi. N\u00eb tekstet kishte kaq shum\u00eb zhurm\u00eb vizuale dhe detaje t\u00eb panevojshme, saq\u00eb rregullorja dhe dizajni i ri ishin t\u00eb pamjaftueshme.<\/p><\/blockquote>\n<p>\nShum\u00eb nga ato q\u00eb u p\u00ebrmenden m\u00eb sip\u00ebr do t\u00eb p\u00ebrcaktohen nga platforma q\u00eb po p\u00ebrdorni p\u00ebr dokumentacionin. P\u00ebr ne, p\u00ebr shembull, \u00ebsht\u00eb Confluence. Kemi pasur gjithashtu disa v\u00ebshtir\u00ebsi me t\u00eb. N\u00ebse jeni t\u00eb interesuar, lexoni tregimin e zhvilluesit ton\u00eb t\u00eb uebit: <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ispsystem\/blog\/438236\/\">Confluence p\u00ebr baz\u00ebn e njohurive publike: po ndryshojm\u00eb dizajnin dhe rregullojm\u00eb ndarjen sipas gjuh\u00ebve<\/a><\/noindex>.<\/p>\n<h2>Nga duhet t\u00eb filloni p\u00ebrmir\u00ebsimet dhe si t\u00eb mbijetoni<\/h2>\n<p>\nN\u00ebse dokumentacioni juaj \u00ebsht\u00eb po aq i gjer\u00eb sa ai i ISPsystem dhe nuk dini nga t\u00eb filloni, filloni me problemet m\u00eb serioze. Klient\u00ebt nuk kuptojn\u00eb dokumentacionin - meruni me p\u00ebrmir\u00ebsimin e teksteve, krijoni rregullore, trajnojn\u00eb shkruesit. Dokumentacioni nuk \u00ebsht\u00eb i p\u00ebrdit\u00ebsuar - meruni me proceset e brendshme. Filloni me artikujt m\u00eb t\u00eb njohur p\u00ebr produktet m\u00eb t\u00eb k\u00ebrkuara: pyesni mb\u00ebshtetjes, shikoni analizat e faqes dhe k\u00ebrkesat n\u00eb motor\u00ebt e k\u00ebrkimit. <\/p>\n<p>T\u00eb themi t\u00eb drejt\u00ebn - nuk do t\u00eb jet\u00eb e leht\u00eb. Dhe gjithashtu, shpejt nuk do t\u00eb ndodh\u00eb. P\u00ebrve\u00e7 n\u00ebse sapo keni filluar dhe e b\u00ebni gjith\u00e7ka si\u00e7 duhet nga fillimi. Nj\u00eb gj\u00eb e dim\u00eb me siguri - me kalimin e koh\u00ebs do t\u00eb b\u00ebhet m\u00eb mir\u00eb. Por procesi nuk do t\u00eb p\u00ebrfundoj\u00eb kurr\u00eb :-).<\/p>\n<p>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ispsystem\/blog\/443648\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0414\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044f \u043a \u0441\u043e\u0444\u0442\u0443 \u2014 \u044d\u0442\u043e \u043f\u0440\u043e\u0441\u0442\u043e \u043d\u0430\u0431\u043e\u0440 \u0441\u0442\u0430\u0442\u0435\u0439. \u041d\u043e \u0434\u0430\u0436\u0435 \u043e\u043d\u0438 \u043c\u043e\u0433\u0443\u0442 \u0432\u044b\u0432\u0435\u0441\u0442\u0438 \u0438\u0437 \u0441\u0435\u0431\u044f. \u0421\u043d\u0430\u0447\u0430\u043b\u0430 \u0434\u043e\u043b\u0433\u043e \u0438\u0449\u0435\u0448\u044c \u043d\u0443\u0436\u043d\u0443\u044e \u0438\u043d\u0441\u0442\u0440\u0443\u043a\u0446\u0438\u044e. \u041f\u043e\u0442\u043e\u043c \u0440\u0430\u0437\u0431\u0438\u0440\u0430\u0435\u0448\u044c\u0441\u044f \u0432 \u043c\u0430\u043b\u043e\u043f\u043e\u043d\u044f\u0442\u043d\u043e\u043c \u0442\u0435\u043a\u0441\u0442\u0435. \u0414\u0435\u043b\u0430\u0435\u0448\u044c \u043a\u0430\u043a \u043d\u0430\u043f\u0438\u0441\u0430\u043d\u043e, \u0430 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043d\u0435 \u0440\u0435\u0448\u0430\u0435\u0442\u0441\u044f. \u0418\u0449\u0435\u0448\u044c \u0434\u0440\u0443\u0433\u0443\u044e \u0441\u0442\u0430\u0442\u044c\u044e, \u043d\u0435\u0440\u0432\u043d\u0438\u0447\u0430\u0435\u0448\u044c\u2026 \u0427\u0435\u0440\u0435\u0437 \u0447\u0430\u0441 \u043f\u043b\u044e\u0451\u0448\u044c \u043d\u0430 \u0432\u0441\u0451 \u0438 \u0443\u0445\u043e\u0434\u0438\u0448\u044c. \u0422\u0430\u043a \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u043f\u043b\u043e\u0445\u0430\u044f \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044f. \u0427\u0442\u043e \u0434\u0435\u043b\u0430\u0435\u0442 \u0435\u0451 \u0442\u0430\u043a\u043e\u0439, \u0438 \u043a\u0430\u043a \u044d\u0442\u043e \u0438\u0441\u043f\u0440\u0430\u0432\u0438\u0442\u044c [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-42119","post","type-post","status-publish","format-standard","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.1.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0414\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044f \u043a.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/news\/polzovatelskaya-dokumentatsiya-chto-delaet-eyo-plohoj-i-kak-eto-ispravit\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u0441\u043a\u0430\u044f \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044f: \u0447\u0442\u043e \u0434\u0435\u043b\u0430\u0435\u0442 \u0435\u0451 \u043f\u043b\u043e\u0445\u043e\u0439, \u0438 \u043a\u0430\u043a \u044d\u0442\u043e \u0438\u0441\u043f\u0440\u0430\u0432\u0438\u0442\u044c | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0414\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044f \u043a.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/news\/polzovatelskaya-dokumentatsiya-chto-delaet-eyo-plohoj-i-kak-eto-ispravit\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-03-17T21:00:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-02-18T10:44:55+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Dokumentacioni i p\u00ebrdoruesit: \u00e7far\u00eb e b\u00ebn at\u00eb t\u00eb keqe dhe si ta rregullojm\u00eb | ProHoster","description":"Dokumentacioni p\u00ebr.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/news\/polzovatelskaya-dokumentatsiya-chto-delaet-eyo-plohoj-i-kak-eto-ispravit","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u0441\u043a\u0430\u044f \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044f: \u0447\u0442\u043e \u0434\u0435\u043b\u0430\u0435\u0442 \u0435\u0451 \u043f\u043b\u043e\u0445\u043e\u0439, \u0438 \u043a\u0430\u043a \u044d\u0442\u043e \u0438\u0441\u043f\u0440\u0430\u0432\u0438\u0442\u044c | ProHoster","og:description":"\u0414\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044f \u043a.","og:url":"https:\/\/prohoster.info\/sq\/blog\/news\/polzovatelskaya-dokumentatsiya-chto-delaet-eyo-plohoj-i-kak-eto-ispravit","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-03-17T21:00:00+00:00","article:modified_time":"2020-02-18T10:44:55+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"42119","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-22 07:20:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 00:05:22","updated":"2026-01-22 07:20:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/42119","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=42119"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/42119\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=42119"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=42119"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=42119"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}