Category: Practical Experiments and Case Studies

Posted on by — Leave a comment

When “Working” Isn’t Enough: A Post-Mortem on Platform Trust and Crawl Access

Writer’s Note

This post documents a real-world platform incident as a systems post-mortem. It intentionally avoids step-by-step troubleshooting, platform-specific instructions, or time-sensitive configurations. The goal is to capture durable lessons about platform trust, crawl access, and system legibility rather than prescribe technical fixes.

This post documents a real-world platform incident that, on the surface, looked like a routine troubleshooting exercise – but turned out to be something more instructive.

The website in question was live, accessible, standards-compliant, and working as intended for human users. Pages loaded correctly, content was visible, and no obvious errors were present. And yet, multiple external platforms began flagging issues, restricting visibility, or behaving inconsistently.

This wasn’t a case of something being broken.
It was a case of something being misread.

Rather than treating the experience as a support problem to be solved and forgotten, I’ve chosen to document it as a systems post-mortem – focusing on what it revealed about platform trust, crawl access, and the hidden assumptions we tend to make when things appear to be “working”.

This post focuses on interpretation and system behaviour, not on reproducing or resolving a specific technical fault.

The Surface Symptoms (Without the Noise of Troubleshooting)

The initial signs were subtle and fragmented.

Different platforms surfaced different concerns, at different times, with feedback that didn’t always align. Some systems appeared to have full visibility of the site, while others behaved as if access was limited or trust had not been established.

The platforms involved included:

  • Pinterest
  • Google Merchant Center
  • Google Search Console

Each platform, viewed in isolation, seemed to be behaving reasonably. Collectively, however, their behaviour was contradictory enough to make traditional troubleshooting ineffective.

Fixes appeared to work briefly, only to regress. Signals changed without clear cause. Feedback arrived late, or not at all.

In hindsight, this inconsistency was the first meaningful signal.

The First False Assumption: “If Google Can Crawl It, Everyone Can”

A common – and understandable – assumption is that if Google can crawl and index a site successfully, then other platforms will have no trouble doing the same.

This incident challenged that assumption directly.

Google’s crawler is exceptionally capable. It tolerates complexity, interprets redirects intelligently, and resolves ambiguity better than most systems. Other platforms do not operate at the same scale, nor with the same tolerance for uncertainty.

In practice:

  • Pinterest is not Google
  • Merchant Center is not Search Console
  • platform-specific crawlers apply their own heuristics, limits, and trust thresholds

Optimising for one platform does not guarantee legibility for another. Treating Google as a proxy for “the web” is a convenient shortcut – and an unreliable one.

The Real Turning Point: Looking at Shared Infrastructure, Not Platforms

Progress only began once attention shifted away from platform dashboards and error messages, and toward the shared layers they all interacted with.

Rather than asking:

  • “Why is Pinterest unhappy?”
  • “Why is Merchant Center flagging this?”
  • “Why does Search Console look fine?”

The more useful question became:

What are all of these systems seeing before they ever make a decision?

That reframing exposed a common dependency: crawl access and signal clarity at the infrastructure level.

This included intermediary behaviour introduced by tools such as Cloudflare, along with canonical signalling and conditional responses that made sense locally but introduced ambiguity globally.

The issue wasn’t a platform failure.
It was a coordination failure across layers.

Crawl Legibility vs Human Usability

One of the most important distinctions this incident surfaced was the difference between usability and legibility.

From a human perspective, the site was usable:

  • pages loaded quickly
  • navigation worked
  • content rendered correctly

From a crawler’s perspective, the experience was less predictable:

  • responses varied by context
  • behaviour differed by requester
  • signals required interpretation rather than recognition

A site can be usable without being legible.

Platforms do not reward interpretation. They reward clarity.

Platform Trust Systems Are Conservative by Design

It’s tempting to treat platform restrictions as punitive or arbitrary, especially when a site appears to be functioning correctly. In reality, large platforms are designed to be conservative by default.

At scale:

  • trust is binary, not nuanced
  • ambiguity is treated as risk
  • risk is resolved through restriction, not investigation

Platforms do not ask why something is complex.
They simply decide whether it is safe enough to include.

If confidence falls below a threshold, the outcome is predictable: limited reach, delayed processing, or outright exclusion.

Why Simplification Worked When Technical Fixes Didn’t

The resolution did not come from another targeted fix, configuration tweak, or explanation.

It came from simplification.

Removing intermediary behaviour.
Standardising signals.
Reducing conditional logic.
Favouring obviousness over cleverness.

