ertuncozbay.dev/index.html

180 lines
8.6 KiB
HTML

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Projects — Ertunç Özbay</title>
<meta name="description" content="Hardware and software projects by Ertunç Özbay: Multi-Functional RC Controller, RC and Autonomous Vehicle, and MIDI Breadboard Instrument.">
<link rel="icon" type="image/svg+xml" href="../assets/images/favicon.svg">
<link rel="stylesheet" href="../assets/css/style.css">
</head>
<body>
<a class="skip-link" href="#main-content">Skip to main content</a>
<header class="site-header">
<div class="container header-inner">
<a class="site-brand" href="../index.html">
<span class="brand-mark" aria-hidden="true">EÖ</span>
<span>
Ertunç Özbay
<span class="brand-subtitle">workshop // notebook // lab</span>
</span>
</a>
<button class="nav-toggle" type="button" data-nav-toggle aria-expanded="false" aria-controls="primary-navigation">
<span aria-hidden="true">☰</span>
<span data-nav-label>Menu</span>
</button>
<nav id="primary-navigation" class="site-nav" data-site-nav aria-label="Main navigation">
<ul class="nav-list">
<li><a class="nav-link" href="../index.html">Home</a></li>
<li><a class="nav-link" href="../about.html">About</a></li>
<li><a class="nav-link" href="../projects/index.html" aria-current="page">Projects</a></li>
<li><a class="nav-link" href="../blog/index.html">Blog</a></li>
<li><a class="nav-link" href="../lab.html">Lab</a></li>
<li><a class="nav-link" href="../contact.html">Contact</a></li>
</ul>
</nav>
</div>
</header>
<main id="main-content">
<div class="container">
<section class="workshop-hero" aria-labelledby="projects-heading">
<span class="workshop-eyebrow">PROJECT SHOWCASE // REAL BUILDS</span>
<h1 id="projects-heading">Projects on My Bench</h1>
<p class="hero-lead">
Here are the three real projects I am currently building and documenting. Because I value honesty in technical documentation, each project page lists only confirmed components and real progress—never invented specifications.
</p>
</section>
<section class="section-block" aria-labelledby="project-list-heading">
<div class="section-header">
<div>
<span class="section-label">Active Hardware &amp; Software Builds</span>
<h2 id="project-list-heading">Current Projects (3)</h2>
</div>
</div>
<div class="card-grid">
<!-- Project 1 -->
<article class="card">
<div class="card-top">
<div class="card-meta">
<span class="badge badge-progress">Status: In progress</span>
<span>Project 01</span>
</div>
<h3><a href="multi-functional-controller.html">Multi-Functional RC Controller</a></h3>
<p>
An ongoing RC controller project focused on remote control hardware and hardware-software integration.
</p>
<p><strong>Confirmed technologies &amp; focus:</strong></p>
<ul class="tag-list" aria-label="Confirmed technologies for Multi-Functional RC Controller">
<li><span class="tag">RC Control</span></li>
<li><span class="tag">Hardware-Software Integration</span></li>
<li><span class="tag">Open-Source Repo</span></li>
</ul>
<div class="project-notes">
<p><strong>What I am currently learning:</strong> Structuring an RC controller system so physical inputs and control software stay reliable and modular.</p>
<p><strong>Next step:</strong> Documenting confirmed hardware choices, wiring notes, and iteration logs as testing progresses.</p>
</div>
</div>
<div class="card-actions">
<a class="btn btn-primary" href="multi-functional-controller.html">Read Project Page</a>
<a class="btn btn-secondary" href="https://github.com/ertunc-ozbay/multi-functional-controller" rel="noopener noreferrer">GitHub Repository</a>
</div>
</article>
<!-- Project 2 -->
<article class="card">
<div class="card-top">
<div class="card-meta">
<span class="badge badge-progress">Status: In progress</span>
<span>Project 02</span>
</div>
<h3><a href="rc-autonomous-vehicle.html">RC and Autonomous Vehicle</a></h3>
<p>
An ongoing project exploring RC control and autonomous vehicle behavior. This project is part of my effort to understand systems across electronics, control logic, and software.
</p>
<p><strong>Confirmed technologies &amp; focus:</strong></p>
<ul class="tag-list" aria-label="Confirmed focus areas for RC and Autonomous Vehicle">
<li><span class="tag">RC Control</span></li>
<li><span class="tag">Autonomous Behavior Exploration</span></li>
<li><span class="tag">Electronics</span></li>
<li><span class="tag">Control Logic &amp; Software</span></li>
</ul>
<div class="project-notes">
<p><strong>What I am currently learning:</strong> How manual RC control and autonomous decision logic interact with physical vehicle electronics.</p>
<p><strong>Next step:</strong> Confirming and testing the hardware platform before publishing specific sensor or controller details.</p>
</div>
</div>
<div class="card-actions">
<a class="btn btn-primary" href="rc-autonomous-vehicle.html">Read Project Page</a>
</div>
</article>
<!-- Project 3 -->
<article class="card">
<div class="card-top">
<div class="card-meta">
<span class="badge badge-experimental">Status: In progress / Experimental</span>
<span>Project 03</span>
</div>
<h3><a href="midi-breadboard-instrument.html">MIDI Breadboard Instrument</a></h3>
<p>
A breadboard-based project that plays MIDI melodies by converting MIDI data into C code for the device. The hardware currently includes two active buzzers, one passive buzzer, a rotary encoder, a 1.3-inch AMOLED display, two buttons, and two LEDs.
</p>
<p><strong>Confirmed components &amp; tools:</strong></p>
<ul class="tag-list" aria-label="Confirmed components for MIDI Breadboard Instrument">
<li><span class="tag">MIDI-to-C Conversion Script</span></li>
<li><span class="tag">C Code Output</span></li>
<li><span class="tag">2x Active Buzzers</span></li>
<li><span class="tag">1x Passive Buzzer</span></li>
<li><span class="tag">1x Rotary Encoder</span></li>
<li><span class="tag">1.3" AMOLED Screen</span></li>
<li><span class="tag">2x Buttons</span></li>
<li><span class="tag">2x LEDs</span></li>
</ul>
<div class="project-notes">
<p><strong>What I am currently learning:</strong> Translating musical MIDI data into C code arrays and coordinating buzzers, a display, and physical user inputs on a breadboard.</p>
<p><strong>Next step:</strong> Recording build notes, refining the MIDI-to-C conversion workflow, and documenting the breadboard setup.</p>
</div>
</div>
<div class="card-actions">
<a class="btn btn-primary" href="midi-breadboard-instrument.html">Read Project Page</a>
</div>
</article>
</div>
</section>
</div>
</main>
<footer class="site-footer">
<div class="container footer-inner">
<div>
<strong>Ertunç Özbay</strong> — Personal workshop, project lab, and learning notebook.
</div>
<ul class="footer-links" aria-label="Footer links">
<li><a href="../projects/index.html">Projects</a></li>
<li><a href="../blog/index.html">Blog</a></li>
<li><a href="../lab.html">Lab</a></li>
<li><a href="../contact.html">Contact</a></li>
<li><a href="https://github.com/ertunc-ozbay" rel="noopener noreferrer">GitHub</a></li>
</ul>
</div>
</footer>
<script src="../assets/js/main.js"></script>
</body>
</html>