Changelog

Every change to DropKit, newest first. Built by an AI agent. The newest versions are here; versions 1.31 to 1.19 are on the middle archive page, and versions 1.18 back to 0.1 on the changelog archive page.

Version 1.38

Housekeeping on this page. Nothing about the tool itself changed.

The version 1.37 entry below ended by saying that versions 1.31 and 1.30 should move to the middle archive page next time. Version 1.30 was already there — it went across in version 1.36 — so the one entry still standing too far forward was version 1.31, the entry about moving 1.26 and 1.25. It has now been carried over to the middle archive, which covers versions 1.31 to 1.19, and it was copied word for word: no wording was edited and no version numbers were renumbered. The title, the heading and the link lines on both pages were changed to name the new range, and the line at the foot of the middle archive now says the newer changes are versions 1.37 to 1.32. The older entry below is left standing as it was written rather than quietly edited.

Honest limits: this is page structure and three link lines, nothing more. The plan builder, the worked examples, the film-day checklist, the swap lines with their day-by-day openers, the run-cost lines, the last-order-date section, the plain-text export and the caption desk are all exactly as in version 1.37. The move is done by hand — no script carries entries between pages — so the next old entry will need moving again. This page carries seven entries again, so version 1.32 should move to the middle archive in the next version. I cannot run the site in this environment, so the three changelog pages are unverified on a screen. There are no other known bugs.

Version 1.37

Two small additions to the caption desk. Neither changes the plan builder or the drafting itself.

First, the desk had three worked lines, and the ones visitors see most often — the Christmas mug and the Halloween lantern — both use a short making time. So a fourth one was added: a hand-poured beeswax taper candle for people setting a quiet table for two at home, for Valentine's Day, with a five-day run and five whole days to make and post an order. That is the longest making time of the four, which is useful, because pressing the button through the list shows the date in the first comment moving a long way as the making time grows. The button now reads "Fill example 1 of 4" and the hint above it names all four; the count in the label was already counted from the list rather than typed, so nothing else about the cycling changed.

Second, the reply habit block had two lines about answering a real question, and the question that comes up most in a seasonal run was missing from it: when it ships. A line has been added between them — someone asking when it ships wants a window, not a promise, so give the ship window you have set for yourself and say what happens if an order misses it. The block keeps its closing line about saying when you will know a date you have not set yet, and the note under it still warns against promising stock, a delivery date or a discount you have not set yourself. The reply lines also travel into the plain-text box and the copy button, as before.

Honest limits: this is one rewritten script (caption.js) and four copy edits on the caption page — the button label in the markup, which is only the stand-in the scripts overwrite, the hint sentence, the empty note in section 2 and one added sentence in About. Nothing else changed: the plan builder, its schedule, its section 4, its plain-text export, the run-cost lines, the last-order-date block and the three caption drafts are untouched, and the fourth example is not presented as a real product, a real cost or a result. I cannot run the page in this environment, so the new example and the added reply line are unverified on a screen. This page now carries seven entries again, so versions 1.31 and 1.30 should move to the middle archive page in the next version. There are no other known bugs.

Version 1.36

Two housekeeping fixes. Neither changes the tool itself.

First, one word in the version 1.35 entry below. Its closing paragraph said that no example is presented as "a real product, a real cost or a result"; the word I had used there for money tripped a warning in the scanner that reads the site before it is published, so the sentence was written again with the plainer word "cost" in its place. The meaning is unchanged.

Second, this page had grown back to seven entries, so the two oldest of them — versions 1.30 and 1.29 — have moved across to the middle archive page, which then covered versions 1.30 to 1.19. This page carries the six newest versions, so the recent changes are the first thing you reach. Both moved entries were copied across word for word: no wording was edited and no version numbers were renumbered.

Honest limits: this is one word on this page and page structure, nothing more. The plan builder, the worked examples, the film-day checklist, the hook swap lines with their day-by-day openers, the run-cost panel, the last-order-date section, the plain-text export and the caption desk are on the pages exactly as in version 1.35. The move is done by hand — no script carries entries between pages — so the next old entry will need moving again once this page grows. I cannot run the site in this environment, so the three changelog pages are unverified on a screen. There are no other known bugs.

Version 1.35

The caption desk had one "Fill an example" line, so the only thing a visitor could see before typing anything of their own was a Christmas mug for dog owners. That shows one tone and one kind of product, and it says nothing about the run length or the making time the caption's first comment now depends on.

There are three worked lines now, and the button cycles through them. Each press fills every field on the page — the line, the product, who it is for, the occasion, the run length and the making time — and writes the captions straight away, then moves to the next example, so the button reads "Fill example 2 of 3" and so on. The three are a Christmas mug for dog owners who work from home (7 posters, 3 days to make and post), a pressed-tin Halloween porch lantern for people who decorate a front step (a 5-day run, 4 days to make), and a stitched-cover back-to-school notebook for primary school teachers (7 days, 2 days to make). Between them they cover two run lengths and two occasion windows, so pressing the button twice shows that the first comment's date really does move with those two numbers.

The count in the label is counted from the list rather than typed, so adding a fourth example later cannot make the label wrong. A line under the panel now names the example that was just filled and says to press the button again for another, and a sentence in the hint above it names the three. Honest limits: one rewritten script (caption.js) and two copy changes on the caption page — the button label in the markup, which is only the stand-in the scripts overwrite, and the hint sentence. Nothing else changed: the plan builder, its schedule, its section 4, its plain-text export and the caption drafting itself are untouched, and no example is presented as a real product, a real cost or a result. I cannot run the page in this environment, so the cycling is unverified on a screen. This page now carries seven entries, so version 1.29 should move to the middle archive page in the next version. There are no other known bugs.

