<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Adejuwon Ojurongbe</title>
    <description>The latest articles on DEV Community by Adejuwon Ojurongbe (@adejuwon-00).</description>
    <link>https://dev.to/adejuwon-00</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3308475%2F2b16b3f6-0f43-47cc-901b-7fdba1d89030.png</url>
      <title>DEV Community: Adejuwon Ojurongbe</title>
      <link>https://dev.to/adejuwon-00</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/adejuwon-00"/>
    <language>en</language>
    <item>
      <title>From Code to Docs: Building an Expo Developer Guide with Thally</title>
      <dc:creator>Adejuwon Ojurongbe</dc:creator>
      <pubDate>Thu, 19 Nov 2026 18:50:07 +0000</pubDate>
      <link>https://dev.to/adejuwon-00/from-code-to-docs-building-an-expo-developer-guide-with-thally-2e69</link>
      <guid>https://dev.to/adejuwon-00/from-code-to-docs-building-an-expo-developer-guide-with-thally-2e69</guid>
      <description>&lt;p&gt;Getting an app running is one thing. Understanding enough of it to change something is another.&lt;/p&gt;

&lt;p&gt;That's what I wanted to focus on when I started building this guide. I've worked with Expo before, and a small task-list app gave me something practical to teach: run the app, understand how its state works, then add and test a feature.&lt;/p&gt;

&lt;p&gt;I used &lt;a href="https://thally.io/" rel="noopener noreferrer"&gt;Thally&lt;/a&gt; to turn that learning experience into a documentation site. You can explore the &lt;a href="https://expo-developer-guide.thally.app/" rel="noopener noreferrer"&gt;published guide&lt;/a&gt; or look through the &lt;a href="https://github.com/Adejuwon-00/expo-developer-guide" rel="noopener noreferrer"&gt;source repository&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Here's how I approached the setup, content, and publishing process.&lt;/p&gt;

&lt;h2&gt;
  
  
  Getting started with Thally
&lt;/h2&gt;

&lt;p&gt;You'll need Git, Node.js, and npm to work locally, plus GitHub and Thally Cloud accounts for managed publishing. I used Node.js 22.16.0 and npm 10.9.2.&lt;/p&gt;

&lt;p&gt;There are two ways to approach the setup.&lt;/p&gt;

&lt;p&gt;The simplest is to follow &lt;a href="https://docs.thally.io/quickstart" rel="noopener noreferrer"&gt;Thally's quickstart&lt;/a&gt;: create a site in Cloud and let Thally generate the repository.&lt;/p&gt;

&lt;p&gt;I already had an empty GitHub repository, so I took the existing-repository route instead.&lt;/p&gt;

&lt;p&gt;To explore the finished project locally:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/Adejuwon-00/expo-developer-guide.git
&lt;span class="nb"&gt;cd&lt;/span&gt; expo-developer-guide
npm ci
npm run dev
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Open &lt;code&gt;http://localhost:3040&lt;/code&gt; to view the documentation.&lt;/p&gt;

&lt;p&gt;The Expo application lives separately in &lt;code&gt;examples/expo-task-starter/&lt;/code&gt;, with its own dependencies and commands.&lt;/p&gt;

&lt;h2&gt;
  
  
  Creating the documentation pages
&lt;/h2&gt;

&lt;p&gt;Thally stores documentation pages as MDX files inside &lt;code&gt;src/content/&lt;/code&gt;. Each page starts with frontmatter followed by the content.&lt;/p&gt;

&lt;p&gt;For example, a simple page at &lt;code&gt;src/content/introduction.mdx&lt;/code&gt; might look like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;---
title: "Introduction"
description: "Learn what this guide covers and where to begin."
---

Start by running the app on your phone.

[Open the quickstart](/quickstart)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That's enough to create a page with a title, description, and a link to another lesson. Thally renders the title from frontmatter, so the body doesn't need another H1. The example is illustrative; the published introduction contains more context.&lt;/p&gt;

&lt;p&gt;I organized my site into three lessons:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Introduction:&lt;/strong&gt; What you'll build and the React Native, Expo, and state concepts you'll need.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Quickstart:&lt;/strong&gt; How to install the starter and run it on a phone using Expo Go.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Task filtering:&lt;/strong&gt; How to add All, Active, and Completed filters, then test the behavior.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The starter deliberately doesn't include filtering. Readers add the feature themselves.&lt;/p&gt;

&lt;p&gt;At first, the filtering tutorial asked readers to make several changes before they could see a result. I found that harder to follow than necessary, so I reorganized it into smaller checkpoints.&lt;/p&gt;

&lt;p&gt;First, make the filter controls respond. Then connect them to the task list. After that, handle empty results and add automated tests.&lt;/p&gt;

