I should clarify a bit. Don't run a contest where you use Twitter as the main way for people to enter the contest. Unless you already have a large following, you will be disappointed.
I'm a big fan of the Quicktabs module, which easily lets you create tabbed content in Drupal. However, there is an SEO problem that people should be aware of when using it.
On my Pitbulls.org site, I noticed Google indexing multiple versions of the same page. This is known as duplicate content and it can penalize your rankings. Given that I had already modified my robots.txt file specifically to prevent this type of thing, I was a little confused.
No, this isn't another boring rehash of technical specs and righteous, ecstatic sermons on "openness". Because honestly, no one really cares. At least, not anyone who actually matters: an average consumer.
This is about the general marketing behind the devices, and why Apple wins and Droid loses.
The Facebook Like button is showing up everywhere. And while it may seem simple to put it on your Drupal nodes and pages, it's a little trickier than normal.
You can't just put a piece of javascript in a .tpl file like you can with the old Facebook Share widget, because you need to dynamically pass the URL of the current page yourself.
But it's easy to accomplish. The following is for Drupal 6.
One of the reasons Yahoo Search is somewhat less trusted in the industry is because they have a paid inclusion system. In order to increase rankings to your site, all you really had to have was enough money. Very simple for people to buy rankings of some form or another. (This is all moot, of course, when Bing takes over their search).
When developing CrowdedText.com, I ran into the problem of needing read-only fields once a node had been created. I didn't want to prohibit editing completely. Only for a few fields.
You can't just hide or disable the field, although that's a necessary step. Anyone with a tool like Firebug would still be able to edit the html in real-time and submit the form, changing the value. When some of your backend logic depends on the keeping these values accurate, this is a big no-no.
Technology shouldn't be used just for the sake of technology. It should have a clear benefit that you can measure. I could have the best shovel every made, hand-forged and encrusted with diamonds with a gold-trimmed handle (my dream), but if all I can do with it is dig holes, then fill them back up, what good is this ultimate shovel?
Technology shouldn't be used just for the sake of technology. It should have a clear benefit that you can measure. I could have the best shovel every made, hand-forged and encrusted with diamonds with a gold-trimmed handle (my dream), but if all I can do with it is dig holes, then fill them back up, what good is this ultimate shovel?
