◆ HTML

Make an interactive calendar in HTML

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskBuild an interactive calendar for the upcoming company events. It needs to show event names,…+
Build an interactive calendar for the upcoming company events. It needs to show event names, dates, and times. The event list is in the project brief.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I roll out this interactive web calendar, make it more user-friendly for John in HR. He…+
Before I roll out this interactive web calendar, make it more user-friendly for John in HR. He needs to easily see event details when he clicks on a date and filter by department. Also, ensure it loads quickly on older browsers, as he's still using one.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI've got the basic calendar working, showing the dates, but I'm struggling with how to make…+
I've got the basic HTML calendar working, but I'm struggling with how to make event details appear on click without reloading the page.
I've got the basic calendar working, showing the dates, but I'm struggling with how to make event details appear on click without reloading the entire page. I'm worried about a clunky user experience for new hires trying to find information, and I can't seem to get the data to display smoothly. What's the best JavaScript approach to dynamically show event info when a date is selected?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternMy interactive calendars often have inconsistent behavior across different browsers, especially…+
My interactive HTML calendars often have inconsistent behavior across different browsers.
My interactive calendars often have inconsistent behavior across different browsers, especially for older versions, leading to complaints from users like Sarah in accounting. I spend too much time debugging these cross-browser issues after the fact. What habit should I change to build more robust and universally compatible calendar components from the beginning, so I'm not constantly fixing display glitches?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from HTML's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.