Thing I plan to do is to make many websites based on Drupal core.
All of these websites will be quite small, but there will be many of them (in matter of hundreds).
I'm working on this with one HTML / CSS coder, guy who should make themes for every website we make.
He doesn't know much of a PHP (enough for PHPTemplateEngine tho) therefor I what I want is to make as little interaction between me and him as possible. He shouldn't touch PHP part of themes, I shouldn't touch HTML part of themes.
My question is:
Can you tell me what structure of theme folder should I use, what's your opinion of Zen theme for beginning of Drupal theming and how can I make automatic JavaScript and CSS loading script for themes?
Also I'd greatly appreciate any tips concerning multi-site Drupal setup, best practices and so on.
Thanks in advance.
With regards to drupal theming you have a couple of options:
If all the themes will share 98% of the same code base and just have different classes etc to style it visually different (say a different heading colour), then you can get away with one drupal theme and use theme settings to alter the configuration of the theme on each site. This has the advantage of having to maintain only one code base. Zen can still be used as a base theme if you wish
Another option is one you have mentioned above, in which you have a base theme which declares all inherited code, and sub themes to which override specific parts of the base theme to create the necessary effects. I would suggest that this is the better option if your themes vary wildly from one site to another. There is a administrative burden with this option though, as say you have 100 sites, you could potentially have 100 sub-themes to maintain and provide fixes for.
Related
I have been asked to create an eCommerce website for a client on a strict budget. I figured using WordPress would be my best bet in this case. I am new to both WordPress and developing an eCommerce/online store. I intended on designing and developing my own bespoke theme for the client, however their limited budget does not accommodate the fee I quoted for designing and developing a bespoke theme. Therefore, I thought that a free theme would be the most suitable option in working within the constraints of the budget.
My questions regarding using the free theme are:
What are the limitations to using a free pre-made theme in terms of its styling, look and layout (structure)? For example, could I easily move the logo or other elements and graphics to elsewhere on the same page if I wanted or I am stuck with having those items wherever they are originally placed? In other words, what flexibility do I get in changing the design?
How 'unique' could I expect it to look with some customization?
What are the limitations on features and functionality?
Would I get more design flexibility with a premium theme instead?
There are pretty much no limitations.
You can make a child theme out of the free theme, then you can customise the css and php files which make up that theme, as much as you like. That will allow you to do everything you mention in point 1. See http://codex.wordpress.org/Child_Themes for details.
Wordpress provides a simple web interface that allows you to view and edit the files, or you can just edit them using your favourite code editor.
The idea with a child theme is that any file which you customize overrides the file in the original theme. This means if there are updates to that theme in the future, you can safely download them without wiping out the customisations you've made.
I would recommend you start with something like the twitter bootstrap theme for wordpress, which gives you a neutral design and quite a lot of useful javascript functions. That will help you with point 2 - ensuring uniqueness, as you don't start with something that already has a distinctive look and feel.
re: point 3 - that's the great thing with wordpress. Just add plugins and widgets (or even develop your own). There really are no limits.
To answer point 4: Premium themes typically provide more sophistication in terms of design features and add-ins like scrollers, slideshows and shortcodes. Sometimes they also provide customised interfaces that allow limited customisation such as colour schemes and page layout, but essentially the wordpress interface for customisation is the same, whether you've paid for the theme or not.
This is a serious question, specifically relating to the many frameworks out there for Wordpress and Joomla - Warp, T3, Gantry etc. What I dont understand is how they are different to a starter template and what exactly you are supposed to do with them - simply child theme them or is it a whole other codex to learn? I mean, all of the native codex is there with Joomla and WP anyway to construct a theme simple enough so what good does a whole proprietary app do between your design and the CMS? Are they faster to develop with?
What confuses me is that people seem to love them and claim that they make life easier but I dont get how adding another technology to learn can make things easier. Like I say, it is a serious question, not one for effect to make a point.
Can anybody define the difference between a framework and a starter template? I ask in part because I am one of those anxious developers who always feels like I am somehow missing a trick or doing things the "wrong" way - what am I missing?
This is definitely mostly an issue of definition, and I can guarantee that some cases will not follow what I outline below. Obviously, anyone is free to call the template/framework by whatever they want.
Generally though, a template is comprised of basic HTML and CSS that works with the platform (Wordpress, Joomla, etc) that is used to build the output to the page. In Wordpress, this contains the loop and other constructs to get all the content for the page. In Joomla, it outlines all the module positions available and such.
Typically when you purchase a higher end theme, you will have significant choices on the backend to customize the theme without having to actually code. These parameters let you typically change colors and such.
Some of the theme developers and others have taken this parameter settings system to the next level and made it into a framework. In all the cases that I've seen, "framework" is really the basis for the template parameter system. In this way, you can have consistency between different themes and expect the same settings and features between different themes. This is why they use a different word, because it really isn't a "theme" any more. It really is like a "theme engine" in that it is a backend system for changing things in the theme.
Yes, many platforms offer some basic options for editing the theme out of the box, so in most cases, the framework is really an improvement on the base platform's theme engine.
It's been my experience that a theme will be a visual style along with a set of theme options available in the admin (in addition to Customize if it's supported).
Theme Frameworks on the other hand, like Thesis, are installed just like a theme but have a very vanilla visual style that you build your theme on top of. Usually the framework provides many added features that aren't available in WP core.
tl;dr - Themes frameworks aren't installed and used right away, they are installed and built upon to deliver a site.
First of all i don't have any experience on wordpress.. So please forgive my ignorance.. I've found a theme on themeforest. Unfortunately it's a wordpress theme. I want to develop my own admin panel. I don't want to use wordress. Is it possible?
Anything is possible, however this is a gum in hair scenario. Ask the theme author if there is an HTML version which is common on ThemeForest. If you do try to "extract" the layout:
Begin with the stylesheet and match up the styles with each page template's markup.
Also, why not use WordPress? The Redux theme options framework is very easy to use.
Since a wordpress theme is just a bunch of html/css/js/php files, yes, it is possible. Depending on what language/framework will used backend side, the easiest way would be to extract the html/css/js parts of the theme and than add your own "content-placeholders" which will be used by your own backend.
But: Think twice about doing this. First, there could be a conflict with the license of the theme (depending on what type of license is used by the author of the theme). And more important, second, you should think twice about building your own backend.
For the case this isn't an experiment and you're building a productive website, building you're own backend is a lot of work. Unless you need some special functionalities (or you would like to keep it very slim and basic), I would suggest using a ready made CMS for this - like wordpress.
My opinion: 95% of self-made backends for basic cms features I've seen (and was forced to work with) are very messy and far beyond available open source cms. It seems like many people don't balance the pros and cons of building an own CMS-backend and undervalue the effort to build a state-of-the-art CMS.
I hope this is not too basic to be off-topic, but I am wondering to what extent it is possible to customize WordPress to fit an existing design. I have a design in mind and read somewhere (WordPress manuals?) that it is possible to only manage a small part of a website with WordPress and then slowly migrate the whole site to be WordPress-managed. If one would like to preserve a certain design, is this preferred to tweaking WordPress templates? That is to say, should I start from a website and slowly move into WordPress, or should I start from the WordPress template, and try to tweak it until I arrive at the design I want. Are there any examples of WordPress sites, which fall into light-weight (but image heavy) websites, which exhibit freedom from the WordPress mold? (Is this too vague?)
Generally speaking, I think it makes more sense to start with WordPress from the start if that is what you intend to use at the end. It will be much easier to transition your site into being fully WordPress-managed after you have some small piece of it in WordPress. This is because, while a lot of the design will fit easily into the HTML WordPress with only minor tweaks, WordPress theming is kind of a specific subcategory of its own, and there will be less of a barrier to moving if your start with CSS that is compatible with WordPress.
WordPress also makes it easy to override individual page nodes, so the static portions of your site can be part of WordPress in a very loose sense, and you'll have full control over the markup. It is less to start writing your markup knowing what you've already had to do to get your design to work with WordPress than to transition to WordPress later.
If you are new to WordPress theming, here are some links to get you started:
http://codex.wordpress.org/Theme_Development
http://themeshaper.com/2009/06/22/wordpress-themes-templates-tutorial/
Your approach depends on the technical capabilities of you to setup two sites that live next to each other.
In general, you'll have to modify Wordpretss theme to fit your design. I prefer something of a skeleton theme - http://themehybrid.com/themes Skeleton/Hybrid one. The thing about this approach is that you'll have to build your design from ground up and fit it into Wordpress way of doing things. Wordpress likes to output HTML with additional CSS styles and it's usually much easier to use those elements then to modify them to fit yours.
My personal choice, I'd start using WordPress right away, learn as much as I can about the CMS aspects, you have great tutorials at WP101 (dot) com then move to create or built your own templates. I'd suggest you first start with a simple template like Twenty Ten and modify it then perhaps you can use Responsive which is my favorite or many others. This 2 sites for example were built in WP
http://www.philiphousenyc.com/ and
http://www.danielhopwood.com/
Good Luck,
Mike
I'm developing a web site for a further education college in the UK, using Drupal (6.19). The site won't contain a huge volume of content and the structure is fairly simple.
I understand HTML and I have an reasonable understanding of PHP, SQL and CSS. I've created a sub-theme based on Genesis, but I'm feeling a bit out of my depth.
In your opinion, based on my level of skill, is it best to create a theme from scratch, or should I continue to develop my Genesis sub-theme?
Thanks,
Mike
As a general rule it makes sense to build on top of a starter theme such as Zen, ninesixty, or genesis. Those themes provide considerable functionality that is not worth rewriting. I'm not that familiar with genesis, but the other two provide a CSS reset, skiplinks to navigation for accessibility, SEO-sensitive content ordering, inline edit controls, and much more. Also, as with any piece of Drupal, when problems are discovered and corrected, you can update the base of your subtheme and get the fixes for free. Unless you have specific requirements that can't be met by subtheming, I recommend using a base theme.