Tumblr is where tens of millions of creative people around the world share and follow the things they love.Sign up to find more cool stuff to follow
Весьма доволен тем, что в свое время набрел на эту систему управления содержимым сайта (CMS - Content Management System). Сделав на ней сайт, смог предоставить возможность вести его (добавлять содержимое) - другим людям.
Но всё течет и изменяется. В начале этого года вышла уже версия 7.0 (которая ныне “доросла” до 7.8). Ну и как бы надо начинать осваивать, а то сайт на старой версии. И это может оказаться чревато.
Опять же мне всегда хотелось попробовать такой формат, как wiki.
Сегодня наконец удалось разобраться, как на localhost устанавливается wiki-сборка Drupal с русским интерфейсом. Так что впереди ожидает много интересного. Осваивать и осваивать
Singular theme to rule them ALL!
Yay! OSSCube and related micro-sites powered by Singular theme (Drupal 6).
As the OSSCube progressing with time and exploring more markets. Exploring & hitting on new territories.
The time for makeover for the old site. Looks needs to be more polished, dynamic and professional. And the old site sucks BIG! at typographical level.
That was the most major reason to polish the site and commence the retheming (drupal themer/coder perspective) or I would like to say realignment phase (saving time and efforts to reach to the desired result). And not changing the architecture level of the site.
To serve this requirement, i come up with concept of single theme named Singular theme. And Singular theme is makeover of the land theme(old Drupal theme for osscube.com) which is initially based on garland theme.
Singular theme is a much compressed and carries no bull shit code from its parent theme. And have my best of the best efforts for Singular theme at that span of T.I.M.E.
All of the design decisions regarding alignment, the look and feel were taken solely be me.
Some of the salient points answered by Singular theme are as follows:
- Less focus on image gradients. Heavy use of CSS3 based gradients. Few lines of code, That ease substantial amount of pain from the server in terms of HTTP request. (for eg. www.osscube.com/portfolio )
- Making best use of Google font API. Using Droid Sans from Google font directory and going for fresh look as depicted in home page slider
- Using CSS3 transition properties to have the APPEAL in the content, which responds to you hover interactions as in picture set osscube.com/resources/pictures Go and Play!
- Writing highly scalable code, that helps to cut down the time and efforts for development and also for maintenance phase of the different version of the site. That also means in simple terms that other designer or UI person need not to put much efforts to chew the code. He can work straight through it.
- First the Singular theme turn on www.osscube.com (here ‘s the tweet from timeline history) And later turned on other micro site and just visual level tweaks was just few hours job (if done well with focus!).
- Changed completely the look of blog section. This page usage of CSS3 is very high in terms of drop shadows and gradients in right side bar. That also means major amount of time spent in browser rather in photo-editing app. following the Design in browser methodology.
- There is no conditional css hack system to serve the IE browser (7,8 or 9 in future). A common css code in theme for all the majority of browser. That also means writing cross browser code in stylesheets.
- Tested in Firefox, Chrome, Safari, Opera, IE7 and IE8. Infact tested in IE6 also. But not supported for IE6. Just wanted to see how ugly the site looks in this special version of IE browser.
In nutshell Looks Good and Loads up fast!
Talking on UI/UX is Good only If you are doing and implement it. Talking on it is very easy.
Will come back with some more good news.
Bye! for now : )
Hey, hey Eric! Want a balloon?
Today I finished my first custom module for Drupal Commerce, the new integrated e-commerce solution for Drupal 7. DC is finally kicking old UberCart out of the playground, and that’s good for at least two reasons.
First, UberCart sucks hard! Not that it doesn’t work, is just that it’s much more a piece of code somehow glued to Drupal than a real Drupal module.
Second, DC make an example on how a Drupal module should be realized.
Instead of writing tons of code to implement what was already there, but with little variations, DC seems much more of a wrapper for Drupal abstract components.
I just scraped its surface writing a very Quick&Dirty custom module but, well… how could I say? What I quickly ended up to is not so dirty. I felt at home in a consistent environment, always knowing where to look and what to expect, even when docs was not so enlightening.
If on the developer side Commerce is a charm, I think it is even better on administrator side, since once you’ve mastered Rules and Views there is almost nothing you can’t do with Commerce, and it remains steady and clean.
I really think DC is showing every Drupal developer the way to go. Now I hope Drupal 8 will allow us to retain this same approach, solving current API hell! :P
Little challenge: can you guess citation in the title?