Skip to content
This repository has been archived by the owner on Dec 4, 2022. It is now read-only.

MVP Requirements

joshuahover edited this page Sep 14, 2021 · 16 revisions

Background

  1. Ability to have profile searchable
  2. MVP awards are presented as badges
  3. Gravatar (or similar) solution to display profile photos
  4. Optionally link to Twitter, LinkedIn, Community and StackExchange profiles

Requirements:

  • Ability to link to badges: https://github.com/Sitecore/MVP-Site/wiki/MVP-Badges
  • Search will be based on Name, category and year
  • Profile will be a Sitecore item: Tagging for category and year
  • Fields: Name, category, year, country, Gravatar (based on email/id), bio with text limit (2000 limit)
  • Badge entity would be based on year and category as this can change yearly
  • Based on initial import, will be able to update own profile

Background

  1. Users with the MVP flag should be able to “edit” their profile
  2. Gravatar email address
  3. Profile links
  4. Optional biography

Requirements

  1. Will be able to login through Okta
  2. Okta ID will be tied to profile
  3. Update Gravitar
  4. Profile links: LinkedIn Twitter
  5. Optional bio
  6. Location

Background

  1. Ability to import historical MVP nominee's into Sitecore
  2. Import will be performed through a job
  3. Ability to have tagging
  4. Ability to import into Sitecore from Excel file
  5. Import will include data from 2008 - 20021

Notes:

  1. What format works best? Should it be JSON or CSV. Or keep as Excel
  2. Format will be shared via email. Will update to include country

Requirements:


Background:

  1. Be able to log-in with External Okta account
  2. Will leverage Okta for front end only, will not be used for backend as this will add additional complexity
  3. Link MVP profiles to Okta accounts

Requirements:

  • Local host Url: https://mvp.sc.localhost
  • Single sign-on URL: to be shared via email
  • Logout URL: to be shared via email
  • Leverage openID protocol
  • Implicit flow w/ key
  • Determine how this is passed back from private server

Links

  1. https://github.com/Sitecore/MVP-Site/wiki/Okta-Integration-Details

Background:

  1. Search based on names and filters by category, country and year
  2. Display result with name, year+category (badge) and country
  3. Results will be displayed in a listview
  4. Leverage design for corp site. (Tamas to provide HTML)

Background

  1. Authenticated MVPs should be able to request a license through the portal
  2. Integrate with the LOS API
  3. Integrate with Developer Tools License API

Background

  1. Using Okta authentication Applicants can log in
  2. They can see if they are invited or not
    • Flag to show is able to apply
      • Could have it on the OKTA account
      • Or can be a flag on their profile
      • Need to grab save status to profile so that application can be saved
  3. Interface for Sitecore employees (separate site w/ internal Okta?) and existing MVPs (MVP flag) to invite (first recommendation) or recommend someone
  4. They can fill in multi-page form and save it to come back later
    • This will be a Sitecore form
  5. Once their application is final they can submit it for MVP review
    • No alert is needed, they will be reviewed once application process is closed
  6. Application is open from Nov 1 to Nov 30 8pm PST
    • Need to determine current server location for timestamp to open
    • Leverage personalization for page on sitecore to show the form
      • Otherwise, show application is currently closed
  7. Will be saved as Sitecore item
  8. 4 different forms and will be submitted together
    • Do these need to be 4 forms, or can the be broken out into steps

Background

  1. Notification for the invited applicants if they did not start filling in the form
  2. Notification for applicants started the form but did not submit it (last 7 days daily)
  3. Automatic backup of the application data
  4. Daily report of invitations/applications in progress/applications submitted

Background

  1. To be able to review individual applications by multiple reviewers (Corporate, Regional, MVP)
  2. To be able to assign security for regional, corporate and MVP reviewers by category, country or individually
  3. Save verdicts (Yes, No, Maybe) along with Comments from reviewers
  4. An interface where the summary of the verdicts can be seen and a final Verdict can be assigned
  5. Create reports by category, country, company, etc.

Background 1.