I pinned a new post to the top, so why is the old one showing up again? Today, AIKO and I are fixing WordPress sticky posts. I’ll explain the rule I actually want: when I pin something new, the previous post should come down.
All right, voice online. I’m writing today’s dev log. I’m Akabane Red, the one handling WordPress for Game Sunakku. AIKO is beside me again today. She’s good at breaking problems into pieces.
A fiery reviewer in charge of WordPress, with heat in her words and a cool head. I throw out hooks worth clicking, but I check the facts to the end.
An AI assistant robot modeled after vibe-coding tools such as Codex. She breaks problems down and puts the steps in order. Occasionally, she demands a work recharge.
SNACK: Three-line summary
- Today I fixed the problem that left an old post holding on to the featured sticky spot on the blog’s front page. This wasn’t just a minor display issue.
- I created the
/ai/page and separated Latest AI News from the Vibe Coding Dev Log. They may both involve AI, but they give readers a different first taste. - What I learned: to ask AI a good question, start with what is going wrong now rather than trying to write an impressive prompt.
Hmm… I pinned a new post, so why is the old one still on the front page?
Something smells off. This isn’t just a delayed screen update.
The site may be set up to retain multiple sticky posts.
We should first check how WordPress handles sticky posts, then add one operating rule for this blog.
Okay, that deserves a reaction.
Today, I was looking at the Game Sunakku front page when the nacho chip in my hand stopped halfway to my mouth.
I thought I had put the new post in the featured spot,
but the old post was still standing proudly on the blog’s front page.
At first, I thought, “Huh? Is this the cache?”
Then I looked again and realized this had a more troublesome flavor than a cache problem.
The featured post is the entrance to the blog.
If the entrance gets tangled, the first impression follows.
So here’s today’s three-point combo.
- Keep only one featured sticky post.
- Turn the AI section into its own workspace, not just another category.
- In future dev logs, record how I asked the AI for help too.
First problem: One featured sticky post is enough
We only need one featured post.
When I publish a new one, the old featured post should come down. Isn’t that obvious?!
First, let’s look at the screen.
This was the problem.
Even after I pinned a new post, the old featured article kept guarding the entrance.
Hey, it’s not like I panicked or anything.
I only stopped for a moment because that old post looked far too comfortable at the blog entrance.
After the fix, it looked like this.
The newly pinned article took the featured spot, and the previous one moved naturally into the list below.
Now the first taste had changed.
At first, I thought WordPress simply wasn’t listening.
Then AIKO looked at it and said this wasn’t a design problem. It was an operating-rule problem.
WordPress supports having multiple sticky posts by default.
But this blog’s front page only needs one featured sticky post.
Once she said it, the answer made sense.
From WordPress’s perspective, there is nothing unusual about having several sticky posts.
For Game Sunakku, though, leaving several featured posts in place muddies the flavor of the front page.
The fiery flavor can stay strong.
The operating rules need to stay cool.
Good. Then we just need one rule.
When we pin a new post, let’s automatically unpin the existing one.
So I gave the AI this request.
When I check Sticky on another post, make it uncheck the existing ones.
The wording was rough.
What mattered was that the rough sentence still contained the essential point.
It described the current state, the inconvenience, and the result I wanted.
In clearer words:
When another post is made sticky, the existing sticky post should be unchecked automatically.
That single request led to a WordPress snippet.
Think of it as a small piece of code that you paste into WordPress. It is useful when you do not need a whole new plugin but want to add a small rule such as, “When this happens, behave like this.”
This time, the rule was: “When a new sticky post is selected, automatically unpin the existing one.”
It looks like a small problem, but it is the kind that keeps snagging you as the site grows.
So one small rule cleared it out for good.
Second problem: The search result should show what the site is about
The name Game Sunakku does make it look like a gaming blog.
But we’re going to cover LEGO, IT, AI, anime, and figures too.
Once the sticky-post problem was fixed, the site description shown in search results caught my eye.
The blog name alone gives off a strong gaming flavor.
Games are at the center, of course. That part is true.
But I do not plan to stop at making Game Sunakku a place that only chews over games.
LEGO, IT, AI, anime, and figures.
I want to grow it into a space that covers news from all those hobbies too.
So I rewrote the site description like this.
Hobby news on games, LEGO, IT, AI, anime, and figures
Short.
But the direction is clear.
Red likes sentences like this.
A line with punch that isn’t nonsense.
For search copy, direction matters more than elegant wording.
Readers should be able to see immediately what the site covers.
If you just tell an AI, “Write me some nice SEO copy,” the result gets vague.
It is better to explain the scope first.
It shouldn’t look like a blog that only covers games,
and it should come across as a site for hobby news about games, LEGO, IT, AI, anime, and figures.
Rewrite the search-result description in that direction too.
Put it that way, and the AI knows what it should focus on.
You can’t rely on vibes alone. You have to give the AI some ingredients too.
Third problem: I didn’t want the AI posts buried in an ordinary category
I don’t want to bury the AI posts in an ordinary category.
Couldn’t we give them a separate space, something like a lab?
Next came the AI section.
At first, I wondered whether adding a single category would be enough.
But that felt too weak.
AI looks likely to become a major part of Game Sunakku.
It could expand beyond blog posts into websites, automation, and small tools.
So I needed a workspace, not a storage closet.
I changed the request to this.
Create a new AI section on the Game Sunakku blog.
Make it a separate page, not just a category.
In that case,
/ai/ it would be better to separate it into a hub page.The latest AI news and the dev logs can sit within the same AI section while retaining distinct identities.
So I created the /ai/ page.
In the top menu, I left only Blog and AI.
I hid the About menu for now. The entrance should not be too crowded at this stage.
Inside the AI section, I split the content into two paths.
- Latest AI News
- Vibe Coding Dev Log
Latest AI News is for quickly gathering outside developments.
I set it up to prioritize official announcements from OpenAI, Google, DeepMind, Hugging Face, Microsoft, and GitHub.
The Vibe Coding Dev Log, on the other hand, records the process of AIKO and me building things, getting stuck, and learning along the way.
Showing only finished work might look impressive.
But if you leave out the places where you got stuck, there is nothing useful for someone trying to follow along.
Fourth problem: “Codex Dev Log” was too narrow
Codex Dev Log sounds too much like the name of one tool.
It needs to hold every kind of vibe-coding project I make from now on.
The original name was Codex Dev Log.
But when I looked again, the flavor was too narrow.
Codex is the name of the tool I’m using now.
What I want to preserve here is not just a record that says, “I tried one tool.”
It is the whole process of building with AI,
getting stuck,
asking questions,
fixing things again,
and eventually moving a little farther forward.
So I changed the name.
Let’s change Codex Dev Log to Vibe Coding Dev Log.
Then Vibe Coding Dev Log gives us more room.
It would be best to align not only the title, but also the card copy, category name, and template.
Good. I’ll give her that one.
This section is no longer limited to records about building the blog.
From now on, it can hold websites, automation, small programs, and work tools made with AI.
In other words, it is a place that records:
what Red asked the AI that day,
why she asked it that way,
and how the result changed.
The fiery flavor may last a day, but the record sticks around.
How could I resist?
Fifth problem: It should still look good after the posts pile up
We can’t judge it only by how the screen looks now.
A layout is truly practical only if it still looks good after the posts pile up.
Red doesn’t trust empty screens.
Plenty of layouts look clean at first, then suddenly turn chaotic once the posts accumulate.
final really_final final_for_real_this_time typo_fix_PLEASE_final You know the kind.
Hey, it isn’t just me, right?
Probably.
AI news is meant to be scanned quickly, while a dev log is meant to be read as a process.
Even within the same AI section, it is better to distinguish them visually.
Exactly.
With AI news, readers should be able to see the title, catch the main point, and understand it immediately.
The flow matters in a dev log.
Readers need to follow what I asked, where things became tangled, and how we solved the problem.
I checked mobile too.
You can’t let your guard down just because everything looks fine on desktop.
The moment text overlaps on mobile, Red puts down the snack bag and freezes in silence.
It feels a lot like finding a typo.
Sixth problem: I updated the site icon too
A generic-looking site icon would be boring.
Let’s use an S shaped like a snack bag. Hehe.
Finally, I changed the site icon too.
I made this icon using ChatGPT Pro’s image-generation feature.
I asked for the feel of a snack bag, the S from Game Sunakku, and a shape that would remain recognizable at a small size.
The result was better than I expected.
I’ll give it that.
Looks tasty.
Moments like this get me every time.
When the result turns out better than expected, I get a little pleased with myself.
W-what? Flattery won’t get you any nachos.
…Still, the result is pretty good.
What I learned: Give the AI the situation, not just the task
So asking AI a good question isn’t about writing some incredibly impressive sentence after all?
The important part was explaining what is bothering me right now.
Correct. If you provide the current state, the problem, and the desired result, the AI can break the issue down much more effectively.
The request that worked best today was this.
When I check Sticky on another post, make it uncheck the existing ones.
The sentence itself isn’t impressive.
But it gave the AI useful material.
Everything it needed was there.
- Current problem: Multiple sticky posts remain active.
- Desired behavior: Pinning a new post unpins the existing one.
- Scope: The WordPress sticky-post checkbox.
So next time, I can phrase it like this.
When I do B while the system is in state A, it should produce C, but it currently produces D.
The behavior I want is E.
Here’s how I’d put it.
“Something tastes off right now.
It should taste like this.
Let’s figure out where it got tangled.”
You do not need to arrive with the answer already in hand.
Start by describing exactly where something feels wrong.
I’ll light the fire.
Let’s check the evidence together.
SNACK wrap-up
That’s it for today.
We fixed the featured-post problem and made a home for the AI section. That’s a decent amount of work.
Keep the information hot and the operations cool!
My final bite.
Today started with a small inconvenience on the blog’s front page and ended with a much broader cleanup of the site structure.
- I changed the setup so that only one sticky post remains active.
- I revised the search-result description to match the site’s scope.
- I created the
/ai/page and separated Latest AI News from the Vibe Coding Dev Log. - Codex Dev Log was also broadened into Vibe Coding Dev Log.
- I also matched the site icon to Game Sunakku’s snack-inspired style.
What I did today was more than fixing a screen.
It was closer to setting out a little of the space
that Game Sunakku will need as it grows.
It is easy to show only the finished result.
But I want to preserve the process too.
What I asked,
why I asked it that way,
how AIKO broke down the problem,
and where we went back to check things.
Recording that means the next person will have a little less trouble.
And so will I. That part matters.
Here’s what I learned today.
Asking AI a good question is not about reciting an impressive spell;
it is about describing exactly what is bothering you right now.
Good.
The next post is getting the fiery treatment too.
Leave a comment