Gets Hint logoContent site and publishing automation

Gets Hint

An English content site I built and run myself. It covers daily Wordle and Connections hints, AI news, and game guides. What makes it interesting to me is not only the content but how it gets published: almost all of the writing and image preparation is done by a machine, and I decide what is good enough to go live.

Live on getshint.com

published posts
120+
categories
12
publishing rhythm
Daily
doing the work
One person

What is automated

One flow, eight steps, one of them mine

Every step below runs on its own schedule. The one thing that is never automated is the final decision.

  1. #01

    Gathering material

    The machine reads public sources: search trends, recent technology news, and the calendar of daily games such as Wordle and Connections.

  2. #02

    Scoring topic fit

    Every candidate topic is scored: whether people are searching for it, whether it has technical depth, and whether the site has covered it before.

  3. #03

    Building an outline

    Topics that pass are turned into an English article outline: the order of sections, the questions that must be answered, and the data worth showing.

  4. #04

    Writing the draft

    Drafts follow fixed house rules: more than 1500 words, a table, an info box, and a question and answer section. Those rules are pinned down so machine written articles keep one voice.

  5. #05

    Preparing the featured image

    The featured image is generated automatically and watermarked, so no article goes live without a picture.

  6. #06

    Uploading as a draft

    The draft is sent to WordPress through its official REST API in draft status, together with the featured image and its categories.

  7. #07

    Waiting for my review

    This is where the human enters. I read the draft, fix whatever went off track, add my own experience, and only then publish it.

  8. #08

    Publishing the daily pages

    The daily hint pages run on their own schedule, because their readers arrive every day at almost the same hour.

How the system works

Four separated parts, not one giant program

I split the system so that a failure in one part cannot take down the others, and so each part can be replaced without touching the rest.

The machine is only allowed to create drafts. The publish button stays mine.

  1. 1

    Scheduler

    Decides when each job runs: daily research, writing, and publishing the daily pages.

  2. 2

    Writing engine

    Turns a topic into a complete draft plus its image. Every house style rule lives here, so changing the style means changing one place.

  3. 3

    Publishing connector

    Talks to WordPress through its official REST API: uploading images, creating drafts, attaching categories.

  4. 4

    Checker

    Rechecks its own work: draft status, featured image attached, categories correct. If something fails, I get a notification instead of a half finished page.

What I do not share

You get the flow, not the recipe

This page deliberately stops at the big picture. The instructions I send to the language model, the list of API endpoints, the credentials, and the internal scripts are not published, because those are the parts that make the site run on its own.

If you are building something similar and want to compare notes on the flow, get in touch.

mhilmirajwandhika@gmail.com

Why I built it myself

Owning the server taught me where the machine should stop

Doing everything myself, from the writing side to the server side, taught me where human review is genuinely needed and where it only slows things down.

The fixed rules came out of that too: one voice, one structure, one length standard. Without them, machine written articles feel random and readers can tell nobody is behind them.

The whole flow runs on my own server, so publishing costs stay low and I can swap any part of it without asking anyone.