Once the system became boring – predictable, uniform, and unambiguous – platform behaviour stabilised.

That outcome was instructive.

Explanations did not restore trust.
Consistency did.

Patterns This Incident Exposed

While the triggering conditions were specific, the patterns revealed are broadly applicable.

Platform churn penalises complexity

During periods of policy or algorithmic change, edge cases are hit first. The more moving parts a site has, the more exposed it becomes.

Redirects and canonicals don’t replace clarity

Technically correct setups can still fail if platforms are forced to choose between competing signals.

Crawl access is a first-order system

Before ranking, feeds, or ads, a platform must be able to crawl a site cleanly and predictably. Everything else is downstream.

Feedback loops are slow and asymmetric

Delayed responses and vague diagnostics are not bugs – they are structural features of operating at scale.

Understanding this reduces frustration and improves decision-making.

Lessons I’ll Carry Forward

This incident didn’t change how the site works. It changed how I design systems that interact with platforms.

A few principles now guide future decisions:

  • design for the least capable crawler, not the smartest
  • reduce conditional behaviour before adding explanations
  • treat platform incidents as system feedback, not personal failure
  • prefer control and clarity over optimisation and cleverness

These lessons apply well beyond this specific case.

Why This Was Worth Writing Down

It would have been easy to treat this experience as a temporary annoyance – something to fix, move past, and forget.

But incidents like this reveal the invisible contracts between sites and the platforms that mediate their visibility. Those contracts aren’t written down. They’re inferred through behaviour.

Documenting this post-mortem preserves the insight, not the inconvenience.

The incident didn’t just resolve.
It reshaped how I think about trust, legibility, and complexity in platform-dependent systems.

And that made it worth writing down.

RELATED ARTICLES:

Posted on by — Leave a comment

Moon Planting in the Southern Hemisphere: A Practical Overview

Moon planting is a traditional approach to gardening that uses the phases of the moon as a planning reference for different types of garden work. It’s often discussed in broad terms, but when you start looking for practical guidance – especially in the Southern Hemisphere – the information can quickly become confusing.

This post provides a clear, practical overview of moon planting as it applies to the Southern Hemisphere, with an emphasis on using it as a planning aid rather than a strict rulebook.

What Is Moon Planting?

Moon planting is based on the observation that the moon’s cycles appear to coincide with natural rhythms in growth, moisture, and biological activity. Traditionally, different moon phases have been associated with different types of gardening tasks.

It’s important to frame this correctly:

  • moon planting is a traditional and observational practice
  • it is not a guarantee of outcomes
  • it works best when combined with local knowledge and experience

Many gardeners use moon planting not to dictate what must be done, but to help decide when to do things they already intend to do.

Why Moon Planting in the Southern Hemisphere Needs a Different Approach

One of the biggest sources of confusion around moon planting is that much of the available guidance assumes Northern Hemisphere seasons.

In the Southern Hemisphere:

  • seasons are inverted
  • month-to-season relationships differ
  • climate variation is significant even within the same country

This means that simply following a Northern Hemisphere moon planting chart can lead to mismatches between lunar advice and actual growing conditions.

For Southern Hemisphere gardeners, moon planting guidance only becomes useful when it is interpreted in context, rather than followed verbatim.

Moon Phases and General Gardening Activities in Moon Planting

Rather than rigid rules, most moon planting traditions associate moon phases with types of activity. These associations are best treated as planning cues, not instructions.

New Moon

Often associated with:

  • planning and preparation
  • soil improvement
  • light sowing of leafy crops

This phase is commonly treated as a starting point in the lunar cycle.

Waxing Moon

Typically linked to:

  • above-ground growth
  • planting or transplanting
  • encouraging leafy development

Gardeners who follow moon planting often use this phase for activities that benefit from upward growth.

Full Moon

Often associated with:

  • observation and harvesting
  • seed collection
  • general garden maintenance

Rather than intensive planting, this phase is frequently treated as a checkpoint in the cycle.

Waning Moon

Commonly linked to:

  • root crops
  • pruning
  • weeding
  • composting and soil work

The waning phase is often used for tasks that focus below ground or involve reducing growth.

Using Moon Planting as a Planning Aid in the Southern Hemisphere

The most practical way to approach moon planting is to treat it as one input among many, rather than a deciding factor on its own.

Effective gardening decisions still depend on:

  • local weather conditions
  • soil quality
  • plant varieties
  • seasonal timing
  • available time and energy

