---
# System prepended metadata

title: Final presentation template

---

# Final presentation template
:::success
:wave: Hi, if you are here you are almost there to get ready for the final presentation.

This shouldn't take you more than 30 mins if you have been working in your project and doing the academy exercises.

- Consider this template the final deliverable of the academy
- Copy the template with your project name and remove supporting comments.
- Share the hackmd in our share-progress channel or via email to delftopenhardware@gmail.com. Make sure to make that hackmd public.
:::
length: 10 -15 minutes

## Read this guide before filling the template
- The main goal of the final presentation is to showcase the work that has been done during the academy at a project level, but also at a community level.
- The following template provides some fields for you to fill in to guide you and prepare for your presentation in a format that everybody is familiar with. 
- Your project description is important to feature your project in our open hardware academy website and help you out reaching new people that might be interested in your work.



# Template (Copy this hackmd)

## Project description

**Name of your project**:

**Name of your author**:

---

**Brief description of your project:**
:::success

Tips
- Provide an abstract of your project
- This can be in the form of a simple value proposition based on our [Framing open hardware projects](/AHVevvT-SbOY2jq4FYdieg) lesson.
- You can rely on sections of your documentation.

:::

---
**Current status of your project**:
:::success
Tips
- For projects that are in early phase we recommend to show a simple hackmd or markdown file in a github repository with a description of the project intent, some features and planned developments that allows to use it as a first step to ask for help and get feedback.
- For projects with a prototype being developed
- For more mature projects close to a first result that can be an alpha or beta design we recommend to show a release or a release plan.
:::

---
**References to your project documentation**:
:::success
Tips
- For projects that are in early phase we recommend to show a simple hackmd or markdown file in a github repository with a description of the project intent, some features and planned developments that allows to use it as a first step to ask for help and get feedback.
- For projects with a prototype being developed a repository or archive that is public is recommended. Showcase your work in progress documented in your development plan. (If you are using github you can showcase project documentation in the form of issues.)
- For more mature projects close to a first result that can be an alpha or beta design we recommend to show a release or a release plan (We recommend to use github for this)
:::
### Upload your project to github or similar platform to make it findable accessible reusable and interoperable
- You can generate an open know how manifest using this tool: https://okh.makernet.org/form
- Once you do it put it at the root of your project repository (Github or alternative)

### Share a link to the peer review you did before

### Share link to the peer review you have received

## Share general feedback to the academy
### What did you learn and/or experienced that was useful to progress in your project

### Do you find that the estimation of 4 hours per week is fair to be able to perform the exercises? 

### What things can we improve for next rounds