More Intergration & Less Code
Are you talking about the core WordPress code of theme code??
At the rate that WP is growing, I strongly doubt that “less code” is an option. Also, IMO, more files (separate files) keep development, hacks, and other modifications organized.
In the mean time, there are plenty of useful guides and documents available for any interested user at http://codex.wordpress.org
WordPress is nothing. Try working with PostNuke for a year…you’ll come back and appreciate how truly tiny it is. 😉
I am refering to the overall wordpress folder structure so many files to change anything you have to look through a 100 files 🙂
here’s an example the stylesheet.css i’m looking to change to the color of the links on the sidebar and in looking through the css file it’s like looking for a needle in a haystack i haven’t been able to find the right css to change the color, this should be much more easier i would think. Unless we create our own style.css to make it more simple
I realize as WP continues to grow so will the coding of course but I would also imagine that a more effective organizational pattern is to keep it more simple less folders, less coding better interface easy to work in it.
Well, normally you shouldn’t have to change *any* of the core WP files, so most people wouldn’t have that complaint. And the few that do need to change core files probably know what they’re doing and won’t have that complaint. WP is pretty well organized, internally. There are only 4 folders with required files in them (besides “
/“). Seems straightforward enough, given their names.
As for the CSS file, blame the theme/template/style author, not WP. The stylesheets can be as simple or complex as the person creating them desires.
To change the colours of the links in the sidebar, start by finding the
#sidebarID in the stylesheet. Then look for
#sidebar Ain there. If that doesn’t exist, create it and assign a colour to it. You might need to mess with the anchor pseudo-classes to make it work though:
#sidebar A:active, #sidebar A:visited, #sidebar A:link
Are you talking about the css file for the theme or for the admin panel? Because the css for themes are dependant on the theme author. And that’s just the nature of the css beast.
ic you are right, the programmers know what all these files and how to navigate, i guess i’m looking at it from a user end someone who knows nothing about coding. But more often than not i’m forced to have to go through the core files just to change something or to find out why something may not be working. I’ll keep learning 🙂
Hmm. I haven’t had to change a thing in the core code. Template stuff is different of course. But even so, the internal structure of php isn’t nearly as difficult to parse as some stuff I’ve run across – js for instance is much more a nightmare to me than is php.
The complexity of the CSS varies with the complexity of the themes. Each individual characteristic of the CSS relates to an individual characteristic of the blog. For example, if you want post text to be black, headers to be purple, and links to be blue, then you need at least 3 entries in your CSS. The only way to simplify that would be to compromise and make all text (post text, headers, and links) one color, like purple (thus requiring only one entry). You may want to read through these: http://codex.wordpress.org/CSS
is there a way to make the blog main index refer to a
?page_id=12 or ?cat=3
without messing up the posts (?cat=#) it appears that WP places the ?cat=# after whatever URL you put in the options area
I want to give it a home page so users don’t have to come to an index page filled with many posts instead a clean homepage then they can browser through categories
- The topic ‘More Intergration & Less Code’ is closed to new replies.