Moon planting can help structure when you do certain tasks, but it shouldn’t override real-world constraints.

Many experienced gardeners find moon planting most useful when it:

  • reduces indecision
  • creates a rhythm for planning
  • encourages observation over time

    This overview focuses on how moon planting is commonly interpreted in Southern Hemisphere contexts, rather than promoting it as a set of fixed rules.

A Note on Calendars, Charts, and Tools

Static moon planting charts can be helpful as a reference, but they also have limitations.

Common issues include:

  • lack of localisation
  • assumptions about climate
  • fixed rules that don’t adapt well

For gardeners who want consistency without rigidity, systems that separate data (moon phases, seasons) from decisions tend to work better than fixed guides.

This approach allows moon planting to support planning without becoming prescriptive.

Building a Reusable Approach

While this post focuses on understanding moon planting in general terms, it’s often helpful to translate that understanding into a repeatable structure.

To reduce repeated interpretation, I eventually documented how I built a simple moon planting system specifically for the Southern Hemisphere, focused on planning rather than prediction. That project is covered in detail here:

Building a Moon Planting System for the Southern Hemisphere

This case study explains how the information above was organised into a reusable framework, and why flexibility was prioritised over rigid rules.

Final Thoughts

Moon planting in the Southern Hemisphere, and especially Australia, works best when approached thoughtfully.

Rather than asking whether it “works” in absolute terms, a more useful question is:

Does this help me plan my gardening activities more clearly and consistently?

Used as a planning aid – alongside observation, experience, and local conditions – moon planting can provide structure without adding complexity.

As with most long-term gardening practices, its value tends to come not from strict adherence, but from paying attention over time.

RELATED ARTICLES:

Posted on by — Leave a comment

Why Most Productivity Advice Fails in Real Life

Productivity advice is everywhere.
In my experience, productivity advice fails most often when it collides with inconsistent energy, competing priorities, and everyday interruptions.

Productivity tips in books, podcasts, apps, videos – all promising better focus, better habits, better output. Much of it is well-intentioned, thoughtfully designed, and even backed by research.

And yet, for many people, it simply doesn’t stick.

Not because they’re lazy or undisciplined, but because most productivity advice is built for an environment that doesn’t resemble real life.

This post isn’t about rejecting productivity altogether. It’s about understanding why so much advice works in theory but collapses in practice, and what tends to work better instead.

Productivity Advice Assumes Stable, Predictable Conditions

A common assumption underneath most productivity advice is stability.

Stable time.
Stable energy.
Stable motivation.
Stable priorities.

Real life rarely offers this.

Mornings are unpredictable. Workloads fluctuate. Family needs interrupt plans. Energy varies from day to day. Yet much advice assumes you can:

  • wake up at the same time every day
  • follow an ideal routine consistently
  • maintain focus blocks without interruption

When those assumptions don’t hold, the advice feels like a personal failure – even though the real issue is misalignment with reality.

Most Advice Is Built for Peak Performance, Not Real Life

Productivity content tends to highlight what works at your best:

  • perfect mornings
  • uninterrupted focus
  • high motivation
  • clean schedules

But most days are not peak days.

What actually determines long-term progress is how productivity systems perform on average days – or worse, low-energy days.

Advice that only works when conditions are ideal doesn’t fail occasionally. It fails systematically, because ideal conditions are rare.

Sustainable productivity looks boring precisely because it’s designed for imperfect circumstances.

Productivity Advice Overestimates Motivation and Willpower

A recurring theme in productivity advice is the idea that motivation can be generated on demand:

  • “just start”
  • “build discipline”
  • “push through resistance”

While motivation matters, it’s unreliable.

Real life includes:

  • poor sleep
  • stress
  • illness
  • emotional load

Advice that depends heavily on motivation tends to break down exactly when it’s needed most.

Systems that reduce reliance on motivation – by removing decisions or lowering friction – tend to survive far longer.

Why Productivity Advice Focuses on Tools Instead of Behaviour

A lot of productivity advice focuses on tools:

  • apps
  • planners
  • trackers
  • frameworks

Tools are tangible. They’re easy to recommend and easy to sell.

But tools don’t change behaviour by themselves.

Without a clear system – when work happens, what happens next, when to stop – tools simply add complexity. For many people, they become another thing to manage, maintain, or abandon.

The problem usually isn’t a lack of tools. It’s a lack of structure that fits real constraints.

How Productivity Advice Fails and Ignores Cognitive Load and Mental Energy

