AskFujo product overview graphic showing all available products on a dark background. Top section features the base AskFujo Starter Askbox with "1 AskBox, 40 fandom questions," displaying physical card previews with Boba-tan's character illustration and the tagline "Connect with your fandom friends...and yourself!" A callout arrow points to the digital Print-at-Home edition shown alongside with "Also available as digital Print-at-Home!" Bottom row shows both expansion packs side by side: Expansion #1 Browserland (blue) with "36 more questions about fanworks, ships & your online world!" featuring cards from CSS, HTML, and ARIA; and Expansion #2 Localhost (teal) with "36 more questions about fandom faves, life ...and hot takes!!" featuring cards from Terminal, GitHub, and Git. Both expansions include the tagline "for parties, cons, and...by yourself!" with the FujoGuide group character illustration.

48 HOURS LEFT before AskFujo preorders close!

You know that feeling when a question you're dying to answer lights up your Tumblr inbox? We put that in a box—a real, physical (OR digital) box. 40 fandom questions. For parties, cons, group calls, and...by yourself ✨

store.fujocoded.com/askfujo

AskFujo’s Stretch Goals: Expansion 2 themes reveal. Boba-tan is pointing at revealed GitHub and terminal, with black bands on their faces (and github's ass). Graphic says only 5 to new bundle.

✨ #AskFujo themes reveal! ✨

With just 5 ask card sets to go before stretch goal #2, let's reveal the next expansion's first TWO TOPICS:

♥︎ Personal & fandom life
♥︎ Your blorbos

Let's hit this goal for even closer (and snoopier 👀) bonds!! Get your ask cards 👇

store.fujocoded.com/askfujo

My thumb hurts from all the coding I did for the upcoming game, which is CLEARLY the right reason to buy your #AskFujo box + expansion and let me release it to you all 👀

I swear it's worth it!!!

store.fujocoded.com/askfujo

There's only one way forward

Box mockup for AskFujo, a game for fans and friends. Boba-tan holds a card between her index finger and thumb, winking knowingly at the viewer. A sample card (in an anonymous Tumblr ask style) reads 'bobatan-for-real-justice asked, Which old OTP would you still die for, and which one do you have mixed feelings about?' Underneath the mockup are several legends: ‘40 questions to share with your fujo friends!’, ‘Learn about each other's blorbdos and blorbdont's’, ‘Put the ‘ship’ in friendship!’, with the FujoCoded logo on the bottom. To the left of the logo is an envelope icon with the ‘new message’ badge replaced with the FujoCoded lemon. The blue background behind the mockup has a pattern of scattered ‘reblog’ and ‘like’ icons.

It's time to a-a-ask!

...with this year's 100% real, sorry-not-sorry April Fool's joke you can actually buy and cherish. Meet AskFujo: your very own "Tumblr" askbox with 40 questions for you, your friends...and your enemies.

Buy digital and physical cards in our store: store.fujocoded.com/askfujo

Newsletter will be out in the next couple days! Putting on the finishing touches and also doing some @fujoweb.dev work because a) IT'S THE PRIORITY!!! b) I need to do something even remotely technical or i'll wither 😭

