The link module provides a standard custom content field for links. With this module, links can be easily added to any content types and profiles and include advanced validating and different ways of storing internal or external links and URLs. It also supports additional link text title, site-wide tokens for titles and title attributes, target attributes, CSS class attribution, static repeating values, input conversion, and many more.
Drupal 7: Fields API is provided already by core [no dependencies].
Drupal 8: Link module is in core now. No module installation needed. Yay! Don't forget to activate it. It's deactivated by default.
INFO Since some misleading user reports we need to clarify here - Link module is NOT about to add links to any menus or the navigation nor primary/secondary menu. This can be done with default menu module (part of Drupal core). The Link module provides an additional custom field for storing and validating links to be added with any content type, which means another input block additional to your text-body, title, image and any other input you can make on new content creation.
The Panels module allows a site administrator to create customized layouts for multiple uses. At its core it is a drag and drop content manager that lets you visually design a layout and place content within that layout. Integration with other systems allows you to create nodes that use this, landing pages that use this, and even override system pages such as taxonomy and the node page so that you can customize the layout of your site with very fine grained permissions.
The SpamSpan module obfuscates email addresses to help prevent spambots from
collecting them. It is based on the technique from spamspan but has undergone major modifications, as the original spamspan code hasn't been updated since 2007.
The currently maintained portion of this module is a very simple scraper that can take a URL and beginning and ending code and display the result in a block. (This could easily be extended to display on a page.)
It does not store this scraped data at the moment, therefore it is necessary to use the blockcache module and replace the scraped_content block with its cached equivalent. Otherwise the page you are scraping is called every time the scraped_content block is viewed.
4.7 only: This module also contains code from an industrial strength scraping module written for 4.7, which is not maintained, Legacy scraper.