{{define "content"}}
{{/* Adding content, on its own page (2026-09-29, Paul: "remove the Add
     forms from the index … that should be a separate Add content form").
     The form, the drop zone, the upload tray and the outcome message moved
     here unchanged; POST /documents still receives them, and now redirects
     back HERE with its outcome rather than to the index. The index keeps
     search and the document list, and links here. */}}
<nav rst-breadcrumb><a href="/">← Back to search</a></nav>
<section>
  <h1>Add content</h1>
  <form method="post" action="/documents" enctype="multipart/form-data" rst-stack>
    <label for="title">Title <span rst-muted rst-hint>{{.Drop.TitleHint}}</span></label>
    <input type="text" id="title" name="title">
    <label for="body">Paste text</label>
    <textarea id="body" name="body" rows="8" placeholder="Paste a document, notes, minutes…"></textarea>
    <label for="file">{{.Drop.FileLabel}}</label>
    {{/* The drop zone WRAPS the file input, it does not replace it. With
         no script the div is an unstyled box, the hint and the note stay
         hidden, and this is the same form it was: choose files, press
         Store it. static/drop.js adds rst-dropzone="ready", which is what
         the styling keys off — so a page whose script did not load never
         draws a drop target that cannot take a drop.

         What a DROP does has changed: it no longer fills this input and
         wait for Store it. Each dropped file is posted on its own, in
         the background, to this form's own action, and the tray below
         the form says how each one went. Choosing files here and
         pressing Store it is untouched and still posts the whole form.

         The data attributes are the handler's own limits and the
         handler's own words (see dropZone in handlers.go). The browser
         reads them from here rather than carrying a second copy, so it
         cannot come to refuse what the server would accept.

         The input is `multiple`, and that is a plain HTML affordance
         with no script behind it: createDocument iterates every part
         named "file" and stores one document each, so a scriptless
         chooser that hands it five files gets five documents. It was
         deliberately single-file while the handler read only the first
         part — four of five would have vanished without a word. */}}
    {{with .Drop}}
    <div rst-dropzone
         data-max-bytes="{{.MaxBytes}}"
         data-max-total-bytes="{{.MaxTotalBytes}}"
         data-max-files="{{.MaxFiles}}"
         data-sniff-bytes="{{.SniffBytes}}"
         data-max-in-flight="{{.MaxInFlight}}"
         data-refresh-header="{{.RefreshHeader}}"
         data-msg-toomany="{{.TooManyFiles}}"
         data-msg-toototal="{{.TooMuchAtOnce}}"
         data-msg-folder="{{.Folder}}"
         data-msg-blocked="{{.Blocked}}"
         data-msg-waiting="{{.Waiting}}"
         data-msg-uploading="{{.Uploading}}"
         data-msg-storing="{{.Storing}}"
         data-msg-row-stored="{{.RowStored}}"
         data-msg-stored-one="{{.StoredOne}}"
         data-msg-stored-many="{{.StoredMany}}"
         data-msg-none-stored="{{.NoneStored}}"
         data-msg-fresh="{{.Fresh}}"
         data-msg-refused-one="{{.RefusedOne}}"
         data-msg-refused-many="{{.RefusedMany}}"
         data-msg-unsure-one="{{.UnsureOne}}"
         data-msg-unsure-many="{{.UnsureMany}}"
         data-reason-toobig="{{.ReasonTooBig}}"
         data-reason-binary="{{.ReasonBinary}}"
         data-reason-empty="{{.ReasonEmpty}}"
         data-reason-unreadable="{{.ReasonUnreadable}}"
         data-reason-noanswer="{{.ReasonNoAnswer}}">
      <input type="file" id="file" name="file" multiple accept=".txt,.md,.markdown,.csv,text/plain,text/markdown">
      {{/* Muted by memoria.css on [rst-dropzone-hint]. (Not the design
           system's muted-cell utility: that is a class, and spelled as an
           attribute it styled nothing at all — nineteen places looked
           muted in the markup and read as body text on the screen. They
           are rst-muted now, which memoria.css styles.)

           Both paragraphs are `hidden` so a scriptless page promises no
           drop target. drop.js unhides the note while it is still EMPTY,
           before it ever writes into it: a live region that enters the
           accessibility tree in the same tick as its first message is
           commonly not announced at all, and a refusal nobody hears is
           the one outcome this feature must not have. */}}
      <p rst-dropzone-hint hidden>{{.Hint}}</p>
      <p rst-dropzone-note role="status" aria-live="polite" hidden></p>
    </div>
    {{end}}
    <div rst-form-bar><button rst-btn="primary">Store it</button></div>
  </form>
  {{if .Flash}}<div rst-callout rst-tone="{{.FlashKind | tone}}"{{if eq .FlashKind "danger"}} role="alert"{{end}}><div rst-callout-body><p>{{.Flash}}</p></div></div>{{end}}

  {{/* The upload tray. It lives OUTSIDE the form on purpose: it is not
       something the form submits, and a scriptless browser must find the
       form exactly as it was. Scriptless it is `hidden` and empty, so it
       is not on the page at all.

       drop.js unhides it — still empty — at its ready step, for the same
       reason it unhides the note there: [rst-tray-status] is the live
       region that announces what a drop did, and a live region that
       enters the accessibility tree in the same tick as its first
       message is commonly not announced at all. Only [rst-tray-status]
       is live. The rows are not, and must not be: five files uploading
       is five rows changing several times a second, and a live region
       over that is a screen reader nobody can use.

       Every word here comes from dropZone in handlers.go, like the data
       attributes above — the tray and the flash sentence a scriptless
       browser sees are the same strings, so they cannot drift.

       The document list is on the index, not here, so once anything is
       stored the tray points there with a real link. Nothing follows it
       on its own: someone mid-drop does not want the ground moving under
       them. When a drop settles drop.js re-fetches this page and swaps
       its one rst-refresh region, the passage count in the footer. */}}
  {{with .Drop}}
  <div rst-tray hidden role="region" aria-labelledby="tray-title">
    <div rst-tray-head>
      <span rst-tray-title id="tray-title">{{.TrayTitle}}</span>
      <button type="button" rst-btn="quiet compact" rst-tray-dismiss>{{.TrayDismiss}}</button>
    </div>
    <ul rst-tray-list></ul>
    <p rst-tray-status role="status" aria-live="polite"></p>
    <p rst-tray-listed hidden>{{.Listed}} <a href="/">{{.ViewDocs}}</a></p>
  </div>
  {{end}}
</section>
{{end}}