One hour to register!! 👇 (and ask questions? I think? maybe that's longer, but why risk it 😎)

Reminder: today is your LAST DAY to register for @citruscon.bsky.social & send in your fandom, web AND code question for our Q&AdLib*

- Register: www.eventbrite.com/e/citrus-con-2026-tickets-1425812867669
- Send 'em in: citruscon.fillout.com/fujocoded-qna

*Used to be Q&AdLib(ish), but... yeah....

Reminder: ✨ Free Registration✨ for @citruscon.bsky.social closes tomorrow!

Fun fact: due to a clerical error, the original description of our Q&Ad-lib read as "Fuck code around", further cementing our brand.

Make sure to ask us questions about the web, writing code, or... fucking it? Form below👇👇

Check out—and cheer with us 🎉—our latest Issue 2 progress and lessons (learned and given) on good technical writing 💪🥳

i did work more on fujoguide issue 2, i swear, but the cat ate my progress—

(taking care of some pre-existing obligation and then it's time to go heads down 💪)

An excerpt from the book: This Issue's Scenario: Boba-tan Escapes Disaster! The unthinkable has happened: caught in the crossfire of one of Git and GitHub’s classic skirmishes, Boba-tan’s laptop is now irreparably broken—and just as she was putting the final touches on her NAND Cypher web shrine! (NAND Cypher, charming antagonist of fan-favorite series Binary Calls, and eminent Funblr Sexyman.) Luckily, not all is lost: thanks to Git and GitHub’s combined powers, a slightly-outdated version of Boba-tan’s shrine has been safely uploaded to the cloud. Now it’s time for Boba-tan to download this lost code to Git’s laptop (requisitioned on Terminal’s orders as she waits for her new one), and finish celebrating her favorite fictional character.

For a book like this, "deliver on your promise as soon as humanly possible" means time from first word to cloning the repo and seeing the fun web shrine on your computer must be as short as possible. Plus, if the reader hasn't used GitHub at all, the explanation has nothing to really "latch on" yet.

Putting the Hub in Git You may be wondering: if there are multiple copies of my code, how does Git know which one is the “main copy”? Simple but surprising answer: Git has no concept of a single “main copy” of your code! Since each remote repository maintains its own copy of your various commits (change checkpoints), and since commits can be independently copied—or not copied!—between remotes, it may be sometimes be impossible to point to “the most up-to-date copy”. Since changes can be synced independently, each remote might end up having a unique subset of the full code. In the (chaotically maddening) above situation, no remote knows about all changes! While this flexibility allows for cool possibilities in theory, in practice it can make keeping track of changes confusing. So, to make things easier on the brains of poor developers, Git remotes are often used in a “hub” configuration.

When using Git in a hub configuration, a single remote is designated as the one that holds the canonical (or “official”) version of the code. In this setup, remotes send their changes to the central “hub” once they’re ready to be shared. This way, while some remotes may be temporarily out of date, they can always catch up by asking the remote in charge for all the latest changes. In a hub configuration (the most commonly used), a remote is elected as the official copy of the code. All other copies will then send their own changes to it, or download changes made by others. These days, the central hub for most projects is a Git-based web service like GitHub. GitHub and similar platforms store the code of countless projects—small and large!—in the cloud, making it easy to access them, share them, and even collaborate on them. By keeping the main copy of your own repositories on services like these, you ensure your code remains safe and easily accessible—ready to edit from wherever you wish, and share with whoever you wish!

Re-reading it *definitely* confirmed my suspicions. I had already started moving some of the setup from the book into our free learning platform (learn.fujoweb.dev), but there was more to do. One big culprit was spending too much time upfront explaining remotes and the "hub" model.

In the previous issue, we learned that Version Control Systems (like Git) help you track the history of changes made to your files. But that’s not where the power of Git ends! Distributed Version Control Systems—like, once again, Git—allow you to keep a copy of your files on multiple computers, and to synchronize your changes across all the copies.

My favorite book on writing non-fiction (www.usefulbooks.com/learn/forgo-...) stresses to "deliver on your promise as soon as humanly possible", i.e. "drop the reader in the middle of the action and get yourself out of their way".

I knew from feedback/gut feel that this issue did a poor job at it.

Progress report 🚨✨

Slowed down but not deterred by professional hazards* impacting my writing workflow—that is, sitting on the floor surrounded by paper—the first chunk of FujoGuide TODOS are now TODONE! 🎉

Thoughts below 👇

*I sat on an uncomfortable chair too long so now my lower back hates me

Boost those links ☝️ take our genuine gratefulness you for your support 🙏 follow our progress 🏁 and let's make this a super prolific 2026, and a most excellent guide to GitHub and beyond ✨💖

Speaking of which, you can help @essentialrandom.bsky.social keep her focus on what only she SHE do (shitpost yaoi coding zines into existence) by helping @bobaboard.bsky.social fill 2 important positions:

- Volunteer Coordinator: bsky.app/profile/did:...
- Admin Assistant: bsky.app/profile/did:...

Most importantly, writing this in public reinforces our commitment to make "putting an excellent guide in the hands of our backers" our #1 priority for 2026.

We're SO thankful for everyone's patience as we set up our other initiatives (like learn@ learn.fujoweb.dev), now it's guide guide guide!! 🎓📚

I definitely felt like this was a lot more confusing than the first issue (which is funny because I've at least used github a little bit before but not git) but that's due to the subject matter and not the writing. i don't want to say github is more complicated than git, it just had more possibilities of messing up (but thankfully it seems most of those mess ups are accounted for in text) The writing was amazing and amusing. Overall a very entertaining read. The “take a breather” tasks were actually really nice and properly spaced out, giving readers good places to stop. It also meant it was easy to pick up again even after a few days (or in my case a week cause work was a terror between me starting this and finishing it).

Overall thoughts: Actually really enjoyed going through this! I feel like I understand what's going on with everything outlined, for the most part. I did end up having to read some things multiple times before I got what they were saying -- to a certain extent this might be unavoidable, given there's a lot of terminology and a lot of it sounds pretty similar when you're not familiar with it, but making sure everything is as direct and concise as possible would probably be a good idea.

Our first beta feedback 👇 was very positive, but there's still a lot to improve—not to mention, a couple extra chapters of advanced challenges to write (like how to fork and contribute to other projects, mayhap? 👀)!

Writing this in public means even more direct feedback...and it's fun 💪✨

Let's Rewrite FujoGuide! Issue 2, beta #2 GitHub perches on the top left corner, ready to pounce upon Git, who is very cute and asleep as a catboy loaf at the bottom right corner. A purple git logo is tiled in the background. A checklist, with all items unchecked so far: Review Beta #1 feedback Review Beta #1 flow Finalize new flow Reorganize intro chapter Plan extra chapters

[✨🚨 New Event Alert 🚨✨] Follow along as we liveblog our rewrite of FujoGuide Volume 0 Issue 2 and prepare it for its second beta!

For the next [as long as it takes], we'll be keeping you up-to-date on our progress, so you can keep us accountable for it 💖🙏

Tell your friends! Tell your servers!! Tell your.... blorbos?

You know what, fine—engagement bait time: would your blorbo make for a good Administrative Assistant? Would they join our sister organization, rallying fans together for a better web? Would they be our angle... or our devil?

After a long break, it is time (again): jump on in for a look back at one of our older plugins that loads AO3 data on an Astro website!

Let's update it and look at the README 👀 one of our community members generously contributed 💖

On streamplace 👇 & Twitch 👉 www.twitch.tv/essentialran... ]

[New Week! 📅 New Search! 🔍]

If you haven't checked out our call for a Volunteer Coordinator, or haven't ✨forwarded it✨ to your friends, discord servers, and secret blorbo thirstclubs 👀💦...

...find our form and apply here 👇✨

forms.gle/evUr3VXMV1ba...

What better Saturday afternoon than recycling our Friday m—I mean, helping the independent fandom web thrive?

Fill out—or share!—our Volunteer Coordinator application (forms.gle/evUr3VXMV1ba...) 👈 and help fujos, furries, and other fans build a better web for their communities.

BobaBoard Volunteer Application: Volunteers Coordinator Edition BobaBoard is looking for a Volunteer coordinator to help recruit, organize, and direct volunteers in pursuit of our mission to improve the experience of fandom communities on the web. We welcome appl...

Tired of the web falling apart while everyone's stuck in endless discourse? Been part of an org hitting growing-org pains and thought "I could fix her—if people *cared* and *listened*"?

BobaBoard is seeking a Volunteer Coordinator to rally fans and get 'em building 🧵👇

forms.gle/evUr3VXMV1ba...

BobaBoard Volunteer Application: Volunteers Coordinator Edition BobaBoard is looking for a Volunteer coordinator to help recruit, organize, and direct volunteers in pursuit of our mission to improve the experience of fandom communities on the web. We welcome appl...

tl;dr:

- 🔍 We need: a volunteer coordinator to build accountability systems to help fans actually ship
- 🧑‍🔬 Who has: experience herding folks toward shared goals—formally or through zines, forums, modding, burlesque, J-fashion tea parties, LARP, DIY shows...
- 🏁 Your task: forms.gle/evUr3VXMV1ba...

BobaBoard Volunteer Application: Volunteers Coordinator Edition BobaBoard is looking for a Volunteer coordinator to help recruit, organize, and direct volunteers in pursuit of our mission to improve the experience of fandom communities on the web. We welcome appl...

If you, like us, believe in the power of building our own future; if you, like us, believe it's possible—not easy—to come together to fix our communities; if you want to join a group of stubborn peers dedicated to helping fans *ship*, in more ways than one—

Heed our call:

forms.gle/evUr3VXMV1ba...

Help us spread the word and let's find @bobaboard.bsky.social a Volunteers Coordinator! 👀🙏

This is The Position We Need™ that unlocks everything else. Help our sibling org level up—like every org should—from "passionate chaos" to "passionate ORGANIZED chaos."

Feeling that post-Christmas cheer? Want "new year, new internet"?

Help us find the right person(s) to get fandom sitting down and working together to build a better fandom web! 🌐🦝🦝🦝🙏

Share our hiring call 👇 on your Discord, your group chats, everywhere 🙏

...and if YOU'RE that person, ✨apply!✨

Digital pack launch, Garage Sale 📦, and... so. many. articles. – FujoCoded Between stores and writing processes, betas and autoreleases, there's a lot of ground to cover. We hope you brought a shovel (or a Project Manager) ❄️🏂

Now for @fujoweb.dev. Speaking openly: Issue 2 hit snags (@essentialrandom.bsky.social's DoS-ed teaching energy + a collaborator stepping back), but we've regrouped and are making it our TOP 2026 PRIORITY.

Ongoing: draft tightening, spinning off FREE learn@ content, and recruiting a betas wrangler!