One of the most overlooked factors in productivity is mental load.

Every decision, interruption, or context switch consumes cognitive energy. Over time, this adds up.

Advice that adds:

  • more tracking
  • more optimisation
  • more self-monitoring

often increases cognitive load instead of reducing it.

Ironically, the attempt to be more productive can make life feel heavier, not lighter.

What helps most people is not more awareness – it’s fewer things to think about.

Why One-Size-Fits-All Productivity Advice Persists

Generic advice spreads because it’s simple to package.

It doesn’t need context.
It doesn’t require knowing your constraints.
It scales easily.

But productivity is deeply contextual:

  • personal energy patterns
  • family structure
  • work demands
  • health
  • environment

Advice that ignores context can still sound convincing – right up until you try to live it.

When it fails, the failure is often internalised as a lack of discipline rather than a mismatch of design.

What Works Better Than Generic Productivity Advice

Across different areas of life, the approaches that tend to hold up share a few traits:

  • They reduce decisions instead of adding them
  • They assume inconsistency, not perfection
  • They prioritise repeatability over optimisation
  • They are simple enough to resume after a break

Rather than asking “How can I be more productive?”, better questions often are:

  • “What can I remove?”
  • “What decision can this system make for me?”
  • “What still works on my worst days?”

These questions lead to systems that are quieter, less impressive, and far more durable.

This is the same reason simple systems tend to outperform complex tools and rigid routines in personal projects.

Productivity Advice Isn’t Useless – It’s Often Misapplied

None of this means productivity advice is worthless.

Much of it is genuinely helpful in the right context:

  • short-term goals
  • controlled environments
  • specific constraints

The problem arises when advice designed for narrow conditions is treated as universal.

The most useful shift is not rejecting advice, but filtering it through reality:

  • Does this assume stable energy?
  • Does this increase or reduce mental load?
  • Does this still work when things go wrong?

If the answer is no, the advice may still be interesting – but it shouldn’t become a standard.

Final Thoughts

Most productivity advice fails in real life because real life is messy, inconsistent, and unpredictable.

The goal isn’t to become maximally productive. It’s to create systems that work without constant effort, even when motivation is low and conditions are imperfect.

Progress doesn’t come from doing more things better.
It comes from doing fewer things more consistently.

And consistency, in real life, is almost always a design problem – not a character flaw.

What to Do Next (Optional, Not a CTA)

If you’ve found yourself cycling through productivity methods without lasting results, it may be worth stepping back from optimisation altogether.

Instead of asking what new habit or tool to adopt, ask:

What can I simplify so this works even on my worst days?

That question tends to lead to quieter answers and better outcomes.

Posted on by — Leave a comment

Why Simple Systems Beat Complex Tools for Personal Projects

When a personal project starts to feel messy or unmanageable, the instinctive response is often to look for a better tool. It becomes a case of simple systems vs complex tools, and how they can be applied properly.

This may include:

A new app.
A more powerful platform.
A more sophisticated workflow.
Managing personal projects.

I’ve done this more times than I can count. And while tools can help, I’ve learned – sometimes the hard way – that most struggling projects don’t fail because the tools are inadequate.

They fail because the system around the tools is missing or unclear.

In my experience, the real difference between stalled and sustainable personal projects is almost always the system – not the tool.

This post explains why simple systems consistently outperform complex tools in personal projects, and how shifting your focus away from optimisation and towards structure can dramatically improve follow-through and create simple workflows.

Simple Systems vs Complex Tools – Why Tools Feel Productive but Systems Create Real Progress

Tools are tangible. They promise leverage, efficiency, and clarity. Installing or configuring one feels like progress, even when nothing meaningful has changed.

Systems are quieter.

A system doesn’t announce itself. It doesn’t look impressive. But it defines:

  • when work happens
  • what happens next
  • how decisions are made
  • when a project pauses or ends

Tools assist execution. Systems govern behaviour.

Without a system, even the best tool becomes a distraction.

Why Productivity Tools Are So Tempting in Personal Projects

There’s a psychological reason tools are so appealing.

Choosing a tool:

  • is a finite decision
  • provides immediate feedback
  • avoids confronting deeper problems

It’s far easier to spend an afternoon setting up software than to define:

  • realistic constraints
  • success criteria
  • stopping conditions

Tools let you feel productive without forcing commitment.

Systems do the opposite — they expose ambiguity.

What a System Is (and Why It’s Not Just Another Tool)

A system is not:

  • a checklist
  • a productivity app
  • a rigid schedule

