Development-entry template¶
Copy the Markdown below into docs/blog/posts/YYYY-MM-DD-short-title.md. Replace every instruction in brackets before publishing.
---
date: YYYY-MM-DD
authors:
- elena-team
categories:
- [Mother, Nolena, Melissa, Power, Motors, Sensors, Display, Software, Test]
draft: true
---
# [Title]
[One-paragraph summary for the development-log index.]
<!-- more -->
## Title and date
**[Descriptive title — Month Day, Year]**
## Development stage
[Planning, prototype, integration, testing, troubleshooting, or complete.]
## Goal
[What should this work accomplish? State a measurable result when possible.]
## Components used
- [Component and model]
- [Component and model]
## What changed
[Describe physical, electrical, or architectural changes.]
## Wiring or schematic
[Document pin numbers, wire colors, voltage levels, and shared grounds.]
## Software changes
[List affected files, commands, protocols, configuration, and firmware changes.]
## Test results
| Test | Expected | Observed | Result |
| --- | --- | --- | --- |
| [Test] | [Expected value] | [Measured value] | Pass/Fail |
## Problems encountered
[Record symptoms, error messages, measurements, and conditions.]
## Solution
[Explain the correction and why it worked.]
## Photographs/video
[Add a video link and a short explanation of what it demonstrates.]
## Next steps
1. [Next action]
2. [Next test]
3. [Remaining question]
Tip
Keep measurements and exact error messages. A failed experiment documented clearly is still valuable progress.