Media Library  [[3. Resources/Readwise/Full Document Contents/Articles/Media Library|Full Document Contents]] ## Document Notes --- tags: - #wordpress - #gutenberg - #phase3 Author: Make WordPress Core Source: Make WordPress Core (Website) Reference: https://make.wordpress.org/core/2023/07/07/media-library/ date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} --- # Title: Media Library — Phase 3 vision for WordPress media management ## Table of Contents: - [[#📝 Summary:]] - [[#📖 Main Content:]] - [[#🗒️ Notes]] - [[#📖 References:]] - [[#🗣️ Paraphrase:]] - [[#📰 Newsletter:]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical validity]] - [[#🔍 DARVO Analysis]] - [[#🔍 SEO Evaluation]] - [[#🎯 Conclusion]] ### References: - Make WordPress Core, “Media Library” (2023-07-07): https://make.wordpress.org/core/2023/07/07/media-library/ ## 📝 Summary: This post outlines a Phase 3 initiative to overhaul WordPress’s Media Library and related media flows. Goals include expanding media management (categorization, tagging, improved filtering), unifying the Media Library with the block editor and single-media views, enhancing image editing (cropping, duotone, focus point), improving handling of non-image media (audio, video, files), integrating Openverse attribution and contributions, revisiting publishing flows for media/format-driven posts, and tightening block integration with attached media. The Scope lists concrete next steps across UX, technical integrations, workflows, and block-level enhancements. Key themes: - Better organization (categories, tags, date groupings, filters) - Unified, modern image tools (cross-context cropping, focus point, duotone, thumbnail management) - Block-aware media flows and admin-wide drag-to-upload - Attribution and Openverse contributions within WordPress - Improved bulk operations, featured media types beyond images, and enhanced media blocks ## 📖 Main Content: The article argues that media has lagged behind block editor progress and now requires focused attention. It proposes: - Management improvements: tagging/categorization, better attached-media visibility, clearer library UI, and filters suited to large teams with separate ingestion workflows. - Editing improvements: unify and modernize image tools across contexts; simplify thumbnail decisions by letting WordPress select sizes at runtime; add non-destructive duotone and focus point controls stored as media data. - Non-image media: enhance audio/video/file handling; revisit a native Playlist block via the Interactivity API; better presentation in block lists and templates. - Workflows and publishing: require steps like alt text/attribution before publishing; support media/format-driven posts for expressive publishing. - Scope details: migrate media UI to modern data stores (wordpress/data), integrate patterns into media exploration, surface tools in the command center, incorporate featured image in-canvas, support other featured media types, strengthen bulk editing, and enable drag-to-upload anywhere. Personal insight: - This roadmap recognizes media as a cross-cutting concern: editorial workflow, accessibility, performance, and developer experience. The emphasis on runtime file-size selection and storing focus points suggests a move toward smarter, context-aware rendering rather than static authoring choices. Integration with Openverse aligns with open culture and attribution best practices, which could meaningfully improve legal/ethical media use at scale. ### 🗒️ Notes - Vision and Goals - Expand media management capabilities for larger teams and collaboration. - Unify Media Library with block editor and single-media views. - Improve major media flows across ingestion, editing, and publishing. - Organization & Discovery - Add categories/tags for media; improve filters and date headings. - Make attached-media relationships discoverable and actionable. - Design enhancements for grid/list views for clarity and speed. - Image Editing Alignment - Unify cropping tools across contexts; support custom aspect ratios. - Let WordPress auto-select file sizes at runtime; revisit default thumbnail sizes for modern screens. - Non-destructive duotone at library level; store and reuse focus point data in blocks (e.g., Cover). - Non-Image Media - Improve audio/video/file handling and block APIs. - Resurface a native Playlist block via Interactivity API. - Attribution and Openverse - Track attribution metadata and integrate Openverse more deeply. - Explore contributing to the commons from within WordPress. - Workflows & Publishing - Require steps like alt text, captions, attribution before publish. - Prevent external images on publish if disallowed. - Enhance media/format-driven publishing; featured image in-canvas when applicable. - Block Integration and UX - Blocks aware of attached media; suggest unused attachments inline. - Expose media actions in command center; show previews in block list. - Drag-to-upload anywhere in editor/admin. - Bulk Ops and Featured Media - Strengthen bulk attach/edit; support featured media types beyond images. - Follow through on attachment templates and single-image expansion. - Technical Direction - Migrate to wordpress/data and modern components. - Patterns integrated into media browsing for rapid layout previews. ## 📖 References: - Make WordPress Core: “Media Library” (2023-07-07) — https://make.wordpress.org/core/2023/07/07/media-library/ - Openverse project overview — https://openverse.org/about - WordPress Interactivity API overview — https://developer.wordpress.org/block-editor/reference-guides/packages/packages-interactivity/ ## 🗣️ Paraphrase: 1) Original idea: “We should revamp the image editing interface and align with current block editor tools… reduce the burden on picking the right file size… allow non-destructive duotone… store focus point information for automatic use in blocks.” Paraphrase: The image editor should match the modern block tooling, unify and improve cropping, and relieve users from manually choosing file sizes by handling that automatically. Authors should be able to apply reversible duotone effects in the library, and define a focal point that blocks can read to render images optimally. 2) Original idea: “On the management side… categorization and tagging, better handling of attached media… bulk attach media files… important for collaboration.” Paraphrase: For media management, add categories/tags, make attachment relationships clearer, and allow bulk attachment of files to posts. These features will better support teams where media ingestion happens independently from writing. ## 📰 Newsletter: This week in WordPress, we’re leveling up your media game. The Core team shared a Phase 3 vision for a smarter, friendlier Media Library—think tags and categories for assets, unified cropping across contexts, automatic image-size selection at runtime, and a non-destructive duotone you can set once and reuse everywhere. Focus points become first-class: set it in the library and your Cover blocks thank you later. Audio/video fans: better handling is on deck, plus a native Playlist block powered by the Interactivity API. Accessibility and ethics get a boost too, with attribution tracking and deeper Openverse integration—potentially including contributing to the commons right from WordPress. Developers, you’ll see tighter block/media integration, drag-to-upload anywhere, and modernized data stores via wordpress/data. Bonus: workflows can require alt text, captions, and attribution before publish. Links: - Media Library Phase 3 overview (Make/Core): https://make.wordpress.org/core/2023/07/07/media-library/ - Openverse: https://openverse.org/ - Interactivity API reference: https://developer.wordpress.org/block-editor/reference-guides/packages/packages-interactivity/ > [!note]+ Document Notes > tags: > - #wordpress > - #gutenberg > - #phase3 > Author: Make WordPress Core > Source: Make WordPress Core (Website) > Reference: https://make.wordpress.org/core/2023/07/07/media-library/ > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # Title: Media Library — Phase 3 vision for WordPress media management > <!-- deep-read:sections start --> ## Table of Contents: - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#-notes) - [📖 References](#-references) - [🗣️ Paraphrase](#-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical validity](#-logical-validity) - [🔍 DARVO Analysis](#-darvo-analysis) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ### References: - Make WordPress Core, “Media Library” (2023-07-07): https://make.wordpress.org/core/2023/07/07/media-library/ ## 📝 Summary: This post outlines a Phase 3 initiative to overhaul WordPress’s Media Library and related media flows. Goals include expanding media management (categorization, tagging, improved filtering), unifying the Media Library with the block editor and single-media views, enhancing image editing (cropping, duotone, focus point), improving handling of non-image media (audio, video, files), integrating Openverse attribution and contributions, revisiting publishing flows for media/format-driven posts, and tightening block integration with attached media. The Scope lists concrete next steps across UX, technical integrations, workflows, and block-level enhancements. Key themes: - Better organization (categories, tags, date groupings, filters) - Unified, modern image tools (cross-context cropping, focus point, duotone, thumbnail management) - Block-aware media flows and admin-wide drag-to-upload - Attribution and Openverse contributions within WordPress - Improved bulk operations, featured media types beyond images, and enhanced media blocks ## 📖 Main Content: The article argues that media has lagged behind block editor progress and now requires focused attention. It proposes: - Management improvements: tagging/categorization, better attached-media visibility, clearer library UI, and filters suited to large teams with separate ingestion workflows. - Editing improvements: unify and modernize image tools across contexts; simplify thumbnail decisions by letting WordPress select sizes at runtime; add non-destructive duotone and focus point controls stored as media data. - Non-image media: enhance audio/video/file handling; revisit a native Playlist block via the Interactivity API; better presentation in block lists and templates. - Workflows and publishing: require steps like alt text/attribution before publishing; support media/format-driven posts for expressive publishing. - Scope details: migrate media UI to modern data stores (wordpress/data), integrate patterns into media exploration, surface tools in the command center, incorporate featured image in-canvas, support other featured media types, strengthen bulk editing, and enable drag-to-upload anywhere. Personal insight: - This roadmap recognizes media as a cross-cutting concern: editorial workflow, accessibility, performance, and developer experience. The emphasis on runtime file-size selection and storing focus points suggests a move toward smarter, context-aware rendering rather than static authoring choices. Integration with Openverse aligns with open culture and attribution best practices, which could meaningfully improve legal/ethical media use at scale. ### 🗒️ Notes - Vision and Goals - Expand media management capabilities for larger teams and collaboration. - Unify Media Library with block editor and single-media views. - Improve major media flows across ingestion, editing, and publishing. - Organization & Discovery - Add categories/tags for media; improve filters and date headings. - Make attached-media relationships discoverable and actionable. - Design enhancements for grid/list views for clarity and speed. - Image Editing Alignment - Unify cropping tools across contexts; support custom aspect ratios. - Let WordPress auto-select file sizes at runtime; revisit default thumbnail sizes for modern screens. - Non-destructive duotone at library level; store and reuse focus point data in blocks (e.g., Cover). - Non-Image Media - Improve audio/video/file handling and block APIs. - Resurface a native Playlist block via Interactivity API. - Attribution and Openverse - Track attribution metadata and integrate Openverse more deeply. - Explore contributing to the commons from within WordPress. - Workflows & Publishing - Require steps like alt text, captions, attribution before publish. - Prevent external images on publish if disallowed. - Enhance media/format-driven publishing; featured image in-canvas when applicable. - Block Integration and UX - Blocks aware of attached media; suggest unused attachments inline. - Expose media actions in command center; show previews in block list. - Drag-to-upload anywhere in editor/admin. - Bulk Ops and Featured Media - Strengthen bulk attach/edit; support featured media types beyond images. - Follow through on attachment templates and single-image expansion. - Technical Direction - Migrate to wordpress/data and modern components. - Patterns integrated into media browsing for rapid layout previews. ## 📖 References: - Make WordPress Core: “Media Library” (2023-07-07) — https://make.wordpress.org/core/2023/07/07/media-library/ - Openverse project overview — https://openverse.org/about - WordPress Interactivity API overview — https://developer.wordpress.org/block-editor/reference-guides/packages/packages-interactivity/ ## 🗣️ Paraphrase: 1) Original idea: “We should revamp the image editing interface and align with current block editor tools… reduce the burden on picking the right file size… allow non-destructive duotone… store focus point information for automatic use in blocks.” Paraphrase: The image editor should match the modern block tooling, unify and improve cropping, and relieve users from manually choosing file sizes by handling that automatically. Authors should be able to apply reversible duotone effects in the library, and define a focal point that blocks can read to render images optimally. 2) Original idea: “On the management side… categorization and tagging, better handling of attached media… bulk attach media files… important for collaboration.” Paraphrase: For media management, add categories/tags, make attachment relationships clearer, and allow bulk attachment of files to posts. These features will better support teams where media ingestion happens independently from writing. ## 📰 Newsletter: This week in WordPress, we’re leveling up your media game. The Core team shared a Phase 3 vision for a smarter, friendlier Media Library—think tags and categories for assets, unified cropping across contexts, automatic image-size selection at runtime, and a non-destructive duotone you can set once and reuse everywhere. Focus points become first-class: set it in the library and your Cover blocks thank you later. Audio/video fans: better handling is on deck, plus a native Playlist block powered by the Interactivity API. Accessibility and ethics get a boost too, with attribution tracking and deeper Openverse integration—potentially including contributing to the commons right from WordPress. Developers, you’ll see tighter block/media integration, drag-to-upload anywhere, and modernized data stores via wordpress/data. Bonus: workflows can require alt text, captions, and attribution before publish. Links: - Media Library Phase 3 overview (Make/Core): https://make.wordpress.org/core/2023/07/07/media-library/ - Openverse: https://openverse.org/ - Interactivity API reference: https://developer.wordpress.org/block-editor/reference-guides/packages/packages-interactivity/ ## ✅ Action Items: Tailored prompt for your role and goals: - Map article themes to advocacy and OSPO priorities: - Open-source advocacy: Emphasize Openverse contributions, attribution tracking, and ethical media use as part of open culture. - Contributor engagement: Highlight opportunities for contributors across UX, accessibility, workflows, Interactivity API, and data-store migration. Identify onboarding paths for first-time contributors via media UI polish, documentation, and testing. - Education: Develop curricula on “Media workflows in WordPress,” including alt text best practices, focus point usage, runtime image decisioning, and pattern-driven media layouts. - Sustainable funding: Connect improved media infrastructure to ecosystem value (hosting/CDN partners, educational institutions, public media) to justify sponsorships and Five for the Future commitments. - OSPO trajectory: Frame the Media Library work as a governance-friendly initiative with clear scopes (bulk ops, attribution, accessibility gates) and measurable outcomes (reduced support tickets, improved upload->publish time). - Create an outreach plan: - Run community workshops on focus points, duotone, and alt-text workflows. - Pilot contributor cohorts around “drag-to-upload anywhere” and “attached media discoverability.” - Publish transparent dashboards tracking adoption, a11y compliance, and contributor diversity for media-related projects. - Build bridges: - Coordinate with hosting teams (e.g., GoDaddy) to test runtime size selection and performance impacts on real-world sites. - Partner with Openverse to streamline in-WP contributions and legal review workflows. - Develop artifacts: - Tutorial series and GitHub starter issues for migration to wordpress/data. - Pattern library examples showing “media-first” page assembly, with a11y checks baked in. Use this single prompt for each new article you process: “Analyze how this article’s proposals intersect with open-source advocacy, contributor onboarding, and education in the WordPress ecosystem. Identify concrete contributor entry points, recommend inclusive educational materials, suggest governance metrics suitable for an OSPO, and propose partnerships that support sustainable funding. Conclude with a transparent rollout plan that includes accessibility gates, DEIB commitments, and measurable community outcomes.” ## 🧪 Hypotheses: - Adding media categories/tags will reduce asset retrieval time and improve editorial throughput for multi-author sites. - Storing focus point data at the media level will increase above-the-fold visual quality and reduce manual cropping by authors. - Auto-selecting image sizes at runtime will decrease Largest Contentful Paint (LCP) variability across devices. - Workflow gates (alt text, attribution) will improve accessibility compliance without significantly increasing time-to-publish after initial training. - Integrating Openverse contributions within WordPress will increase commons contributions and proper attribution usage. ### 📊 Methodology: - Data sources: WordPress.com/hosting telemetry (with consent), site-owner surveys, support tickets, GitHub issues, lab benchmarks of LCP/CLS with/without runtime sizing, usability tests with editors. - Designs: A/B testing (runtime sizing vs. manual selection), controlled usability studies for focus point tool discoverability, time-motion studies for bulk attachment workflows, accessibility audits on gated workflows. - Analysis: Mixed-methods—quantitative performance metrics (Web Vitals), qualitative thematic coding for usability feedback, interrupted time series to measure rollout effects. ### ❓ Questions: - What taxonomy model best fits media (built-in vs. custom, hierarchical vs. flat)? - How can runtime image-size selection respect responsive images and art direction choices? - What metadata model stores focus point, duotone, attribution in a portable way? - How to prevent friction from required a11y gates while maintaining compliance? - What is the roadmap for featured media types beyond images (video covers, 3D, SVG animations)? - How will command center actions integrate with role/capability checks? ### 🔮 Future Research: - Performance tradeoffs of runtime sizing vs. pre-generated thumbnails at scale. - Cross-site media hubs for multi-site organizations with shared taxonomies. - Intelligent suggestions: “unused attachments” surfaced contextually by content semantics. - Interactivity API patterns for media playlists, clips, and chapters. - Provenance and licensing: standardized schemas for attribution and license enforcement. ### 💡 Implications: - Better editorial velocity and consistency across teams. - Stronger accessibility culture through workflow gates and education. - Increased legal compliance and ethical media use via built-in attribution. - Improved Core–host collaboration around performance and media CDN strategies. - Clearer contributor onramps, growing the maintainer pipeline. ### 🧠 Learning Styles Assessment: Readability: Approximately 11th–12th grade (concise but technical; assumes WordPress familiarity). - Visual Learners - Present: Conceptual structure, but few visuals. - Improve: Add UI mockups for cropping, focus point, duotone; flowcharts for ingestion->publish; comparison screenshots for before/after library views. - Aural Learners - Present: None. - Improve: Provide an audio summary and a short podcast segment discussing rationale and expected benefits. - Verbal Learners - Present: Clear bullet points and feature lists. - Improve: Add examples and short scenarios (“An editor uploads 100 assets…”). - Physical Learners - Present: None. - Improve: Interactive prototypes or sandbox tasks (e.g., try focus point on sample images). - Logical Learners - Present: Structured scope list. - Improve: Include decision trees for image-size selection and workflow gate logic. - Social Learners - Present: Implied collaboration (teams, workflows). - Improve: Link to discussion threads, calls for testing, and Slack channels for feedback. - Solitary Learners - Present: Self-paced reading. - Improve: Reflection prompts and a checklist to evaluate one’s current media workflow. - Naturalistic Learners - Present: Not applicable. - Improve: Use nature-based image examples to illustrate focus point/art direction decisions. ### 📊 Accessibility Assessment: - Screen Reader Compatibility: The post is likely semantic (heading structure common on make.wordpress.org). - Improve: Ensure all images have alt text and headings follow a logical hierarchy; include captions for example images. - Keyboard Navigation: - Improve: Verify all interactive elements (if any demos are added) are tab-navigable with visible focus styles. - Contrast and Readability: - Improve: Maintain high contrast; ensure code/UI screenshots meet contrast guidelines or provide descriptions. - Text Resizing: - Improve: Confirm responsive typography does not break layout; avoid fixed-height containers for media mockups. ### 🌍 DEIB Assessment: - Cultural Relevance: Neutral, but lacks diverse examples. - Improve: Include case studies from global publishers, community orgs, and NGOs. - Inclusive Language: Generally inclusive and technical. - Improve: Define jargon; provide glossaries for non-native speakers. - Neurodiversity Support: - Improve: Break complex sections into shorter paragraphs; add stepwise checklists. - Representation: - Improve: Use inclusive imagery and examples reflecting varied identities and contexts. - Psychological Safety: - Improve: Invite feedback, note that proposals are exploratory, and set norms for respectful discussion; add content warnings if using sensitive media examples. ### ✅ Logical validity: Tone: Professional, forward-looking, solutions-oriented. Positive reasoning observed: - Causal reasoning: “Cropping tools need to be unified… reduce burden on picking right file size… WordPress should determine at runtime.” This links tool unification and automation to reduced user burden. Strengthen by providing data from user tests or support tickets. - Logical flow: Starts with a gap (media lag), proposes goals, then concrete scope. Strengthen by mapping each scope item to a specific problem statement. - Appeal to evidence (implicit): Mentions current screen size distribution to justify revisiting default thumbnails. Strengthen by citing analytics on device breakpoints. - Ethical reasoning: Attribution tracking and Openverse contributions. Strengthen by referencing licensing compliance benefits and accessibility standards. No explicit fallacies detected; the document is a roadmap, not an argumentative essay. To improve rigor, include measurable KPIs (e.g., median time-to-insert-media, % posts with alt text). 🔍 DARVO Analysis: - Deny: Not present; the post doesn’t deny problems—acknowledges slow iteration and discoverability issues. - Attack: Not present; no adversarial framing or blame. - Reverse Victim/Offender: Not present; the post doesn’t cast Core or users as victims; it proposes solutions. - Notes: Tone is collaborative and constructive, with no manipulative rhetoric. ### 🔍 SEO Evaluation: - Keywords: Present implicitly—“Media Library,” “WordPress,” “block editor,” “image editing,” “Openverse,” “Interactivity API.” Could improve density naturally in headings and first paragraph. - Meta Description: Add a concise summary including “WordPress Media Library Phase 3” and “block editor integration.” - Title Tag: “Media Library” is short; consider “WordPress Media Library — Phase 3 Improvements and Roadmap” (within 60 chars). - Headers: Add H2/H3s for Organization, Editing, Workflows, Non-image media, Attribution. - Content Length: Adequate for an announcement; could expand technical details for in-depth SEO. - Internal/External Links: Add links to related Core posts (media filters, attachment templates), and external to Openverse and Interactivity API docs. - URL: Already clean and descriptive. - Image Optimization: If screenshots are added, use descriptive filenames and alt text. - Mobile Optimization: Make site is responsive (it is); ensure images are optimized for speed. - Engagement: Add “Call for testing,” GitHub issues, and discussion links. - Schema Markup: Use Article schema; consider HowTo/FAQ if steps are added. - Social Sharing: Ensure Open Graph/Twitter Card with a descriptive image and summary. ## 🎯 Conclusion: The Media Library Phase 3 vision brings long-awaited, holistic improvements to how WordPress teams organize, edit, attribute, and publish media. By unifying tools across the block editor, automating smart image choices, elevating focus point and duotone as reusable media data, integrating Openverse, and strengthening workflows and bulk operations, WordPress is aligning media management with modern editorial and performance needs. These changes also open clear pathways for contributor engagement, accessibility gains, and ethical use of media across the ecosystem. You have read this document completely (100%). <!-- deep-read:sections end --> ## Highlights - The main goals are to expand the media management capabilities, unify the block edit and single media interfaces, and improve upon the major media flows. ([View Highlight](https://read.readwise.io/read/01h5jr4dk8nkz0rhg5c0r72s11)) - On the management side, it’s time to look at categorization and tagging, better handling of attached media, design improvements to the library views and filtering ([View Highlight](https://read.readwise.io/read/01h5jr8eem8r7xywashxrw8gm6)) - media attachment functionality (items anchored to a specific post) is often hard to discover, the interface is not the most intuitive, and the connection doesn’t necessarily carry through other editing flows in a clear way. ([View Highlight](https://read.readwise.io/read/01h5jr8vfytc1mv9xdjh5fr7dc)) - For larger teams, media ingestion can often be an entirely separate process from writing posts. The ability to bulk attach media files and connect them to the relevant content pieces is thus an important part of the collaborative process. ([View Highlight](https://read.readwise.io/read/01h5jr92etb9vmjn28v1z7qns1)) - Note: A multinational corporation with offices in different countries may have a team of content creators and social media managers responsible for producing blog posts, social media updates, and other forms of content marketing. The company might use a centralized Digital Asset Manager (DAM) to store all their media assets such as images, videos, and audio files. When the content creators need to create a new blog post or social media update, they can browse and search for relevant media assets in the DAM. They may select the images and videos they want to use, and then use the bulk upload feature to transfer them into the WordPress Media Library. Once the media files are in the Media Library, the responsive and user-friendly WordPress interface allows content creators to easily add multimedia content and create visually appealing blog posts, social media updates and other promotional materials. In this way, WordPress Media Library, combined with a centralized Digital Asset Manager, can help corporations to streamline their media ingestion processes and ease the collaborative process between content creators, social media managers, and other stakeholders. - We should also revamp the image editing interface and align with the current block editor tools. ([View Highlight](https://read.readwise.io/read/01h5jrcw76fx7s2as7tgx18rfg)) - Cropping tools in particular need to be unified and further improved ([View Highlight](https://read.readwise.io/read/01h5jrd3amtkc00xkcgtdcbk8w)) - Iterate on how users can visualize and toggle between different thumbnails, while reducing the burden on picking the right file size (WordPress should determine that for you at runtime) ([View Highlight](https://read.readwise.io/read/01h5jrdakfmthebxangq2d5r7e)) - Review default thumbnail sizes to accommodate current screen sizes distribution. ([View Highlight](https://read.readwise.io/read/01h5jrdg4sqj57whvyf4weqdpr)) - It’d be nice to bring UI tools like *focus point control* to the library flows, so that media objects can store that information and be leveraged automatically when inserting on a cover block, or when using an image on a cropped featured media container. ([View Highlight](https://read.readwise.io/read/01h5jrdv6e054cr1fxf8x0ft1k)) - When managing the media library, it should be easy to check and keep track of attribution. As we look into expanding the presence and touch points of [Openverse](https://openverse.org), it’d be interesting to see how contributions to the commons could work directly from a user’s WordPress install. ([View Highlight](https://read.readwise.io/read/01h5jrebqqt9wfkhqq1rkxrd95)) - We should resurface work on a native Playlist block, ideally powered by the [Interactivity API](https://make.wordpress.org/core/2023/03/30/proposal-the-interactivity-api-a-better-developer-experience-in-building-interactive-blocks/). ([View Highlight](https://read.readwise.io/read/01h5jrep4wbyn46fh4ys51frm5)) - Tackle design improvements of the media library elements and see about a path to migrate to `wordpress/data` and newer UI components. Make it even easier to reuse and connect the media experience anywhere on the admin and blocks plugins. ([View Highlight](https://read.readwise.io/read/01h5jrj96zdkn6gpcmgchm9036)) - Look into adding categories and tags support. Explore better browsing organization (for example, date headings and other improvements to the filtering UI). ([View Highlight](https://read.readwise.io/read/01h5jrjcqmafv9ngx6pxjzf3s1)) - Improve inline and freeform cropping across block editor and standalone image editing. Connect cropping variations with defining custom aspect ratios across the block UI. ([View Highlight](https://read.readwise.io/read/01h5jrjh73d77s3cjwej50swf9)) - Explore how patterns could be incorporated into media flows. For example, being able to preview a selection of media (or all attached media) within different media patterns quickly. ([View Highlight](https://read.readwise.io/read/01h5jrjncw206qjzre0s1kmxch)) - Connect with [Workflows](https://make.wordpress.org/core/2023/07/04/workflows/): for example, to require certain steps, such as adding a caption, attribution, alt text, or prevent things like publishing with external images. ([View Highlight](https://read.readwise.io/read/01h5jrjw9nswfthjcrc134f1hz)) - Media flows and block integration should be excellent. For example, make blocks aware of attached media so that inserting an image block could automatically display unused media or allow an author to cycle through those without opening the full media library or browsing through an entire collection. ([View Highlight](https://read.readwise.io/read/01h5jrjzcrz43te7q3h57pzbgq)) - Expose relevant media tools and actions in the command center. ([View Highlight](https://read.readwise.io/read/01h5jrkef5d5zn7sfact23cqv4)) - Improve presentation of media in other editing contexts, like showing small media previews in the block list view. ([View Highlight](https://read.readwise.io/read/01h5jrkmj84q40r4paegpczxkk)) - Incorporate featured image in the canvas of the post editor when the single template uses a featured image block (this is a lingering task from the site and post editor interface work). ([View Highlight](https://read.readwise.io/read/01h5jrks7p8rw9x2sjajc4mtee)) - Look at the possibility of supporting other featured media types beyond images. ([View Highlight](https://read.readwise.io/read/01h5jrkw2gr87cha83h6cmra28)) - Improve upon bulk editing operations, including attaching already uploaded media to a post type. ([View Highlight](https://read.readwise.io/read/01h5jrmanbawn9s67fhdgtnxja)) - Explore treating focal point as image data and make it available to plugins and blocks. ([View Highlight](https://read.readwise.io/read/01h5jrmd1vben106e75bbz18fv)) - Allow operations like drag to upload media anywhere on the editor — and then maybe anywhere on the admin. ([View Highlight](https://read.readwise.io/read/01h5jrmfht37tr1nezyangtk52)) - Follow through on updates to the attachment theme template and single image expand functionality. ([View Highlight](https://read.readwise.io/read/01h5jrmj62hmsptsdxbmqjgpra)) - Review outstanding tasks on main media blocks (image, gallery, cover, video, audio, file, etc) for enhancements and bug fixes. ([View Highlight](https://read.readwise.io/read/01h5jrmn0zrmd5t4jyrrvws8j1)) - Note: I'm sorry, but the text you provided is not an article but rather a collection of highlights from a document titled "Media Library". Therefore, there are no main arguments or supporting evidence to analyze, and there are no logical fallacies employed in the document highlights. The document lists various tasks and goals related to improving and expanding the capabilities of the WordPress media library. These include enhancing the functionality of media blocks, improving bulk editing operations, supporting different types of media, integrating media tools and actions in the command center, improving media presentation and organization, and aligning the media editing interface with the block editor tools. Without the context of the full document, it is difficult to assess the validity and logical coherence of these goals. However, the fact that they are presented as tasks to be reviewed, explored, improved, and unified suggests that they are based on practical considerations and user feedback, rather than being mere assertions or fallacies.