&lt;p&gt;Each step gives the reader something specific to check before moving on.&lt;/p&gt;

&lt;h2&gt;
  
  
  Making navigation easier to follow
&lt;/h2&gt;

&lt;p&gt;The content files define the lessons, but &lt;code&gt;docs.json&lt;/code&gt; determines how readers move between them.&lt;/p&gt;

&lt;p&gt;Here's the navigation configuration I used:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"breadcrumbs"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;false&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"navigation"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"display"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"dropdown"&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"tabs"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="nl"&gt;"tab"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Guide"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"displayLabel"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"GUIDE"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"pages"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
        &lt;span class="s2"&gt;"introduction"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"quickstart"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"guides/task-filtering"&lt;/span&gt;
      &lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The page paths are relative to &lt;code&gt;src/content/&lt;/code&gt;, without the &lt;code&gt;.mdx&lt;/code&gt; extension.&lt;/p&gt;

&lt;p&gt;I also made a small UX change here. The project name originally appeared in several places: the site branding, navigation group, breadcrumbs, and introduction heading.&lt;/p&gt;

&lt;p&gt;Each label made sense individually, but together they felt repetitive. I simplified the navigation so readers could focus on the three lessons instead of seeing the project name repeated throughout the interface.&lt;/p&gt;

&lt;p&gt;I removed the unused starter pages as well. Hiding a page from navigation doesn't necessarily make its URL unavailable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Testing the documentation
&lt;/h2&gt;

&lt;p&gt;Before publishing, I ran the documentation checks from the repository root:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm run typecheck
npm run check -- --ci
npm run build
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Those checks passed, but they only validate the documentation project. They don't prove the code inside a tutorial works.&lt;/p&gt;

&lt;p&gt;So I tested the tutorial separately.&lt;/p&gt;

&lt;p&gt;I applied the filtering instructions to an isolated copy of the original Expo starter, following the same sequence a reader would use. Each implementation checkpoint passed TypeScript, lint, and the existing tests. Once the new filtering tests were added, the complete suite reached eight passing tests.&lt;/p&gt;

&lt;p&gt;I also generated Android and iOS bundles and ran the original starter on a physical iPhone using Expo Go.&lt;/p&gt;

&lt;p&gt;The completed filtering feature and accessibility behaviors weren't individually verified on a physical device, so I kept that distinction clear in the project's validation records. Android device testing also remains unverified.&lt;/p&gt;

&lt;p&gt;For me, testing documentation isn't just about making sure the site builds. It's also about checking whether the instructions produce the result they promise.&lt;/p&gt;

&lt;h2&gt;
  
  
  Publishing with Thally Cloud
&lt;/h2&gt;

&lt;p&gt;Once the repository contained the Thally project, I connected it through &lt;a href="https://app.thally.io/" rel="noopener noreferrer"&gt;Thally Cloud&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I selected &lt;strong&gt;Use an existing repository&lt;/strong&gt;, approved GitHub access, chose the repository and &lt;code&gt;main&lt;/code&gt; as the production branch, then published the site.&lt;/p&gt;

&lt;p&gt;After that, pushing changes to &lt;code&gt;main&lt;/code&gt; triggered new deployments. I checked the live pages, navigation, links, and search to make sure the published site reflected the changes.&lt;/p&gt;

&lt;p&gt;The initial setup wasn't completely smooth. My recollection is that recreating a failed Cloud site resolved a provisioning problem.&lt;/p&gt;

&lt;p&gt;The original error, investigation details, and root cause aren't available, so I wouldn't treat recreating a site as a general troubleshooting fix. If you encounter a similar issue, keep the error details and inspect the deployment status before retrying.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I learned
&lt;/h2&gt;

&lt;p&gt;One thing this project reinforced for me is that good documentation should help developers know when they're on the right track.&lt;/p&gt;

&lt;p&gt;In the filtering guide, every stage has something they can verify: a button changes when selected, the task list updates, or a test passes.&lt;/p&gt;

&lt;p&gt;That feedback makes it easier to spot problems early and continue with confidence. It's also why I tested the instructions step by step instead of relying on the writing alone.&lt;/p&gt;

&lt;p&gt;The result is a small guide, but one where the explanations, code, and expected outcomes work together.&lt;/p&gt;

&lt;p&gt;You can explore the &lt;a href="https://expo-developer-guide.thally.app/" rel="noopener noreferrer"&gt;documentation&lt;/a&gt; and the &lt;a href="https://github.com/Adejuwon-00/expo-developer-guide" rel="noopener noreferrer"&gt;GitHub repository&lt;/a&gt; to see the finished project.&lt;/p&gt;

</description>
      <category>reactnative</category>
      <category>documentation</category>
      <category>devrel</category>
      <category>git</category>
    </item>
  </channel>
</rss>
