In reply to Justin Tadlock.

About the CSS, I could have chosen a better word I guess, I should have said hand coded and not hard coded.

As far as the silly example that I brought up - the Real Estate site, using CPT or not or using a plugin or theme to code it, has NO bearing in what we are talking about here. The issue on hand was old-school vs new-school. And unless I'm totally wrong, Justin, by you suggesting to use metadata (which I had already suggested - because it's the only way), you are re-enforcing my argument. By using metadata, you are separating content from design. Not only you are separating the two, but you are getting the data and structuring it by field types (at least that's what ACF and Tooset do). And that is old-school, which makes it very much alive, and still necessary in many instances.

Nothing is perfect though... With metadata you get really bloated databases that Gutenberg avoids by combining the content with the design, but once again, that could be another blog post idea to explore.

Bottom line, using blocks or metadata will depend on one's priorities and necessities, and both approaches have their advantages and disadvantages. I think it's up the Tavern's of the world to bring up these controversial subjects to raise awareness, resulting in better core code quality and make things better. There is a reason while WP is 41% of the Internet, we are never going to see the next Facebook, or Twitter, and any app. type site, like a globally popular Classified, or Auction site, made with WordPress. Before jumping on me again, I'm talking about sites with millions of users, and billions of records in the database(s). Of course, it is possible to go the WP route, but it will be extremely expensive, in terms of hosting and database load balancing - you better use something else.