{"id":35419,"date":"2019-10-31T22:04:14","date_gmt":"2019-10-31T19:04:14","guid":{"rendered":"https:\/\/prohoster.info\/blog\/ispolzujte-git-pri-dokumentirovanii\/"},"modified":"2019-10-31T22:04:14","modified_gmt":"2019-10-31T19:04:14","slug":"ispolzujte-git-pri-dokumentirovanii","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/ispolzujte-git-pri-dokumentirovanii","title":{"rendered":"P\u00ebrdorni GIT p\u00ebr dokumentimin","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Ndonj\u00ebher\u00eb jo vet\u00ebm dokumentacioni vet\u00eb, por edhe procesi i pun\u00ebs mbi t\u00eb mund t\u00eb jet\u00eb kritik. P\u00ebr shembull, n\u00eb rastin e projekteve, pjesa m\u00eb e madhe e pun\u00ebs \u00ebsht\u00eb e lidhur pik\u00ebrisht me p\u00ebrgatitjen e dokumentacionit, dhe nj\u00eb proces i gabuar mund t\u00eb \u00e7oj\u00eb n\u00eb gabime dhe madje n\u00eb humbje informacioni, dhe, p\u00ebr pasoj\u00eb, n\u00eb humbje kohe dhe p\u00ebrfitimi. Por edhe n\u00ebse kjo tem\u00eb nuk \u00ebsht\u00eb qendrore n\u00eb pun\u00ebn tuaj dhe ndodhet n\u00eb periferin\u00eb, prap\u00eb procesi i duhur mund t\u00eb p\u00ebrmir\u00ebsoj\u00eb cil\u00ebsin\u00eb e dokumentit dhe t\u00eb kursej\u00eb koh\u00eb.<\/p>\n

Qasja e paraqitur k\u00ebtu, me nj\u00eb shembull t\u00eb zbatimit konkret<\/a><\/noindex>, ka nj\u00eb prag t\u00eb ul\u00ebt t\u00eb hyrjes. Teknikisht, q\u00eb nes\u00ebr mund t\u00eb filloni t\u00eb punoni ndryshe.
\n<\/a><\/noindex><\/p>\n

Formulimi i detyr\u00ebs<\/h3>\n

\nJu nevojitet t\u00eb krijoni nj\u00eb dokument ose nj\u00eb grup dokumentesh. Ndoshta, \u00ebsht\u00eb dokumentacion projekti ose protokollimi i rrjetit tuaj, ose di\u00e7ka m\u00eb e thjesht\u00eb, p\u00ebr shembull, duhet t\u00eb p\u00ebrshkruani proceset n\u00eb kompani ose n\u00eb departamentin tuaj. N\u00eb p\u00ebrgjith\u00ebsi, b\u00ebhet fjal\u00eb p\u00ebr \u00e7do dokument ose grup dokumentesh me tekst, imazhe, tabela... Ta nd\u00ebrlikojm\u00eb problemin duke marr\u00eb parasysh se <\/p>\n

    \n
  1. kjo pun\u00eb parasheh pun\u00eb bashk\u00ebpunuese, p\u00ebrpjekje t\u00eb nj\u00eb grupi ose disa grupeve t\u00eb punonj\u00ebsve<\/li>\n
  2. me rezultatin q\u00eb d\u00ebshironi t\u00eb keni nj\u00eb dokument n\u00eb nj\u00eb format t\u00eb caktuar, me atributet e stilit korporativ, i krijuar sipas nj\u00eb shablli t\u00eb caktuar. P\u00ebr t\u00eb qen\u00eb m\u00eb t\u00eb qart\u00eb do t\u00eb marr\u00ebim parasysh se kjo \u00ebsht\u00eb MS Word (.docx)<\/li>\n<\/ol>\n

    \n10 vite m\u00eb par\u00eb, qasja do t\u00eb ishte e qart\u00eb: do t\u00eb kishim krijuar nj\u00eb dokument MS Word ose dokumente dhe n\u00eb ndonj\u00eb form\u00eb do t\u00eb organizonim pun\u00ebn mbi ndryshimin e tyre. <\/p>\n

    Dhe ajo qasje ende mbetet n\u00eb fuqi. Ajo p\u00ebrdoret gjithashtu nga integrator\u00ebt e m\u00ebdhenj n\u00eb krijimin e dokumentacionit t\u00eb projekteve. Por \u00ebsht\u00eb intuitivisht e qart\u00eb se, n\u00ebse ju v\u00ebrtet punoni intensivisht, me shum\u00eb ndryshime dhe diskutime, p\u00ebr nj\u00eb periudh\u00eb t\u00eb gjat\u00eb kohore mbi nj\u00eb dokument, kjo qasje nuk \u00ebsht\u00eb shum\u00eb e p\u00ebrshtatshme.<\/p>\n

    Shembulli<\/b><\/p>\n

    E ndjeva mjaft ndjesh\u00ebm k\u00ebt\u00eb problem, duke punuar n\u00eb nj\u00eb integrator t\u00eb madh. Procesi i ndryshimit t\u00eb dokumentacionit projekti ishte si vijon:<\/p>\n

      \n
    1. injegjeri shkarkon versionin m\u00eb t\u00eb fundit t\u00eb dokumentit MS Word (.docx)<\/li>\n
    2. ndryshon emrin<\/li>\n
    3. b\u00ebn ndryshime n\u00eb modin track<\/li>\n
    4. d\u00ebrgon dokumentin me ndryshimet tek arkitekti<\/li>\n
    5. po ashtu d\u00ebrgon nj\u00eb list\u00eb t\u00eb t\u00eb gjitha rregullimeve me komente<\/li>\n
    6. arkitekti analizon ndryshimet<\/li>\n
    7. n\u00ebse gjith\u00e7ka \u00ebsht\u00eb n\u00eb rregull, at\u00ebher\u00eb kopjon k\u00ebto ndryshime n\u00eb dosjen me versionin m\u00eb t\u00eb fundit, ndryshon versionin dhe e shp\u00ebrndan n\u00eb burimin e p\u00ebrbashk\u00ebt<\/li>\n
    8. n\u00ebse ka v\u00ebrejtje, fillon diskutimi (email ose takime)<\/li>\n
    9. arrihet nj\u00eb konsensus<\/li>\n
    10. pastaj pikat 3 - 9<\/li>\n<\/ol>\n

      \nDerisa puna nuk ka qen\u00eb intensive, kjo ka funksionuar m\u00eb disa pengesa, por ndonj\u00ebher\u00eb ka ndodhur. Por n\u00eb nj\u00eb moment t\u00eb caktuar, ky proces u b\u00eb ngusht\u00ebsia e t\u00eb gjith\u00eb projektit dhe \u00e7oi n\u00eb probleme. Problemi \u00ebsht\u00eb se gjith\u00e7ka shkon keq sapo ndryshimet b\u00ebhen shpesh dhe nj\u00ebkoh\u00ebsisht nga disa ekipe.<\/p>\n

      K\u00ebshtu, kur kaluam n\u00eb faz\u00ebn e testimit t\u00eb parakohsh\u00ebm, filluan t\u00eb shfaqen disa probleme, dhe ndon\u00ebse ishin t\u00eb vogla, duhet t\u00eb ndryshohej shpesh dokumentacioni \u2014 kat\u00ebr ekipe t\u00eb ndryshme, \u00e7do dit\u00eb, praktikisht n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, me diskutime. T\u00eb gjitha k\u00ebto ndryshime kalonin p\u00ebrmes nj\u00eb inxhinieri \u2014 arkitektit. Skedari me dizajnin e projektit ishte i madh, dhe si pasoj\u00eb, arkitekti ishte i mbushur me pun\u00eb rutin\u00eb, q\u00eb kishte t\u00eb b\u00ebnte me nj\u00eb num\u00ebr t\u00eb madh kopjimesh dhe redaktimesh, b\u00ebnte shum\u00eb gabime, duhej t\u00eb kontrolloheshin t\u00eb gjitha, t\u00eb d\u00ebrgoheshin p\u00ebrs\u00ebri, dhe gjithsesi, kjo ishte af\u00ebr kaosit. <\/p>\n

      N\u00eb k\u00ebt\u00eb rast, ky qasje, qasja p\u00ebr pun\u00ebn mbi dokumentin MS Word, funksiononte me shum\u00eb v\u00ebshtir\u00ebsi dhe krijonte probleme.<\/p><\/blockquote>\n

      <\/p>\n

      Git, Markdown<\/h3>\n

      \nDuke u p\u00ebrballur me problemin e p\u00ebrshkruar n\u00eb shembullin e m\u00ebsip\u00ebrm, fillova t\u00eb hulumtoj k\u00ebt\u00eb \u00e7\u00ebshtje.
      \nPash\u00eb se po b\u00ebhet gjithnj\u00eb e m\u00eb popullor p\u00ebrdorimi i       Markdown<\/a><\/noindex> bashk\u00eb me Git<\/a><\/noindex> n\u00eb krijimin e dokumenteve.<\/p>\n

      Git \u00ebsht\u00eb nj\u00eb mjet p\u00ebr zhvillim. Por pse t\u00eb mos e p\u00ebrdorim at\u00eb p\u00ebr procesin e dokumentimit? N\u00eb k\u00ebt\u00eb rast, problemi i pun\u00ebs shum\u00ebp\u00ebrdoruese zgjidhet. Por p\u00ebr t\u00eb shfryt\u00ebzuar plot\u00ebsisht potencialin e Git, na nevojitet nj\u00eb format tekstual dokumenti, na nevojitet t\u00eb gjejm\u00eb nj\u00eb mjet tjet\u00ebr, jo MS Word, dhe p\u00ebr k\u00ebto q\u00ebllime, Markdown \u00ebsht\u00eb ideal. <\/p>\n

      Markdown \u00ebsht\u00eb nj\u00eb gjuh\u00eb e thjesht\u00eb e sh\u00ebnjimit t\u00eb tekstit. Ajo \u00ebsht\u00eb krijuar p\u00ebr t\u00eb krijuar tekste n\u00eb formate t\u00eb bukura n\u00eb skedar\u00ebt e zakonsh\u00ebm TXT. N\u00ebse ne krijojm\u00eb dokumentet tona n\u00eb Markdown, lidhja Markdown - Git duket natyrale.<\/p>\n

      E gjith\u00e7ka do t\u00eb ishte mir\u00eb, dhe n\u00eb k\u00ebt\u00eb pik\u00eb mund t\u00eb vendosnim nj\u00eb pik\u00eb, n\u00ebse nuk do t\u00eb ishte kushti yn\u00eb i dyt\u00eb: \"n\u00eb dalje na nevojitet nj\u00eb dokument n\u00eb nj\u00eb format t\u00eb caktuar, me atributet e stilit korporativ, i krijuar sipas nj\u00eb shablloni t\u00eb caktuar\" (dhe ne u dakorduam q\u00eb p\u00ebr qart\u00ebsi do t\u00eb p\u00ebrdorim MS Word). Pra, n\u00ebse vendosim t\u00eb p\u00ebrdorim Markdown, na nevojitet nj\u00eb m\u00ebnyr\u00eb p\u00ebr ta transformuar k\u00ebt\u00eb sked\u00eb n\u00eb .docx t\u00eb k\u00ebrkuar.<\/p>\n

      Eksistojn\u00eb programe konvertimi midis formateve t\u00eb ndryshme, p\u00ebr shembull, Pandoc<\/a><\/noindex>.
      \nMund t\u00eb konvertoni nj\u00eb sked\u00eb Markdown n\u00eb formatin .docx me k\u00ebt\u00eb program.
      \nMegjithat\u00eb, duhet ta kuptojm\u00eb se, n\u00eb radh\u00eb t\u00eb par\u00eb, nuk \u00e7do gj\u00eb q\u00eb \u00ebsht\u00eb n\u00eb Markdown do t\u00eb konvertohet n\u00eb MS Word dhe, n\u00eb t\u00eb dyt\u00eb, MS Word \u00ebsht\u00eb nj\u00eb vend i t\u00ebr\u00eb n\u00eb krahasim me qytetin e vog\u00ebl, Markdown. Ka nj\u00eb sasi t\u00eb madhe t\u00eb gjitha atyre q\u00eb jan\u00eb n\u00eb Word dhe nuk ekzistojn\u00eb n\u00eb asnj\u00eb form\u00eb n\u00eb Markdown. Nuk mund t\u00eb merrni thjesht dhe t\u00eb p\u00ebrdorni \u00e7el\u00ebsa t\u00eb caktuar n\u00eb Pandoc p\u00ebr t\u00eb konvertuar formatin tuaj Markdown n\u00eb pamjen e d\u00ebshiruar t\u00eb MS Word. Prandaj zakonisht, pas konvertimit, duhet t\u00eb \"p\u00ebrfundojm\u00eb\" dokumentin e .docx t\u00eb marr\u00eb manualisht, q\u00eb gjithashtu mund t\u00eb jet\u00eb e shtrenjt\u00eb n\u00eb aspektin e koh\u00ebs dhe t\u00eb shkaktoj\u00eb gabime.<\/p>\n

      N\u00ebse do t\u00eb mundnim t\u00eb shkruanim nj\u00eb skenar t\u00eb cilin automatikisht do t\u00eb \"d\u00ebnte\" at\u00eb q\u00eb Pandoc nuk e kishte mbuluar, do t\u00eb ishte zgjidhja perfekte.<\/p>\n

      P\u00ebr shkak t\u00eb mosidentitetit t\u00eb funksionalitetit t\u00eb MS Word dhe Markdown n\u00eb m\u00ebnyr\u00eb t\u00eb p\u00ebrgjithshme, mendoj se \u00ebsht\u00eb e pamundur t\u00eb zgjidhet kjo detyr\u00eb, por a \u00ebsht\u00eb e mundur ta realizojm\u00eb at\u00eb p\u00ebr situata specifike, k\u00ebrkesa specifike? P\u00ebrvoja ime ka treguar se po, \u00ebsht\u00eb e mundur dhe ndoshta e mundur p\u00ebr shum\u00eb, ose ndoshta edhe p\u00ebr shumic\u00ebn e situatave. <\/p>\n

      Zgjidhja e nj\u00eb detyre private<\/h3>\n

      \nPra, n\u00eb rastin tim, pas konvertimit t\u00eb sked\u00ebs me Pandoc, m\u00eb \u00ebsht\u00eb dashur t\u00eb b\u00ebj p\u00ebrpunim t\u00eb m\u00ebtejsh\u00ebm manual t\u00eb skedave, pra<\/p>\n