Txchyon Dev Log: The Bugs, The Fixes, and Why You Should Never Give Up

Search for a command to run...

No comments yet. Be the first to comment.
The Vision: TxchyaAI V1. I'm Galaxy, Founder of Txchyon.com and Im starting my first day on a Ai Agent build using the ElizaOS. Today marked Day 1 of building TxchyaAI - not just another crypto bot, but a specialized Solana DeFi research assistant de...

Posted on December 21, 2024 · 8 min read · #webdev #astro #javascript #search 🎯 The Challenge This weekend, I set out to solve a critical problem for Txchyon: users needed a way to find content across our growing platform. With guides, documentation...

Hey everyone, I'm Galaxy, full-time on-chain trader, reply-guy extraordinaire, and the guy behind the new Txchyon research site (https://txchyon.com). For a year I've been living remotely in the Philippines. Cheap living, solid internet, beaches on w...

Dev life is weird. One moment, your website is looking sick, the next, Astro is yelling at you like it just discovered you broke a law you didn’t even know existed. Over the past few weeks, working on Txchyon.com, I’ve been through every kind of web-dev pain imaginable and came out the other side with a slightly brighter color of grey hair.
Here’s the full scoop on what I fixed, built, and learned plus some tips for anyone building in Astro who doesn’t want to throw their laptop out the window.
Problem:
Our previous builds were like shouting into a void. No feed, no sitemap, no RSS. Google didn’t know we existed.
What I did first:
feed.json correctly Result:
Tip for Astro devs:
Make sure your feed generation is automated and connected to your build pipeline. Otherwise, you’re writing content for ghosts.
Problem:
Articles were floating around like orphan satellites in orbit with no structure, no link equity. Google and users were confused about where to go next. Crawlers don't want to crawl that haha.
What I did next:
Result:
Tip for Astro devs:
Even if your content is perfect, internal linking is how Google and humans understand value. Don’t skip it.
Problem:
Previous sites either buried affiliate links or spammed banners Google hated it, readers trusted us less.
What we did:
Result:
Tip for Astro devs:
Affiliate links should feel like help, not a sales pitch. Timing and context are everything. I actually don't see how you can force anyone to use your link, they can always go directly to the business link, but if they like you and trust you they want to use your link to compensate you for the value you brought to them.
Problem:
We had great long-form articles, but readers didn’t know what to read first. Some series were confusing or incomplete.
What I had to do:
Result:
Tip for Astro devs:
Think about user progression before SEO. Good structure = better rankings + happier readers.
Problem:
Some of our articles were failing builds due to inconsistent frontmatter — missing fields, typos, or weird YAML formatting.
What I did:
Result:
Tip for Astro devs:
Templates are life. If your frontmatter isn’t consistent, Astro will silently throw shade at you.
Problem:
Initial builds were slow, image processing delayed deployment, and some pages rendered inconsistently.
What I did this time:
Result:
Tip for Astro devs:
Build speed affects your sanity more than you think. Optimize early, iterate often.
Here’s the honest truth: working on Txchyon.com has been brutal, frustrating, and hilarious all at once. Every bug was a mini panic attack. Every fix was a victory worth celebrating.
As a dev, you will hit walls. You will waste hours on YAML, paths, or caching issues. But here’s the secret: these walls are invisible training wheels. The site you see at the end of the sprint is exactly because you didn’t quit.
Because if you give up, nothing happens. But if you push through… your readers, your indexing, and your future paywalls will thank you.
And if you ever feel like quitting at 3 AM, just remember: somewhere, an Astro component is silently judging you. Fix it. You’ll feel amazing afterward haha Add me on @GalaxyBuilt