Not as "child friendly" as they imply
-
I was looking for a blank theme, a responsive framework with minimal styles so I don’t need to spend a lot of time over-riding what’s already there. Skeleton is not a blank theme. I would call it more a “no frills” theme, but to “child theme” it is a PITA, especially due to the use of embedded CSS. What *is* the point of this?
There’s no reason at all a “skeleton” theme, made to be a blank slate, should have styles that need to be over-written, much less ones that are embedded with style tags. I shouldn’t have to use “!important” in order to style what is supposed to be a blank theme.
The 2 blue images on the background…that shouldn’t be happening, either.
You’ve already got 10-15 different stylesheets, what is the reasoning behind FORCING a style by way of using the style tags (*after* the child CSS is called)???
<link rel='stylesheet' id='skeleton-style-css' href='https://www.example.com/dir/wp-content/themes/skeleton-child/style.css' type='text/css' media='all' /> <link rel='stylesheet' id='skeleton-theme-settings-css-css' href='https://www.example.com/dir/wp-content/themes/smpl-skeleton/css/layout.css' type='text/css' media='all' /> <style type='text/css'> body { color: #333333; font-family: Sans-Serif; background-color: #f9f9f9; } h1,h2,h3,h4,h5 { font-family: Sans-Serif; } a,a:visited { color: #3376ea; } a:hover, a:focus, a:active { color: #3376ea; } #header h1#site-title a { color:#375199; } h3.widget-title, #header span.site-desc { color:#BE3243; } </style>
If you want to force your styles in the theme, then don’t bill it as “fully child-themeable.”
- The topic ‘Not as "child friendly" as they imply’ is closed to new replies.