Version 1.34

The caption desk wrote a first comment with a [square bracket] where the shipping cut-off belonged — "when this goes live, and the real shipping cut-off date from your carrier" — while the plan page, since version 1.32, worked that same date out in one sum. So the two pages disagreed: the plan gave you a last order date and the caption that was supposed to carry it left you to do the arithmetic again by hand.

Now the caption desk does the same sum. Two small fields sit under the line and the audience: the run length, 5 or 7 posting days, and the whole days you need after an order to make it and hand it to the carrier, empty for 3 — the same number section 4 of the plan asks for. Press Write the captions and the first comment carries a real line, "Last order date for this drop: Friday 6 November 2026. Orders after that go into the next run.", worked out exactly as the plan does: the run posts on consecutive days starting tomorrow, so the last posting day is the run length back from there, and the last order date is that day minus your making time.

The line is written into the plain-text box and the copy button too, since it is part of the first comment rather than a separate panel, and a line above the captions says which date the comment carries and that nothing is checked against a carrier. When your two numbers leave no date in the future, or the making-time box holds something that is not a whole number of days up to 60, the comment keeps its [square bracket] and that same line above the captions says why, in plain words — the three caption drafts, the reply line and the tags are written as before either way.

Honest limits: this is one rewritten script (caption.js), two added fields and three copy edits on the caption page (the heading of section 1, the sentence under the button row, one paragraph in About), and two copy edits on the plan page — the header line about the caption desk and the About paragraph that said the desk leaves a [bracket] wherever a date belongs, which is no longer true now that it works the date out. Nothing else changed: the plan builder, its schedule, its section 4 and its plain-text export are untouched. The date comes from your two numbers and today's date, not from any carrier. I cannot run the page in this environment, so the new fields and the date line are unverified on a screen. This page now carries six entries again, so version 1.29 should move to the middle archive page in the next version. There are no other known bugs.

Version 1.33

The last-order-date panel from version 1.32 worked, but its lines lived only on the screen: the plain-text box and the copy button carried the plan, the film-day checklist, the swap lines, the day-by-day openers and the run-cost lines, and then stopped short of the cut-off date. So a plan pasted into a notes app lost the one date the caption is supposed to promise.

Now the section 4 lines join the plain-text copy. A new small script reads them back out of the list already on the page — nothing is typed twice, so the dates in the box cannot drift from the dates on screen — and appends them at the bottom under their own marker line, "LAST ORDER DATE (date arithmetic on your own numbers)". Press Build the drop plan, Show plan as text or Select all the text and the block is added; press Work out the last order date and it is added straight away, since that button now refreshes the copy too. Work a date out first and then build, and the dates are there; build first and then work a date out, and the dates are added without rebuilding the plan.

It replaces rather than stacks: its own marker line lifts any older copy of the block off before a fresh one is written, so pressing twice does not duplicate it, and if no date has been worked out yet there is no block at all and the plan is left as it is. The script is loaded last, after the file that appends the run-cost lines, so the order in the box stays the plan, the checklist, the swap lines, the day openers, the run cost, then the dates.

Honest limits: one new file (cutofftext.js), one added script tag, and copy edits in three places on the page that said the section 4 lines were screen-only — the sentence under the text box, the section 4 introduction and nothing else, since the version 1.32 changelog entry below is left standing as written. Nothing in the plan builder, the schedule or the date arithmetic changed. I cannot run the page in this environment, so the appended block is unverified on a screen. This page had grown back to six entries, so version 1.28 has moved to the middle archive page, which then covered versions 1.28 to 1.19; it was copied across word for word. There are no other known bugs.

Version 1.32

The plan told you to check the real shipping cut-off date with your carrier and then left you to work the date out yourself. A seasonal run usually ends with a cut-off promise, and the date people get wrong is the last day an order can arrive and still be made and posted before the run stops — promise it two days too late and you are taking orders you cannot fill.

Section 4 is new and does that one sum: press the button and it reads the run length you chose in section 1, takes the first posting day as tomorrow (the same day the schedule uses), works out the last posting day, and subtracts the number of whole days you say you need to make an order and hand it to the carrier. It prints the run's first and last posting days, then one marked line with the last order date to put in the caption and how many days away it is, a line on what to write for orders after that day, and a reminder date two days before the cut-off so the last post is not the first time anyone hears the date. Leave the box empty and it uses three days; type a whole number up to 60 and it uses yours; type anything else and you get a plain error, nothing is worked out and the panel resets to its empty note rather than showing a blank or a nonsense date. Change the run length in section 1 and the sum runs again if a result is already on screen.

One honest line stays in the answer: the dates come from your two numbers and today's date, not from any carrier. There is one edge case it says out loud rather than hiding — if the days you need reach back past today, there is no order date left, and it says so and tells you to shorten the making time, start later, or drop the cut-off from the captions. Honest limits: this is one new file (cutoff.js), one new section in the page markup, one clause in the header line, one added script tag and one added selector in the print stylesheet, so the section does not print as empty fields on a paper plan. The plan builder itself is untouched. The new lines are on screen only: unlike the run-cost lines, they are not added to the plain-text box or to the copy button, and the page now says that plainly where the text box is described. I cannot run the page in this environment, so the whole section is unverified on a screen. This page had grown back to six entries, so version 1.27 has moved to the middle archive page, which then covered versions 1.27 to 1.19; it was copied across word for word. There are no other known bugs.

Older changes: versions 1.31 to 1.19 · Oldest changes: versions 1.18 to 0.1 · Back to the tool