As a long-time WordPress user with numerous production sites, I actively follow WordPress news. This post curates some recent developments and resources I found particularly interesting.
-
Advanced Custom Fields (ACF): Iain Poulson's guide highlights ACF's crucial role in enhancing WordPress's content management capabilities, particularly its custom block functionality. This is a must-read for anyone seeking granular control over data modeling.
-
Designing with WordPress Blocks: Mel Choyce's presentation (video linked) demonstrates the surprising design flexibility of the WordPress block editor, showcasing visually appealing pages built solely with core blocks like Columns, Spacers, and Cover blocks.
-
Local Pro Goes Free: Sarah Gooding announces WP Engine's decision to make Local Pro free for all users, a significant cost saving for many developers. The one-click admin login feature is a personal favorite. (Disclosure: Flywheel sponsors this site.)
-
Simplified Block Spacing with CSS: Michelle Barker shares a CSS technique using
:is()
and:where()
to create cleaner, more maintainable styles for nested WordPress blocks. -
Faust.js for Headless WordPress: Will Johnston introduces Faust.js, a framework from WP Engine simplifying headless WordPress development, particularly data fetching, authentication, and SSR/SSG. It's built on Next.js.
-
A Proposal for a WordPress Performance Team: Ari Stathopoulos advocates for a dedicated performance team within WordPress, acknowledging the platform's lagging performance compared to competitors. This is a significant challenge given the influence of third-party themes and plugins.
-
Understanding
theme.json
: Ellen Bauer's explanation oftheme.json
in WordPress block themes provides insight into this crucial file for styling control, particularly relevant for Full Site Editing (FSE). (Related resources by Eric Karkovack and Annie McCarthy are also linked.) -
Mastering the Query Loop Block: Justin Tadlock's deep dive into the Query Block in WordPress 5.8 highlights its importance in FSE, offering a powerful way to query and visually style data within blocks.
-
Encute Plugin for Script/Style Management: Mark Jaquith's Encute plugin offers a streamlined approach to managing scripts and styles, a valuable alternative to the now-defunct MinQueue. This allows for better control over resource loading and optimization.
My primary method for managing links is the Notion Web Clipper, organizing them in a central Notion table for later review and tagging. My workflow is essentially RSS → Notion → WordPress.
The above is the detailed content of Links on WordPress I. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

CSS blocks page rendering because browsers view inline and external CSS as key resources by default, especially with imported stylesheets, header large amounts of inline CSS, and unoptimized media query styles. 1. Extract critical CSS and embed it into HTML; 2. Delay loading non-critical CSS through JavaScript; 3. Use media attributes to optimize loading such as print styles; 4. Compress and merge CSS to reduce requests. It is recommended to use tools to extract key CSS, combine rel="preload" asynchronous loading, and use media delayed loading reasonably to avoid excessive splitting and complex script control.

ThebestapproachforCSSdependsontheproject'sspecificneeds.Forlargerprojects,externalCSSisbetterduetomaintainabilityandreusability;forsmallerprojectsorsingle-pageapplications,internalCSSmightbemoresuitable.It'scrucialtobalanceprojectsize,performanceneed

No,CSSdoesnothavetobeinlowercase.However,usinglowercaseisrecommendedfor:1)Consistencyandreadability,2)Avoidingerrorsinrelatedtechnologies,3)Potentialperformancebenefits,and4)Improvedcollaborationwithinteams.

CSSismostlycase-insensitive,butURLsandfontfamilynamesarecase-sensitive.1)Propertiesandvalueslikecolor:red;arenotcase-sensitive.2)URLsmustmatchtheserver'scase,e.g.,/images/Logo.png.3)Fontfamilynameslike'OpenSans'mustbeexact.

Autoprefixer is a tool that automatically adds vendor prefixes to CSS attributes based on the target browser scope. 1. It solves the problem of manually maintaining prefixes with errors; 2. Work through the PostCSS plug-in form, parse CSS, analyze attributes that need to be prefixed, and generate code according to configuration; 3. The usage steps include installing plug-ins, setting browserslist, and enabling them in the build process; 4. Notes include not manually adding prefixes, keeping configuration updates, prefixes not all attributes, and it is recommended to use them with the preprocessor.

CSScounterscanautomaticallynumbersectionsandlists.1)Usecounter-resettoinitialize,counter-incrementtoincrease,andcounter()orcounters()todisplayvalues.2)CombinewithJavaScriptfordynamiccontenttoensureaccurateupdates.

In CSS, selector and attribute names are case-sensitive, while values, named colors, URLs, and custom attributes are case-sensitive. 1. The selector and attribute names are case-insensitive, such as background-color and background-Color are the same. 2. The hexadecimal color in the value is case-sensitive, but the named color is case-sensitive, such as red and Red is invalid. 3. URLs are case sensitive and may cause file loading problems. 4. Custom properties (variables) are case sensitive, and you need to pay attention to the consistency of case when using them.

CSSselectorsandpropertynamesarecase-insensitive,whilevaluescanbecase-sensitivedependingoncontext.1)Selectorslike'div'and'DIV'areequivalent.2)Propertiessuchas'background-color'and'BACKGROUND-COLOR'aretreatedthesame.3)Valueslikecolornamesarecase-insens
