Skip to content

sdtonkin/demo

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

#Introduction Wireframes http://xsi0nx.axshare.com/#p=homepage

Visual Comp https://invis.io/3SC57UN7X

Mobile Screens https://invis.io/MRC9N002C

https://zeplin.io/ UN: rp_creative PW: Zeplin

Tech Design https://rpo365.sharepoint.com/sites/ExtranetCompassionInter/O365Intranet/Documents/Technical%20Design/Compassion%20-%20Tech%20Design.docx?d=w5fa44bb5a2db42fca0565ce6ea0d8984

#Getting Started

  1. Install prerequisites Visual Studio 2015 Update 2 NodeJS: https://nodejs.org/download/
  2. Get the solution Run Visual Studio as an administrator (always). Connect to the Visual Studio Online Team Project Name or URL: rightpoint.visualstudio.com, Project: OCCU - Website Replatform https://rightpoint.visualstudio.com/COM%20-%20O365%20Intranet From Unsynced Commits, do a Pull to pull down the entire repository.

#Communication Rules

  1. Expect Daily Check-ins – Be prepared.
  2. Update tasks prior to meeting
  3. Stick to the check-in topics What did you accomplish since last check-in? What are plan on accomplishing between now and next check-in? Do you have any roadblocks? Do you need assistance with any of your tasks?
  4. Add meaningful comments in source control – be specific about the files you touched.
  5. If you need to skip a check-in meeting, please provide update via email.

#Development Rules

  1. Structure your estimates Example of an 8 hour task: How time goes to coding?: 4 hours How much time goes to testing?: 1 hour How much time goes to bug fixing?: 2 hour How much time for a buffer?: 1 hour If you use up all of your coding time (4 hours in the example above) and your not done yet, raise a red flag. Contact the tech lead or the arch for assistance.
  2. Commit your changes on the completion of each task. Adding reference to task in the comments is preferred.
  3. Changes made to the solution should only be executed through the deployment mechanism. Do not make manual changes to the Test or Production environment.
  4. Get confirmation before starting a task. Some tasks may have dependencies.

#SharePoint Best Practices

  1. Always use PnP for data operations.
  2. Use web part titles when possible. Avoid embedding the title of a component within JavaScript code.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published