docs.kenp.io

Start with the troubleshooting page for your specific product on docs.kenp.io. If that doesn't solve the problem, support is handled on the Discord server — but the server is read-only by default, and posting privileges are granted when you purchase something from the shop. So the practical path is: check the docs first, then join Discord, and expect to post only if you're a shop customer.

Step 1: Find the troubleshooting page for your kit

The documentation site organizes everything by project in the left sidebar. Each product section has its own instructions and troubleshooting pages, so the page you need depends on which kit you own.

Two things are worth noting before you start reading:

• Version matters. Several kits have multiple assembly guides (for example, the AirPods PRO 1 kit has v3.1, v3, and v0.2+v0.1 guides). Use the guide that matches the version of the kit you actually received; following a different version's steps is a common source of confusion.
• Troubleshooting pages exist only for some products. The iPhone and AirPods USB-C protection cases list a Troubleshooting page, while other sections list compatibility and version information instead. If your product has no troubleshooting page, check the compatibility and versions pages first — your issue may be a known compatibility limitation rather than a fault.

Step 2: Check the source files and video guides

If a written step is ambiguous, the docs point to two additional resources:

• Project source files on GitHub — useful if you want to inspect the design itself or verify a part.
• Video assembly guides — listed for the AirPods MAX internal kit, AirPods PRO 1 kit, and AirPods 1 + 2. Video is often faster for judging orientation and fit of small parts.

Step 3: Ask on the Discord server

The documentation states that support is on the Discord server. The key condition: the server is read-only by default, and you get posting privileges when you purchase something from the shop. In practice:

1. Join the Discord server.
2. Read the existing channels — you can browse without posting.
3. If you need to ask a question, you'll need posting privileges, which come with a shop purchase.

If you haven't bought anything and only want to read, the server still works as a knowledge base. If you need a direct answer, plan on the purchase requirement rather than expecting open posting.

A quick decision guide

• Installation step looks wrong or a part doesn't fit: open your product's assembly guide at the correct version, then compare with the video guide if one exists.
• Something isn't working after assembly: check the troubleshooting page if your product has one; otherwise review the compatibility page to confirm your device and kit version are a supported pairing.
• Still stuck: join Discord, search the read-only channels first, then post if you have shop purchase privileges.

The site itself is a documentation hub rather than a support desk — it explicitly routes support to Discord and source files to GitHub, so don't expect a contact form or email channel on docs.kenp.io.

docs.kenp.io is the documentation hub for Ken Pillonel's USB-C modification projects. It covers four device families: iPhone USB-C protection cases, AirPods USB-C protection cases, AirPods MAX USB-C adapters, AirPods PRO 1 and AirPods 1 + 2 USB-C internal kits, and a Meta Quest 2 clear kit. Each project has its own section in the left sidebar with instructions, troubleshooting, compatibility notes, and version-specific assembly guides. Use the version selector within each project to match the guide to the hardware revision you actually have.

Projects and what each section contains

How to find the right guide

1. Open docs.kenp.io and locate your device family in the left sidebar.
2. Read the Compatibility and Versions pages first — these tell you which kit revision applies to your hardware.
3. Open the assembly guide whose version number matches your kit. Guides are versioned (for example, AirPods PRO 1 has v3.1, v3, and v0.2+v0.1), and steps differ between them.
4. If something goes wrong mid-build, check the Troubleshooting page in the same section before improvising.

Expected result: you land on a guide written for your exact kit revision rather than a generic teardown.

Source files, video, and support

• Source files: project source files are hosted on GitHub, linked from the documentation site.
• Video: several projects include a video assembly guide alongside the written steps — useful for steps that are hard to describe in text.
• Support: the Discord server is the support channel. It is read-only by default; posting privileges are granted when you purchase something from the shop. If you need to ask a question, plan for that access condition rather than assuming open posting.

Common sticking points

• Wrong guide version. The most frequent mismatch is following an older assembly guide with a newer kit. Always confirm the version number on the kit against the guide title.
• Confusing case vs. internal kits. iPhone and AirPods case projects are protection-case modifications; the AirPods PRO 1 and AirPods 1 + 2 projects are internal port kits. They are different procedures with different risk levels.
• Skipping compatibility pages. Compatibility pages exist because not every kit fits every hardware revision; check before ordering or disassembling.

The site itself is a documentation index, not a store — pricing and purchase details live on the linked shop, and the documentation does not state prices.

To find the correct guide, open the project page for your device in the left sidebar, then match your kit's version number to the guide version listed on that page. The site organizes instructions by project and by version, so the version match matters more than the device name alone. If you don't know your kit version, check the "Compatibility" and "Versions" entries on the project page before opening any assembly guide.

How the documentation is organized

The site's home page states that all projects appear in the left navigation bar, and that instructions are organized so you can find steps for your specific version. Each project page groups its content into a consistent set of sections:

• Instructions — the written assembly steps
• Troubleshooting — fixes for common problems
• Compatibility and Versions — which hardware and kit revisions the guides apply to
• Video and Assembly Guide — video walkthroughs plus versioned written guides

Because guides are split by version number (for example, an Assembly Guide v1.1 alongside v1), following the newest guide on a page is not automatically correct. The version label on the guide must match your kit.

Step-by-step: locate your guide

