WordPress and Default Themes
·
First we had Twenty Ten. Then came Twenty Eleven. Then came the potential of a new default theme every year. We’re doing it wrong.
·
First we had Twenty Ten. Then came Twenty Eleven. Then came the potential of a new default theme every year. We’re doing it wrong.
·
I recognize a lot of what we, in the WordPress community, do wrong, but I also want to highlight several things we do right.
·
This is a problem for which I don’t have a solution. It is also one where I think most of the proposed solutions are problems to begin with.
·
When someone hacks a plugin or theme, it’s bad. When someone hacks the foundation of those systems (WordPress), it’s worse. When someone hacks the base upon which WordPress is built (Apache, Nginx, or whatever server you use), it’s tragic.
·
I love WordPress, both because it’s free and because it’s free.
·
In a community steeped in so much confusion about the names, duties, and roles of various players, why are we still confusing the conference issue when it comes to WordCamp SF?
·
I use WordPress every day. So why am I constantly critical of the platform and its features?
·
I’d like to see WordPress allow multiple repositories to be registered side-by-side with WordPress.org’s official API.
·
Does highlighting the framework with which you developer over the language devalue your worth as a developer?
·
My first experience with a dynamic website was in high school. I was in a Venturing Crew, and my friend Taylor had helped us put our group online with a website hosted by another friend. This website was built in classic ASP and used a Microsoft Access database on the back-end to house content. I