Site structure

Language Switcher for Drupal 7 is an enhancement for core language switcher block in local module. It's very useful for websites with multi-languages where you want to display content in different languages side-by-side. Watch this video to better understand the concept.

Features:

Divide your website page to a number of sections where each sections contains nodes in one language (see the screenshot).

Note:

• When #1164926: Nodes need to have languages specified separately for accessibility lands into D7 core, the code base for this module will be much simpler, and cleaner.
• Currently with core locale module, there is two language switcher blocks, one for interface, and the other for the content. This module should only alter the content one, not the interface one. Currently, it alters the interface block!

How to?

1. Enable Locale and Content Translation modules.
2. Add other languages, e.g. Arabic, French (admin/config/regional/language).
3. Go to Language Switcher config page (admin/config/regional/language/language_switcher), select what mode you want to use.
4. Go the content type you want the translation to be enabled on, select `Enable, with node translation` (e.g. admin/structure/types/manage/article).
5. Add nodes, add translations.

Update December 2011: The listing location module now has a release candidate. The Listing Premium module is now in place to create paid listings of different levels for different periods of time in conjunction with node checkout, node checkout scheduler and scheduler.

The listing module enables listings of all kinds such as jobs, online courses, real estate, hotels, restaurants, classifieds and any kind of business or sales listing, especially those which involve location. It is being developed as a modular system comprising a core listing module upon which different components can be added. The following modules are included.

This module provides the glue that holds together content types, views and other drupal systems to enable:
1. jobs to be applied for, applicants sorted and communicated with.
2. listings to be searched based on location module settings and displayed with map AND listings on same page
3. listing fields to be displayed or hidden according to what the author has paid
4. listings to be searched on based on addresses module and taxonomy module settings
5. menus to be autocreated based on content types and taxonomy
6. and other features

The Giga Menu module enables a standard Drupal menu to be displayed as a Mega Menu.

Flatmenu is a module to display menus on a different way. It shows on a frontpage the top level (Level 0) and his childs (Level 1).

Creates a block with a search box that allows you to find/go to a Drupal Node by NID. I use this on a documentation site -> where I used the NID to track specific solutions. I wanted an easy way to be forwarded to a specific node ny using a Node ID.

Response to the practicality of this module

When I wrote this module I thought that this seems really, really dumb -> but within a certain context, this little module makes sense:

I was building a documentation site for a client where I wanted the (non-drupal) end users to gain quick access to the docs that they need straight away. Since the skill level of the end user wasn't that robust, the easiest and most reliable way was to give them "a reference " number; that number was the NID, of course.

The idea of saying "Well, just go to the site and search ...." isn't really practical as anyone in user experience knows. Also, saying "just type in 'node/42' isn't a practical solution because it leads to questions that are off topic (namely, what is a node?) It is more practical to say -> "Just go to doc 42"

This is an enhanced autocomplete element, that uses the jQuery UI autocomplete. It will also implement a widget for taxonomy.