OK, we need to add the document level design. The doctrine is the trainign and coumentaiton for how to handle issues in an emergency. Eg, Are pets allowed in the shelfter, what are the rules for that. How long can someone stay at a shelter. How to support dietary restrictions. What support services are avaiabile after a housefire
Now I understand the flow. I need to create a doctrine detail/reader screen that shows the actual policy content - things like pet shelter rules, stay duration, dietary accommodations, and post-disaster support. Let me create a rich document reader view.
I've added a complete Doctrine Detail screen with rich, structured content for emergency response policies. It includes sample doctrine for pet policies, shelter stay duration, dietary restrictions, and post-fire support services. The detail view features collapsible sections with visual styling for different content types (warnings, tips, policies, checklists), bookmark and download actions, an "Ask about this" button for AI queries, and related document links. The doctrine list now navigates to the detail view when tapped.
I've completely redesigned the doctrine detail screen as a long-form article reader. It now features flowing content with proper typographic hierarchy (h2 headers, bold subheadings, bulleted lists, paragraphs), a reading progress bar at the top, and rich sample content covering real Red Cross topics like pet shelter policies, stay duration, dietary restrictions, and post-fire support services. The content scrolls naturally like a Medium article with a summary at the top and an "Ask AI" callout mid-article.