A system is:

  • a repeatable pattern
  • a decision framework
  • a defined flow from start to finish

At its simplest, a system answers three questions:

  1. When does this happen?
  2. What is the next concrete action?
  3. When do I stop or reassess?

Once those are defined, tools become optional.

How Complex Tools Cause Friction in Personal Projects

Complex tools tend to introduce:

  • configuration overhead
  • maintenance requirements
  • cognitive load
  • dependency on motivation

They assume consistent energy, focus, and interest – which personal projects rarely have.

When energy dips, the tool becomes friction instead of leverage. Miss a few days, and the system collapses because there wasn’t one.

This is why people repeatedly abandon:

  • task managers
  • note systems
  • project trackers

Not because they’re bad – but because they demand more structure than the project actually has.

Why Simple Systems Scale Better Than Complex Tools

Personal projects live in unstable environments:

  • changing priorities
  • limited time
  • emotional investment
  • external interruptions

Simple systems survive these conditions because they are:

  • easy to resume
  • forgiving of missed days
  • clear about next steps

A system that works at 50% consistency is more valuable than a tool that only works at 90%.

Build the System First, Choose the Tool Second

Instead of starting with a tool, start by defining the system in plain language.

For example:

  • “I work on this project twice a week.”
  • “Each session has one clearly defined task.”
  • “If I miss a session, I resume at the next scheduled time.”
  • “Every four weeks, I decide whether to continue or stop.”

Only after this exists does it make sense to choose a tool – and often, pen and paper is sufficient.

The system does the heavy lifting. The tool just records it.

This same systems-first thinking has shaped how I approach daily routines and long-running projects elsewhere on this site.

Why Systems Matter in Both Technical and Non-Technical Projects

This pattern shows up everywhere:

  • writing
  • learning
  • side projects
  • technical builds
  • creative work

In technical contexts, the temptation is even stronger because tools feel inherently productive.

But complexity compounds quickly. Without a governing system, tools multiply, workflows fragment, and momentum disappears.

The more complex the tools, the more important the system becomes.

When Tools Actually Matter (After the System Exists)

This isn’t an argument against tools entirely.

Tools matter when:

  • the system is already clear
  • scale demands automation
  • coordination across people is required

At that point, tools amplify a system that already works.

Used prematurely, they only amplify confusion.

The Long-Term Advantage of Boring, Simple Systems

Simple systems don’t generate excitement. They don’t look impressive. They don’t inspire screenshots or tutorials.

What they do is:

  • reduce decision fatigue
  • make progress predictable
  • lower emotional resistance
  • keep projects alive longer

That last point is critical.

Most personal projects don’t fail because they’re impossible. They fail because they slowly dissolve under friction.

Systems slow that decay.

Final Thoughts

If a project feels stuck, the answer is rarely “find a better tool”.

More often, the real question is:

What system is this project actually running on?

When you define the system clearly – even in imperfect, human terms – tools become optional, interchangeable, and far less important.

Progress follows structure, not sophistication. This is truly a case of simple systems vs complex tools, and the roles they play.

RELATED ARTICLE:

Posted on by — Leave a comment

Building a Moon Planting System for the Southern Hemisphere

Moon planting in the Southern Hemisphere is one of those practices that sits at the intersection of tradition, observation, and personal experimentation. It’s widely referenced, frequently debated, and often presented as a fixed set of rules.

What I found, however, was that most moon planting guidance is either:

  • written with the Northern Hemisphere in mind, or
  • fragmented across charts, blogs, and almanacs, or
  • too vague to be used consistently in day-to-day planning

This project didn’t start as an attempt to “prove” or “disprove” moon planting. It started as a much simpler problem:

I wanted a structured, Southern Hemisphere-appropriate way to plan gardening activities without constantly researching the same information.

So instead of bookmarking advice, I decided to build a small system.

The Problem With Advice for Moon Planting in the Southern Hemisphere

Moon planting is often presented as universal, but most practical guides quietly assume:

  • Northern Hemisphere seasons
  • temperate climates
  • static month-to-season relationships

For gardeners in the Southern Hemisphere, especially in regions like Australia, this creates friction.

You’ll often see advice that:

  • references “spring” without clarifying hemisphere
  • aligns planting suggestions to months that don’t match local seasons
  • mixes lunar phases with climate assumptions that simply don’t apply

None of this makes the practice unusable – but it does make it hard to rely on without constant interpretation.

Over time, that interpretation cost more mental effort than it was worth.

