I tried to make a custom login box based on the tutorial http://drupal.org/node/92657, but i can't get around a couple of strange problems. Maybe it's because of my modifications of the garland theme, but nearly every primary link leads to a different format of the said box.
Its quite hard to explain, please just see for yourself at http://www.kjs-aktiv.at as you click through the primary links (groups, content...)
There is great module - audio_attach.module It's very useful for me. But I want upload new audio files to attach them to node without deliing old files. How I can do this?
Does enybody met this problem?
I am reposting this thread in theming to spark some ideas on how should pursue a clients need and to create an amazing theme in my study of CSS. all thoughts are welcome
After a year with Drupal and much growth with how web development is evolving I am leaning on learning more about the CSS that is the back bone of the themes or labels that present the mechanics of our websites. I am using Style Master, Mac Rabbit, Go live, and Photoshop for all my web creation. There is also a book out there called "CSS in Ten Minutes" - that you need to read for about 1000 minutes if you don't understand CSS. The Drupal Theme Garden has had a world of improvement over this growing very quickly year. After dealing with many new clients since my start of representing Drupal. I have discovered what really needs to be to developed in a theme which will make Drupal stand completely in front of the pack as a CMS is a universal theme with an admin area that is more elaborate than the new Garland Theme. I have a new client that has requested a theme that changes background colors with every page so that every node can be published in a unique color scheme - tall order or what!
It's as though the theme should have settings that interact within the publishing of the node -seems possible. As everything depends on the right mind writing the code. But most importantly to show the true strength of a CMS like Drupal you should be able to decide if new nodes can be fluid or Fixed, a choice on how many columns and blocks are going to be set when the node is published, if you want your header or footer to change and resizing of logos as well. It is as though you would have to meld a WYSIWUG editor with what work was done with the Meta Theme and then push that development to yet another level. If you catch my drift this is what my clients are pushing for of how much layout control is desired when publishing any new content. I am also thinking the permissions would have to be set as what type of node designs users would be able to published.