Creation of Educational Materials on Arduino Programming

Example of how it should be - link here.

Project goal: Develop a series of high-quality and understandable educational materials (texts/lessons) on programming and working with Arduino boards. 

Final result: Ready-to-publish/use texts/lessons that meet all the requirements of this technical specification.

Content requirements

 Format and structure of materials:

• Type of content: [step-by-step lessons, practical guides, component reviews, etc.]

• Structure of each material (example):

  • Title.

  • Brief introduction (what the material is about, what the reader will learn).

  • Necessary components and software (with links, if possible).

  • Theoretical part (clear and accessible).

  • Practical part:

    • Connection diagram (clear, possibly created in Fritzing or similar software).

    • Program code (sketch) with detailed comments in Ukrainian.

    • Explanation of how the code works.

  • Possible problems and their solutions.

  • Conclusion and next steps.

• Volume of one material: [For example: from X to Y words/characters, or approximate time to study the lesson].

Style and language:

• Language: Ukrainian.

Visual materials:

• Connection diagrams: [For example: should be clear, created in Fritzing].

• Photographs/Screenshots: [For example: real photos of assembled circuits, screenshots of Arduino IDE software.].

• Illustrations: [If specific illustrations are needed].

Code (sketches):

• Code must be functional and tested on [specify specific Arduino boards, if important, e.g., Arduino Uno, Nano, Mega].

• Code must be well-commented in Ukrainian.

• Adherence to the code writing style (Code Style Guide), if available.

Scope of work and deadlines

• Total number of materials: [For example: 10 lessons, 5 articles].

• Submission frequency: [For example: 1 lesson per week, or the entire volume by a certain date].

• Overall project deadline: by [specify date].

• Possibility of phased submission and review.

Requirements for the performer

• Deep knowledge of the Arduino platform (hardware and software parts).

• Experience in writing technical texts, articles, or lessons.

• Ability to explain complex things in simple language.

• Literacy, attention to detail.

• Preferably: experience working with [specify specific sensors, modules, if they are key].

• Portfolio with examples of similar work.

Copyright

• All materials created within this technical specification (texts, code, images) become the full property of the Customer after payment.

• The performer does not have the right to publish or transfer these materials to third parties.