Context Keywords. Context Keywords provides a context condition reactive to the searched keywords used to find your site. This opens up the possibility of customizing a user's experience according to keyword patterns the context administrator defines. A default token is also included, which allows activation of a context if no other keyword contexts are active. This module currently works with Google(incl. Instant Search), Bing, Yahoo and Ask. Dependencies Context 3.x Other Context Plugins Debugging Instructions detailing how to easily test various keywords are included in the README.txt file, as well as in the description on the context edit page.
Page Title. The word "title" is a bit overloaded. Every piece of content in Drupal has a title, and so does every page. The page title is the one found in the HTML head inside the <title> tag. It is also used on SERPs (Search Engine Result Pages) and can greatly enhance your websites SEO (Search Engine Optimization). This module gives you granular control over the page title. You can specify patterns for how the title should be structured and, on content creation pages, specify the page title separately to the content's title. Page Title 2 What features are in Page Title 2? Token Integration: This module integrates with the fantastic Token module. Handy modules which work with Page Title There are now a few modules which help you use Page Title to get the best out of your SEO. Content Optimizer - provides you with an inline keyword analysis of your content.SEO Friend - Generate reports of content SEO across the site (eg, which pages are missing Page Titles or Meta Tags) Testing Page Title API Drupal 5.
Meta tags quick. Meta tags support based on Fields API. Included modules Starting from version 7.x-2.1, meta tags functionality is splitted to several modules: metatags_quick Main module. Adds meta tags support for site pagesmetatags_quick_import Imports nodewords (D6) datametatags_quick_extra (Experimental) automatic settings. Alternatives Comparison of meta tags generation modules can be found here. Upgrade from nodewords Upgrade path from existing nodewords data (D6) is possible in 7.x-2.x series. Module installation Place the entire metatags_quick directory into your Drupal sites/all/modules/ directory.Enable Meta tags (quick) module by navigating to: Administer > ModulesConfigure module-specific settings: Administer > Configuration > Search and meta data > Meta tags (quick) settings.
Financial support I have started this project as my personal workaround of the meta tags problem in Drupal 7. Taxonomy Title. This module was designed to update the heading tag at the top of the taxonomy term page. The contents of this H1 (or sometimes H2) tag are *extremely* important for SEO (Search Engine Optimization). People interested in SEO may prefer to add more user-friendly, keyword-rich, and descriptive words to this heading element. This is the only module that let's you control that title individually for every term. (You can also override the title generally by using a view or a pannel.) The taxonomy title module also provides tokens which can be used in conjunction with the Page title and Meta tags modules.
The Page title module is designed to let you control the title tag in the HTML Header of your page. Note: The D5 version of Taxonomy Title must be invoked from the theme, and requires a minor change to your template.php file (example included). This module was written by Jen Lampton of Jeneration Web Development. Wysiwyg.
Allows the use of client-side editors to edit content. It simplifies the installation and integration of the editor of your choice. This module replaces all other editor integration modules. No other Drupal module is required. The Wysiwyg module supports any kind of client-side editor including HTML editors (a.k.a. WYSIWYG), pseudo-editors (buttons to insert markup into a textarea), or even Flash-based applications. The editor library must be downloaded separately. Various editors are supported (see below). The Wysiwyg module also provides an abstraction layer for other Drupal modules to integrate with any editor. Discussions happen in the Wysiwyg group, and in IRC #drupal-wysiwyg. Installation Download and install the module as usual.Go to Administer » Site configuration » Wysiwyg, and follow the on-screen installation instructions that are displayed there.Follow the on-screen installation instructions.
Further documentation Supported editors/plugins Contribute Maintainers Project links. Footermap: a footer site map. Generates a site map as a block placed in the footer region by default. It recursively searches through the base menu id (mlid) and outputs a basic list of links ordered by sub-menus. This is dynamically generated versus more traditional theme layer based implementations such as seen in Bartik in Drupal 7.
Footermap will be generated based off of Drupal 8's menu router system instead of pulling together from the database layer to make more efficient use of cache. This module was originally developed per request by a client of Kosada Incorporated (a small Columbus Ohio-based consulting firm) and has been used in several other Drupal site projects. Footermap will automatically search for url_aliases if the path.module is enabled. Theming has changed again, which should offer more flexibility in template preprocess or template for overriding what menu, children, and individual menu items to display. Please review the changes before updating to 1.1 if you have not already used 1.1-beta1.
Search 404. Scheduler. Scheduler gives content editors the ability to schedule nodes to be published and unpublished at specified dates and times in the future. Dates can be entered either as plain text or with calendar popups. In Drupal 6 and 7 to use calendar popups you need to install the Date Popup module, which is part of the Date module. In Drupal 8 this is built into Core. Scheduler for Drupal 8 We are actively developing the first 8.x release of Scheduler. You can check the progress of 8.x development and help with these 8.x issues Notes Please check if cron is running correctly if scheduler does not publish your scheduled nodes.Scheduler only does publishing and unpublishing of nodes.
Credits Scheduler is the work of many people. Translations Translations to other languages than English can be found over there: Screencasts If you want a quick introduction to what Scheduler does, check out these nice screencasts: Menu attributes. References. This project provides D7 versions of the 'node_reference' and 'user_reference' field types, that were part of the CCK package in D6, at functional parity with the D6 counterparts. See for details. Note for users upgrading from References 7.x-2.0-beta3 There were a couple changes in the way 'References' views are handled ("referenceable nodes/users defined by a view"), which might require double-checking those existing on your site: The 'label' (node title or user name) is no longer automatically added if not included in the view.
Note for users upgrading from CCK D6 The References project integrates with the content_migrate module present in CCK 7.x-2.x-dev to allow the migration of field definitions and field values from D6 nodereference and userreference fields. Similar modules: