Choosing a technical foundation is not a matter of taste. In Douala, the constraint that decides is the network: a page that takes eight seconds to appear on an average connection will not be read, whatever the quality of its content.
What static rendering changes
A site rendered at build time sends the browser a file that is already written. There is no database to query, no server to wake up, no computation to run while the user waits. On a fast connection the difference is measured in tenths of a second. On a slow, unstable connection it is measured in lost visitors.
A cost that does not run away
A static site is hosted for a fixed price, often nothing until traffic gets significant. There is no bill that doubles because a post did well, no server to resize in a hurry. For an SME, that predictability is often worth more than raw performance.
What Gatsby adds
Gatsby adds a unified data layer on top of React: content, whether it comes from Markdown files, a CMS or an API, reaches the components through the same door. The day the client moves from a folder of files to a CMS, only one layer changes — not the pages.
A foundation is chosen on what it will cost in three years, not on what it saves in the first week.
When we do not use it
Gatsby is not the answer to everything. As soon as an application becomes mostly dynamic — a dashboard, a client portal with data specific to each user — we move to a different foundation. Static rendering shines on content sites; it becomes an obstacle on applications.
What it means for you
Concretely: a site that loads fast everywhere, a stable hosting bill, and a team that updates its own content without calling us.