ProudCity Documents and Meetings

FileToWeb Integration detects ProudCity content only when the relevant post types and hooks exist. It does not require ProudCity classes on ordinary WordPress sites.

Proud Documents

For a PDF-backed Proud Document:

1. The source attachment or document URL is resolved to the original PDF.
2. FileToWeb converts the PDF.
3. WordPress stores a local HTML preview bundle and a provider-neutral preview record.
4. The public Proud Document preview uses WordPress-local HTML when ready.
5. The existing Download action continues pointing to the original PDF.

The administrator can always access:

• Original PDF
• Generated FileToWeb HTML
• FileToWeb editor
• WordPress-local HTML copy
• Sync, poll, or retry action

Non-PDF documents and Office previews are left unchanged.

Meeting materials are independent

Agenda, Agenda Packet, and Minutes are separate source attachments. Each receives its own:

• FileToWeb document identity
• Status and page count
• Original PDF link
• Generated HTML link
• FileToWeb editor link
• Sync, poll, and retry lifecycle
• WordPress-local preview artifact

This matters because meeting records are iterative. An Agenda can be published first, an Agenda Packet later, and Minutes weeks afterward without reprocessing the other materials.

Meeting actions

• Sync this PDF submits only that row's attachment.
• Poll status refreshes only that material.
• Retry processing appears for a failed material.
• Sync all meeting PDFs submits every present PDF on the current Meeting.

The larger FileToWeb meeting PDFs panel remains available at the bottom of the edit screen even when inline controls also appear beside ProudCity's Change File and Remove File actions.

Public behavior

On supported ProudCity releases:

• The Download action keeps the original PDF URL.
• A ready preview uses the provider-neutral ProudCity endpoint and WordPress-local HTML.
• Public requests do not contact FileToWeb to render the completed preview.
• Missing, disabled, or unsafe local preview artifacts fall back to the original PDF.
• Agenda, Agenda Packet, and Minutes fallback independently.

Deactivation support

Completed Proud Document and Meeting previews can survive FileToWeb plugin deactivation only when ProudCity core and theme include the provider-neutral preview contract.

Deactivation stops new sync and polling. ProudCity itself continues serving completed local preview records. See Public replacement and plugin lifecycle before testing deactivation.

Generic page and widget links

Literal PDF links in ordinary page content, attachment URLs, and supported widgets are rewritten by the active FileToWeb plugin.

These generic rewrites are different from the durable ProudCity preview contract. If the plugin is deactivated, arbitrary page and widget links are no longer dynamically rewritten by FileToWeb.