Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Normal Modes Main checklist

Open
  • Is something wrong?
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
testing-qa, web-dev

Research direction

This issue is a master checklist for the Normal Modes simulation, covering design, implementation, publication, and QA. Start by reviewing the unchecked items and the referenced documents, including responsible_dev.md and the QA book. Done means the applicable checklist items are completed and the issue reflects the simulation's publication status.

Written by the indexing model from the issue text.

Description

project:sim-checklist

Normal Modes master checklist

Design

  • Sim folder and design doc created (Date: 02/12/2020)
  • Legacy sim docs/info gathered
  • Learning goals and standards identified (Date: 02/12/2020)
  • Design concept complete (Date: 02/12/2020)
  • Wireframes complete (Date: 03/04/2020)
  • Mockups complete (Date: 03/16/2020)
    • Mockups checked for colorblind and greyscale
  • Features for PhET-iO discussion
  • Interviews complete (Date: //)
    • Results reported to team
    • Notes pasted into design doc
    • Back-up of interviews
  • Lead designer "sign off" (Date: //)
    • Performance acceptable
    • Carefully review ?showPointerAreas
    • No new feature requests
  • Pre-publication items
    • Auxilary screenshots (up to 3 additional)
    • Screen-specific screenshots for metadata service (see naming convention)
    • Accessories (keywords, categories, description, learning goals, related sims, NSDL)
    • Accessibility features
    • Email announcement language
    • Teacher Guide created, uploaded, and added to sim design folder
    • Sim primer draft
    • LoL icons for each screen created and uploaded to Drive
    • LoL metadata for each screen (description, vocab words, questions for before/after sim use)
  • Post-publication items
    • Share new features, design challenges, and treats with group!
    • Review legacy gold star activities, copy over if appropriate
    • Email announcement language
    • Deliver to Legends of Learning
    • Sim primer (create issue, publish ideally within 1 month of live sim)
    • Hold postmortem if applicable (Date: //)

Implementation

  • Repository created (Date: 2/7/20)
    • Simulation added to responsible_dev.md
    • N/A Use grunt create-sim in perennial (see --help for arguments) to create the repository structure
    • Collaborators added (Developer team, QA team, designers, etc)
    • standard GitHub label set applied
    • repository added to perennial/data/active-repos
  • Development started (N/A contributed by 3rd-party)
  • Sim is "feature complete" (Date: 2/7/20 - accepted from 3rd party)
  • Code review completed (Date: 2/10/20)
  • Pre-publication items
    • Main screenshot (read this)
    • Verify credits with lead (Team, Contributors, QA, Graphic Arts, Sound Design, any Thanks)
  • Published (Date: //)

QA

  • Dev testing started (Date: //)
  • Dev testing completed (Date: //)
  • First RC published (Date: //)
  • RC testing completed (Date: //)
Dominant language
JavaScript
Stars
0
Forks
2
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from phetsims/normal-modes

All issues in phetsims/normal-modes

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.