1. Identify your device and kit. The documented projects include iPhone USB-C Protection Cases, AirPods USB-C Protection Cases, AirPods MAX USB-C External Adapter, AirPods MAX USB-C Internal Kit, AirPods PRO 1 USB-C Internal Kit, AirPods 1 + 2, and Meta Quest 2 Clear Kit.
2. Open that project in the left sidebar. The sidebar is the index of all projects; the home page does not list every guide inline.
3. Read the Compatibility and Versions sections first. These tell you which kit revisions the page covers and how the guides are numbered.
4. Match your kit version to the guide version. For example, the AirPods MAX USB-C Internal Kit page lists Assembly Guide (v1.1) and Assembly Guide (v1); the AirPods PRO 1 USB-C Internal Kit page lists v3.1, v3, and v0.2+v0.1. Choose the guide whose version corresponds to your kit.
5. Open the written guide and, if useful, the video. Video guides sit alongside the written steps on the same project page, so you can watch the procedure and then follow the text.
6. Verify you're in the right place. The guide's version label and the compatibility notes should both agree with your kit before you start disassembly.

Version examples from the site

The pattern is consistent: where hardware changed, the site keeps older guide versions available rather than replacing them, so users with earlier kits can still follow the steps that match their parts.

Common pitfalls

• Starting from the home page instead of the sidebar. The home page is an introduction; the project list lives in the left bar.
• Assuming the highest version number applies to you. A v1.1 guide may describe revised parts that an original v1 kit does not have.
• Skipping the Compatibility section. It is the quickest way to confirm your device and kit are covered before you invest time in a guide.
• Ignoring the video when text is ambiguous. Where a step is hard to describe in words, the paired video on the same page often resolves it.

Where to get help and source material

Project source files are hosted on GitHub, and support runs through the project's Discord server. The site notes that the Discord server is read-only by default, and that posting privileges are granted when you purchase something from the shop. If your kit version isn't listed on a project page, that is the channel to ask in before proceeding with a guide that may not match your hardware.

Yes. According to the documentation site, project source files are hosted on GitHub, and the site links to them for reference. The documentation itself is organized by project and version, so you can match a guide to the specific kit you own before looking for its source files.

What the Documentation Site Provides

The site is a versioned instruction hub for hardware modification kits. Its home page states that all projects appear in the left navigation bar, and that project source files live on GitHub.

Documented Projects

The navigation lists these project areas:

• iPhone USB-C Protection Cases (instructions, troubleshooting)
• AirPods USB-C Protection Cases (instructions, troubleshooting)
• AirPods MAX USB-C External Adapter (instructions)
• USB-C Internal Kit (compatibility, versions, video, assembly guides v1.1 and v1)
• AirPods PRO 1 USB-C Internal Kit (compatibility, versions, video, assembly guides v3.1, v3, and v0.2+v0.1)
• AirPods 1 + 2 (compatibility, versions, video guide, repair and upgrade guide)
• Meta Quest 2 Clear Kit (assembly guide v1)

Conditions to Know Before You Start

Two access conditions are stated on the site:

1. Discord support is read-only by default. Posting privileges are granted when you purchase something from the shop. Reading existing support threads does not require that step.
2. Match the guide version to your kit. Several projects list multiple guide versions (for example, v3.1, v3, and v0.2+v0.1 for the AirPods PRO 1 kit). Using the wrong version is the most likely source of assembly confusion, so confirm your kit version on the compatibility page first.

The documentation site does not state prices or purchase terms; those belong to the shop, not the docs. Treat the docs as the reference layer and the shop as the purchasing layer.

Practical Path

1. Open the left navigation and select your device category.
2. Check the compatibility and versions page to identify your exact kit revision.
3. Open the matching assembly guide, and use the video guide if one is listed.
4. Follow the GitHub link for source files if you need the project files themselves.
5. If you get stuck, search the Discord server first; posting requires a shop purchase.

docs.kenp.io is a documentation site for do-it-yourself hardware modification projects, mainly USB-C conversion kits and cases for Apple devices. It hosts step-by-step instructions, troubleshooting pages, compatibility and version information, and assembly guides, organized by project in a left-hand navigation bar. It is a reference site for people building or installing these kits, not a shop or a general blog.

What the site covers

The homepage lists the projects currently documented, each with its own set of pages:

The pattern is consistent: for each project you can check whether your device version is supported, then open the assembly guide that matches the kit version you have.

How the site is organized

• Left navigation bar: every project is listed there, so you pick your device first and then drill into its pages.
• Version-specific guides: assembly guides are split by kit revision (for example v1.1 vs v1, or v3.1 vs v3 vs v0.2+v0.1). Use the guide that matches the hardware you actually received.
• Compatibility and versions pages: these sit alongside the guides for the internal kits, so you can confirm fit before starting a build.
• Video guides: several projects include a video alongside the written assembly guide.

Source files and support

• Source files: project source files are hosted on GitHub.
• Support: help is handled on the project's Discord server. The homepage notes the server is read-only by default, and posting privileges are granted when you purchase something from the associated shop.

That last point matters if you are stuck mid-build: reading the documentation is open to anyone, but asking questions in Discord depends on having a purchase on record. Plan to rely on the written guides and troubleshooting pages first, and treat the Discord as the escalation path for buyers.

When this site is the right resource

Use docs.kenp.io if you are installing or repairing one of the listed kits and need the guide for your specific version, a compatibility check, or troubleshooting steps. If you are looking for general information about USB-C modding, product purchasing, or community discussion outside these projects, this site is not built for that — it is a versioned instruction archive for a defined set of hardware projects.