Displaying 1 To 10 Of 10 Comments Do You Mistrust A Company That Misspells WordPress? @Viktoria Michaelis – Darn it! :) Also I’ve clearly missed some recent discussion on this topic which, from the sounds of other people’s comments, caused Jeff to open this poll. To me though, Jeff made a clear point. He asked whether you’d mistrust a company who misspell WordPress. He didn’t ask anything about educating people on the correct spelling or whether community involvement correlates with ability. As per my first comment, it comes down to due diligence. If a company who claims to specialise in WordPress can’t spell its name correctly on their home page, how can I have trust in their other quality control procedures? » Posted By John Blackbourn On May 17, 2013 @ 11:40 AM The inability of some people to correctly read the subject of an article correctly also bothers me. » Posted By John Blackbourn On May 17, 2013 @ 11:02 AM If a company bills themselves as a general web development agency that does “Word(p)ress” along with other technologies, then fine, I can deal with it. I don’t expect everyone to use the exact correct spelling of everything all the time (for example GitHub has a capital H which I often forget). However, if a company bills themselves as “Word(p)ress specialists” then they won’t get a second look. If you claim to specialise or be an expert in something then you are setting yourself up to be held to high standards. Misspelling the product you specialise in is not acceptable. » Posted By John Blackbourn On May 17, 2013 @ 9:59 AM At 10 Years Old, Is It Time To Fork? It boils down to figuring out a way to remove all the stuff that’s not needed in WordPress and coming up with a lean, modular core. Rather than talking about vague abstractions like modules, forks, core plugins or a lean, modular core, it would be more productive to talk about specifics. What exactly can or should be removed from WordPress core and packaged into an optional module? People seem to be talking about WordPress lately as if it’s some kind of bloatware. It’s a mature application supports a wide variety of server configurations. This is the reason that there are portions of the code that are more complex or more bloated than they would otherwise be. WordPress does a lot, but I honestly can’t think of a lot that would make sense to move into an optional module without causing unnecessary confusion or frustration for end users. Certainly none that would impact performance to such a degree that it’s justified. It would be good to get some suggestions from people for what specifically could be removed or placed into optional modules, and then discuss the impact and the advantages of doing so. » Posted By John Blackbourn On May 8, 2013 @ 5:58 PM The cynic in me is tempted to say that I’d expect uptake from the major theme vendors to be low (especially “premium” theme vendors). By using framework-specific hooks in their themes, they are essentially creating a lock-in, similar to the lock-in created by theme- and framework-specific shortcodes. Bad for customers, bad for the community, good for the theme vendors who want make it hard for customers to switch to themes by other theme vendors. If they were to start using these standardised theme hooks they reduce lock-in and potentially reduce recurring revenue. I would love to be proved wrong and see some good uptake from theme vendors once a nice set of standardised hooks have been agreed on. Also, for anyone looking for Doug’s blog post, it’s here: http://literalbarrage.org/blog/2012/06/29/wordpress-theme-hook-alliance/ » Posted By John Blackbourn On July 6, 2012 @ 6:57 AM Some Orgnizations And WordPress Just Don’t Mix It’s a pity Kevinjohn Gallagher didn’t mention which CMS he’ll be switching to. Out of the most popular open source CMSes out there, none of them fulfill all of his requirements out of the box, and I’ll be damned if any of them have such an extensive plugin architecture as WordPress so that they can be made to do so. If he’s switching to a proporietary CMS then that’ll be fun getting it to do what he wants. » Posted By John Blackbourn On January 10, 2012 @ 12:13 PM Chip Bennett Working On New Template Hierarchy Diagram Chip I think your comment system swallowed my comment (no feedback after posting it) so I’ll post it here. Good work Chip! This is a really nice improvement. There’s an error though (looking at rev 3). The is_tax() conditional isn’t true for category and tag archives as the diagram states. The “Taxonomy Archive” block should be removed, and the “Category Archive”, “Tag Archive”, and “Custom Taxonomy Archive” blocks should be moved up to the same level as “Date Archive”, “Author Archive” and “Custom Post Type Archive”. Also the “Custom Post Type Archive” block can have “post-type-archive post-type-archive-$posttype” added for its body classes. John » Posted By John Blackbourn On October 27, 2011 @ 3:48 AM A Theme With 70 Different Widget Spots This is a classic case of a theme trying to please everyone by providing a ridiculous and unmanagable amount of customisation. When you get to this point, it’s futile and you end up pleasing nobody. » Posted By John Blackbourn On October 25, 2011 @ 11:26 AM WordPress Has A Smaller Community Than Either Drupal Or Joomla @donnacha of WordSkill – Agreed. Just some crappy linkbait. » Posted By John Blackbourn On September 26, 2011 @ 11:31 AM Should Automatic Upgrades Be Opt-In? I agree with Ipstenu. The only way automatic updates will have any real effect is if they are opt-out. Opt-in is just as ineffective as the current situation. » Posted By John Blackbourn On September 8, 2011 @ 12:02 PMComments Posted By John Blackbourn
«« Back To Stats Page