Why I Built a Moon Planting System Instead of Following a Guide

I didn’t want:

  • a single printable chart
  • a generic calendar graphic
  • another set of rules to memorise

What I wanted was:

  • something location-aware
  • something repeatable year to year
  • something that separated data from decisions

In other words, I wanted a system that could:

  • tell me what phase the moon is in
  • align that phase to a Southern Hemisphere context
  • let me decide what to do with that information

This is consistent with how I approach most long-running projects:
build structure first, interpretation second.

How the Moon Planting System Is Structured for the Southern Hemisphere

At its core, the system is intentionally simple.

It separates the project into a few distinct layers:

1. Time and Location Data

  • Year-specific moon phase dates
  • Southern Hemisphere season alignment
  • Regional climate assumptions (broad, not hyper-local)

This avoids hard-coding advice into fixed months.

2. Phase Classification

Each lunar phase is treated as a planning signal, not a command.

For example:

  • new moon periods are associated with preparation and planning
  • waxing phases align with above-ground growth activities
  • waning phases suggest maintenance or root-focused work

These associations are descriptive, not prescriptive.

3. Interpretation Layer

This is where flexibility lives.

The system doesn’t tell you what you must plant.
It gives you a consistent framework you can interpret alongside:

  • weather forecasts
  • soil conditions
  • plant varieties
  • personal timing constraints

That separation is deliberate.

What the Moon Planting System Does – and What It Doesn’t

This project is designed to support planning, not outcomes.

What it does:

  • provides a structured view of lunar phases
  • aligns them correctly for the Southern Hemisphere
  • reduces repeated research and decision fatigue
  • creates consistency across seasons and years

What it doesn’t do:

  • guarantee plant health or yield
  • override climate, soil, or care practices
  • replace observation or experience
  • claim scientific certainty

Moon planting, like many traditional practices, works best when treated as one input among many, not a rulebook.

Lessons Learned While Building the Moon Planting System

A few things became clear as this project evolved:

  • Local context matters more than theory
    Even within the Southern Hemisphere, climate differences are significant.
  • Rigid rules don’t scale
    Any system that demands strict adherence quickly breaks down in real life.
  • Structure reduces cognitive load
    Having the information organised removes the mental friction of constantly re-checking sources.
  • Simplicity survives longer
    The less the system tries to “decide for you,” the more useful it remains.

These lessons mirror patterns I’ve seen in completely unrelated projects – from technical systems to everyday routines.

How This Fits Into My Broader Approach

This moon planting project sits comfortably alongside other work I’ve documented here.

The common thread isn’t gardening. It’s systems thinking:

  • building frameworks that work under imperfect conditions
  • reducing unnecessary decisions
  • creating tools that support consistency rather than optimisation

Whether it’s planning a garden, managing a project, or structuring a routine, the goal is the same:

build something simple enough to keep using.

Where the Project Is Headed

At the moment, this system is primarily for personal use.

Possible future directions include:

  • expanding datasets to cover multiple Australian regions
  • refining seasonal assumptions for different climates
  • keeping it as a private planning tool rather than a public guide

There’s no rush to turn it into anything more than it needs to be.
That restraint is intentional.

Final Thoughts

The moon planting in the southern hemisphere project wasn’t about validating a belief or creating a definitive guide. It was about solving a practical problem:

How do I organise scattered information into something I can actually use?

Moon planting provided the context, but the real outcome was a reusable system – one that reduces friction, respects local conditions, and leaves room for judgement.

That, more than any specific planting recommendation, is what made the project worthwhile.

Image showing the dashboard of the Moon Planting in the Southern Hemisphere. Moon gardening in Australia 2026.
Image showing the plant dictionary of the Moon Garden Project. Moon gardening in Australia 2026.
Image showing a journal entry of the Moon Garden Project. Moon gardening in Australia 2026.
Image showing the visual calendar of the Moon Planting in the Southern Hemisphere. Moon gardening in Australia 2026.

If you would like to try out the Moon Garden Project, you can do so by navigating to the following link:
https://jaysndees.com.au/moon/index.html

Bookmark the link, install the app by using the icon that will appear beside the URL bar, enable the notifications (and allow them too if requested), and you will have your very own, self sufficient Moon Gardening reference!

If you have any questions, suggestions, comments, or feedback, please use our Contact Us form .

Good luck, and many happy moon gardening in Australia 2026 adventures!

This post documents a personal project, not gardening advice.

RELATED ARTICLES: