# Why?
I wanted to make a website, where I can show off some of the stuff I make. So I decided to take it as a learning opportunity and use frameworks that I'm not familiar with.  
So I stumbled upon the usual suspects like Bootstrap and React, but I wasn't satisfied. Until I found Next.js, which sounded very interesting and not as complicated as React alone.  
As backend I decided to use Strapi.io, a headless CMS.

# How did it go?
It was quite a challenge. I never used node.js, had only very basic knowledge of Javascript, but Next.js made it a bit easier, by giving you a ready to go base you can build upon. Don't get me wrong, it was still a challenge, but seeing that even really big websites use it kept me motivated.

# Design
Tailwindcss is really nice. It makes styling the website a lot faster. It might not be that pretty; But you get the styling done, FAST.  
But what was my design concept? I didn't really have one. Most modern websites are so clean, sometimes boring: flat, nice harmonizing colours.  
But I build prototypes and experiment. So I chose neon yellow as my primary colour. And to make it pop, different then most websites, I use it in contrast with black.

# Backend
As mentioned, I use Strapi.io as my backend. It's a headless CMS, easy to set up and also easy to use. It provides a webinterface to add and edit content. As an example, this text is written in Markdown, which gets pulled from the CMS through an API from next.js, which rerenders it on the server on the next request.  
Everything runs in a Docker container, changes to the code get synchronized through a simple `git push` to my server, which then automatically rebuilds everything and serves it.

My own Portfolio Website. First time using Next.js, Tailwindcss and Strapi. It's responsive!

Portfolio Website

# Why?
The NOI Makerspace has an internal access management system (Based on [Fabman](http://fabman.io)), with little nfc boxes that unlock the machines.  
The machines are located in 4 different workshops, so if a user wants to enter one, they have to get the key from the employees. With a growing userbase, verifying if a user is allowed to use it and letting those enter, that are allowed to enter outside of business hours, becomes a problem. Additionally, counting the hours of use of a workshop, if the user only uses manual tools isn't possible.

Thats what the Keydispenser is designed to solve.

# What does it do?
The Keydispenser basically does what the name implies: dispense the requested workshop key, only if a user has the required permission, and saving it into the access management system.  
It also lets a user return a dispensed key, also saving it's return.

# Things I used
- Raspberry Pi
- Stepper motor
- Stepper Driver (with software current control)
- Hall sensor
- NFC module
- Neopixel LED's
- IR LED and detector
- Servo motor

A Keydispenser for the different workshops keys. A User logs in,  sees which keys he has the permissions to use and are available, presses a button, which causes the dispenser to drop the appropriate key and marks it as in use in the central database. After the user returns, he simply drops the key in and the dispenser marks it as returned.

Keydispenser

Changed the individual Lithium-Cells of a cheap E-Bike battery that couldn't hold a charge anymore. Added ~30% more capacity and a new BMS.

My Projects

Designed and Developed by Matthias Pfeifhofer

Made with Next.js and
tailwindcss, with in Italy

My Projects

Designed and Developed by Matthias Pfeifhofer

Made with Next.js and tailwindcss, with in Italy

Made with Next.js and
tailwindcss, with in Italy