edit-article
Home
Up
Delete
Article Name:
Article Description:
] DECISION to continue using our unique/proprietary PAGE DOCUMENTATION process over more conventional DOCU methodologies
Chapter ID/Name:
Status:
Write
Writing
Written
Add Photo:
Owner ID:
Content:
use HTML
Edit Content
<h1 style="text-align: center;">DECISION - keep PAGE PRODUCTION documenting process as is?</h1> <h2>[WHAT]</h2> <ol> <li>] by Don Sagrott founder@ sospep.com - ] DECISION to continue using our unique/proprietary PAGE DOCUMENTATION process over more conventional DOCU methodologies</li> <li>] documentation updates - project-022 - about PAGES, PAGES-sospep, PAGE-VERSIONS, VERSION-PAGES, COMPONENTS and more</li> <li>] with the current system, all/any changes to each/any page on the site/in the application, ARE documented on the docU page that corresponds to the physical site page/file. This is time consuming, </li> </ol> <h2>[WHY]</h2> <ol> <li><strong>] ? = how much documenting do we need?</strong></li> <ol> <li>] # # - </li> </ol> <li><strong>] ? = Do we need/want to continue with the present documenting process? </strong></li> <ol> <li>] Do we use the documentation? -somewhat</li> <li>] Is there a better process? -likely</li> </ol> <li><strong>] ? = we currently have PAGE 'task records', do we also need/want 'PAGE article records'(as above) for each PAGE-task?</strong>, </li> <ol> <li>] currently the task PAGE contains the 'PAGE article' content, ++ the PAGE task content </li> <li>] -YES - because - </li> </ol> <li><strong>] ? = should we seperate out other SITE elements like SCRIPT and CSS files? </strong></li> <ol> <li>] # # - </li> <li>] -YES - because - </li> </ol> <li><strong>*] * </strong></li> <ol> <li>] doing daily documenting tasks VS Plan-month, Plan-week ADDS another LAYER to the overall docU process, </li> </ol></ol> <h2>[WHERE]</h2> <ol> <li><strong>] READ THE FULL ARTICLE</strong></li> <ol> <li>] </li> </ol></ol> <h2>[WHEN]</h2> <ol> <li>] 2016-12-09</li> </ol> <h2>[EXAMPLE]</h2> <ol> <li><strong>] currently HAVE tgrs for 'PAGE-tasks' IN prj-022/planning-projcts = </strong></li> <ol> <li>] # 436 - PAGES</li> <li>] # 437 - PAGE-VERSIONS</li> <li>] # 551 - PAGE-COMPONENTs</li> </ol> <li><strong>] currently HAVE tgrs for 'PAGE-tasks' IN prj-022/documenting-projects = </strong></li> <ol> <li>] # 159 - PAGES-sospep</li> <li>] # 169 - PAGES-sospep-subjects</li> <li>] # 170 - PAGES-sospep-objects</li> <li>] # 171 - PAGES-sospep-systems</li> <li>] # 172 - PAGES-sospep-people</li> <li>] # 173 - PAGES-sospep-events</li> <li>] # 174 - PAGES-sospep-places</li> <li>] # 342 - PAGE-COMPONENTs</li> <li>] # 154 - VERSIONS-PAGES-sospep</li> <li>] # 224 - VERSIONS-PAGES-subjects</li> <li>] # 225 - VERSIONS-PAGES-objects</li> <li>] # 226 - VERSIONS-PAGES-systems</li> <li>] # 227 - VERSIONS-PAGES-people</li> <li>] # 228 - VERSIONS-PAGES-events</li> <li>] # 229 - VERSIONS-PAGES-places</li> <li><span style="background-color: #c0c0c0;">] # 166 - VERSIONS-PAGES-M</span></li> <li><span style="background-color: #c0c0c0;">] # 289 - PAGES-api</span></li> <li><span style="background-color: #c0c0c0;">] # 165 - PAGES-M</span></li> </ol> <li><strong>] ALSO currently HAVE some 'PAGE-articles' in prj-022/sospep-version/beta-2016-11 and ...</strong></li> <ol> <li>] # # - PAGE</li> <li>] # # - PAGE</li> <li>] # # - PAGE </li> <li>] # # - ... </li> </ol> <li><strong>[00:00] currently HAVE in Y <a href="/view/steps?id=28" target="_blank">prj-022/feature</a> </strong></li> <ol> <li>] # # - step by step for creating "NEW FEATURE" dcoumentation, from the intial design documentation, to all steps in the production process, to marketing the completed results </li> </ol> <li><strong>[00:00] currently HAVE in Y <a href="/view/steps?id=27" target="_blank">prj-022/page</a></strong></li> <ol> <li>] # # - step by step for creating PAGE documentation. (this would be part of the "overall feature production"</li> <li>*] also have procedures for ] FIX-PRB/PRB-SOL and ] FIND-*</li> </ol></ol> <h2>[HOW-TO]</h2> <ol> <li>]</li> </ol> <h2>[REFERENCE]</h2> <ol> <li>] # 6633 - CREATE-article# # - DECISION-documenting-process </li> </ol> <h1 style="text-align: center;"> </h1>