article

DECISION - keep PAGE PRODUCTION documenting process as is?

[WHAT]

  1. ] by Don Sagrott founder@ sospep.com -  ] DECISION to continue using our unique/proprietary PAGE DOCUMENTATION process over more conventional DOCU methodologies
  2. ] documentation updates - project-022 - about PAGES, PAGES-sospep, PAGE-VERSIONS, VERSION-PAGES, COMPONENTS and more
  3. ] 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, 

[WHY]

  1. ] ? = how much documenting do we need?
    1. ] # # - 
  2. ] ? = Do we need/want to continue with the present documenting process? 
    1. ] Do we use the documentation? -somewhat
    2. ] Is there a better process? -likely
  3. ] ? = we currently have PAGE 'task records', do we also need/want 'PAGE article records'(as above) for each PAGE-task?, 
    1. ] currently the task PAGE contains the 'PAGE article' content, ++ the PAGE task content 
    2. ] -YES - because -  
  4. ] ? = should we seperate out other SITE elements like SCRIPT and CSS files? 
    1. ] # # - 
    2. ] -YES - because - 
  5. *] * 
    1. ] doing daily documenting tasks VS Plan-month, Plan-week ADDS another LAYER to the overall docU process, 

[WHERE]

  1. ] READ THE FULL ARTICLE
    1. ] 

[WHEN]

  1. ] 2016-12-09

[EXAMPLE]

  1. ] currently HAVE tgrs for 'PAGE-tasks' IN prj-022/planning-projcts = 
    1. ] # 436 - PAGES
    2. ] # 437 - PAGE-VERSIONS
    3. ] # 551 - PAGE-COMPONENTs
  2. ] currently HAVE tgrs for 'PAGE-tasks' IN prj-022/documenting-projects = 
    1. ] # 159 - PAGES-sospep
    2. ] # 169 - PAGES-sospep-subjects
    3. ] # 170 - PAGES-sospep-objects
    4. ] # 171 - PAGES-sospep-systems
    5. ] # 172 - PAGES-sospep-people
    6. ] # 173 - PAGES-sospep-events
    7. ] # 174 - PAGES-sospep-places
    8. ] # 342 - PAGE-COMPONENTs
    9. ] # 154 - VERSIONS-PAGES-sospep
    10. ] # 224 - VERSIONS-PAGES-subjects
    11. ] # 225 - VERSIONS-PAGES-objects
    12. ] # 226 - VERSIONS-PAGES-systems
    13. ] # 227 - VERSIONS-PAGES-people
    14. ] # 228 - VERSIONS-PAGES-events
    15. ] # 229 - VERSIONS-PAGES-places
    16. ] # 166 - VERSIONS-PAGES-M
    17. ] # 289 - PAGES-api
    18. ] # 165 - PAGES-M
  3. ] ALSO currently HAVE some 'PAGE-articles' in prj-022/sospep-version/beta-2016-11 and ...
    1. ] # # - PAGE
    2. ] # # - PAGE
    3. ] # # - PAGE 
    4. ] # # - ... 
  4. [00:00] currently HAVE in Y prj-022/feature 
    1. ] # # - 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 
  5. [00:00] currently HAVE in Y prj-022/page
    1. ] # # - step by step for creating PAGE documentation. (this would be part of the "overall feature production"
    2. *] also have procedures for ] FIX-PRB/PRB-SOL and ] FIND-*

[HOW-TO]

  1. ]

[REFERENCE]

  1. ] # 6633 - CREATE-article# # - DECISION-documenting-process 

 

Details Photos Edit more

Details

ID: 5456

NAME: DECISION-page-documentation

DESCRIPTION: ] DECISION to continue using our unique/proprietary PAGE DOCUMENTATION process over more conventional DOCU methodologies

AUTHOR: article.author/s

EDITOR: article.editor/s

PUBLISHER: article.publisher/s

STATUS: Write

PRIORITY: -5

OWNER ID: 75

Content Photos Edit more

photos

page_photo

actions

Email Email-Owner SMS and