Comments

Lines that start with // (two slashes followed by a space) are stripped from the description before any other AFL processing happens. They never reach the rendered output and are invisible to visitors.

Comments are stage 1 in the processing order, which means they land before directives, URL extraction, and format detection.

Example

// reminder: confirm venue before publishing
// TODO: add the flyer image once design lands

Join us for the annual fundraiser at City Park.

#already:tag:fundraiser
#already:image:https://example.com/flyer.png

Visitors see only the third line and the directive-rendered tag/image card. The first two lines never make it past stage 1.

What comments are good for

• Internal notes for calendar editors. Reminders, draft language, references — things only your team should see.
• Disable a directive without deleting it. Comment out a #already: line while you debug, A/B test, or wait on assets:

  // #already:featured
  // #already:image:https://example.com/old-flyer.png

• Leave TODOs for yourself. // TODO: confirm with venue is a low-friction way to keep editorial state in the description without a separate tracker.

Rules

• Must start at the beginning of a line — leading whitespace is allowed; non-whitespace before // is not.
• A space is required after // — // note is a comment; //note is not.
• Mid-line // is not a comment — visit us // open daily renders as-is.
• URLs are never affected. https://example.com and protocol-relative //example.com are safe — the URL detector and the comment detector don't overlap.
• Lines are delimited by \n or \r\n. An HTML <br> tag does NOT begin a new comment-eligible line. Write comments on real newlines, not after <br> tags inserted by Google Calendar's rich-text editor.