🚌🔬 Magic School Bus Classroom

Science classroom collection with teacher and student dashboards, worksheet generators, lesson hubs, electricity activities, and printable lab resources.

🏷️ Maintained in qamotech/msb · 🌐 Public repository

✨ What is here

• 🎓 Teacher dashboard, student portal, roster, and grading interfaces.
• 📝 Worksheet, quiz, and science-packet generators.
• ⚡ Electricity activities, experiment pages, and video references.
• 📚 Multiple classroom variants plus Word lab guides and local visual assets.

🧭 Try the project

Open index.html, choose a science station, preview a worksheet, and try the print workflow before using materials with a class. Review the individual HTML pages for alternate lesson formats.

🚀 Local setup

git clone https://github.com/qamotech/msb.git
cd msb

Use a current browser. Serve the repository root to preserve relative assets and a stable browser origin:

python -m http.server 8000

Open http://localhost:8000/index.html. Keep related assets beside the entry file. No npm setup is declared in the inspected repository.

🗂️ Source map

• 📄 [CMSB Class 1 DOCS.txt](CMSB Class 1 DOCS.txt)
• 📄 MSB_Science_Packets_Complete.html
• 📄 [Magic School Bus Electricity Lab Guide - Styled.docx](Magic School Bus Electricity Lab Guide - Styled.docx)
• 📄 [Magic School Bus Electricity Lab Instructions.docx](Magic School Bus Electricity Lab Instructions.docx)
• 📄 [Magic School Bus Vids.txt](Magic School Bus Vids.txt)
• 📄 Magic_School_Bus_Electricity_Lab_Complete.docx
• 📄 accessibility.css
• 📄 audit_report.md
• 📄 electricity-overview.html
• 📄 favicon.svg
• 📄 frizz-files-lesson-hub.html
• 📄 frizz-worksheet-generator.html

⚙️ Configuration & data

External videos and media require their original providers. Classroom data and parent/teacher controls should not be assumed to provide secure multi-user accounts. Review attribution and rights before redistributing franchise-related assets.

Keep credentials, private exports, customer records, and personal information out of commits and screenshots. A local browser demo is not evidence of account security, reliable persistence, or connected external services. Preserve exports before changing storage keys or resetting an application.

🧪 Verification checklist

• 🔎 Confirm the entry file and asset paths above exist in your checkout.
• ▶️ Start the documented runtime and inspect browser or terminal errors.
• 🧭 Exercise the project-specific workflow described above using sample data.
• 📱 Check narrow and wide layouts when the project has a browser interface.
• 💾 Verify save/export and recovery behavior before trusting important work to it.
• 📝 Record the exact command, browser, operating system, and outcome of your checks.

This guide was prepared from repository files and manifests. It does not claim a fresh build, deployment, security audit, or full functional test of this project.

🤝 Contributions & useful reports

Keep changes focused and explain the user-visible result. Preserve existing assets and configuration unless a change requires updating them. Include reproduction steps, expected and actual behavior, and relevant screenshots with personal information removed. For UI work, include the viewport and browser; for runtime issues, include the command and error text.

🛠️ Maintenance priorities

• 📚 Keep this guide aligned with implemented behavior and current entry points.
• 🧪 Add or maintain checks for the core workflow before expanding features.
• ♿ Review labels, keyboard navigation, contrast, and responsive layout.
• 📦 Document external services, asset rights, and deployment prerequisites.

📜 Licensing & attribution

This documentation update does not grant a new software or asset license. Consult existing license files, source headers, package metadata, and original asset terms; resolve inconsistencies with the owner before redistribution. Third-party names and resources retain their own terms.