Subir

Crear una vista en Grid Responsive con Drupal 7

Vista Grid Responsive Drupal 7

¿Cómo podemos, sin complicarnos mucho, crear una Vista en nuestro proyecto Drupal 7, en su formato parrilla o Grid, que se adapte a dispositivos móviles?. Es decir, convertirla la Vista en Responsive.

Buena pregunta. Así que vamos a probar un módulo llamado Views Responsive Grid, que nos asegura que va a conseguir este objetivo de manera sencilla.

Descargamos, instalamos y activamos el módulo como es costumbre, y creamos una Vista nueva.

En Formato: Seleccionamos Responsive Grid y básicamente el número de columnas inicial.

En las propias instrucciones ya nos advierte el desarrollador, que sí, la plantilla en la que estamos trabajando, ya es responsive, necesitamos asignar nuevas clases css para las columnas y las filas.

Temas blog: 
Imagen de rummykhan
SOBRE EL AUTOR

Experto en desarrollo de portales web, comercio electrónico y seo.

Añadir nuevo comentario

Filtered HTML

  • Las direcciones de las páginas web y las de correo se convierten en enlaces automáticamente.
  • Etiquetas HTML permitidas: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Saltos automáticos de líneas y de párrafos.

Plain text

  • No se permiten etiquetas HTML.
  • Las direcciones de las páginas web y las de correo se convierten en enlaces automáticamente.
  • Saltos automáticos de líneas y de párrafos.
CONTENTS OF THIS FILE --------------------- * About Drupal * Configuration and features * Installation profiles * Appearance * Developing for Drupal ABOUT DRUPAL ------------ Drupal is an open source content management platform supporting a variety of websites ranging from personal weblogs to large community-driven websites. For more information, see the Drupal website at http://drupal.org/, and join the Drupal community at http://drupal.org/community. Legal information about Drupal: * Know your rights when using Drupal: See LICENSE.txt in the same directory as this document. * Learn about the Drupal trademark and logo policy: http://drupal.com/trademark CONFIGURATION AND FEATURES -------------------------- Drupal core (what you get when you download and extract a drupal-x.y.tar.gz or drupal-x.y.zip file from http://drupal.org/project/drupal) has what you need to get started with your website. It includes several modules (extensions that add functionality) for common website features, such as managing content, user accounts, image uploading, and search. Core comes with many options that allow site-specific configuration. In addition to the core modules, there are thousands of contributed modules (for functionality not included with Drupal core) available for download. More about configuration: * Install, upgrade, and maintain Drupal: See INSTALL.txt and UPGRADE.txt in the same directory as this document. * Learn about how to use Drupal to create your site: http://drupal.org/documentation * Download contributed modules to sites/all/modules to extend Drupal's functionality: http://drupal.org/project/modules * See also: "Developing for Drupal" for writing your own modules, below. INSTALLATION PROFILES --------------------- Installation profiles define additional steps (such as enabling modules, defining content types, etc.) that run after the base installation provided by core when Drupal is first installed. There are two basic installation profiles provided with Drupal core. Installation profiles from the Drupal community modify the installation process to provide a website for a specific use case, such as a CMS for media publishers, a web-based project tracking tool, or a full-fledged CRM for non-profit organizations raising money and accepting donations. They can be distributed as bare installation profiles or as "distributions". Distributions include Drupal core, the installation profile, and all other required extensions, such as contributed and custom modules, themes, and third-party libraries. Bare installation profiles require you to download Drupal Core and the required extensions separately; place the downloaded profile in the /profiles directory before you start the installation process. Note that the contents of this directory may be overwritten during updates of Drupal core; it is advised to keep code backups or use a version control system. Additionally, modules and themes may be placed inside subdirectories in a specific installation profile such as profiles/your_site_profile/modules and profiles/your_site_profile/themes respectively to restrict their usage to only sites that were installed with that specific profile. More about installation profiles and distributions: * Read about the difference between installation profiles and distributions: http://drupal.org/node/1089736 * Download contributed installation profiles and distributions: http://drupal.org/project/distributions * Develop your own installation profile or distribution: http://drupal.org/developing/distributions APPEARANCE ---------- In Drupal, the appearance of your site is set by the theme (themes are extensions that set fonts, colors, and layout). Drupal core comes with several themes. More themes are available for download, and you can also create your own custom theme. More about themes: * Download contributed themes to sites/all/themes to modify Drupal's appearance: http://drupal.org/project/themes * Develop your own theme: http://drupal.org/documentation/theme DEVELOPING FOR DRUPAL --------------------- Drupal contains an extensive API that allows you to add to and modify the functionality of your site. The API consists of "hooks", which allow modules to react to system events and customize Drupal's behavior, and functions that standardize common operations such as database queries and form generation. The flexible hook architecture means that you should never need to directly modify the files that come with Drupal core to achieve the functionality you want; instead, functionality modifications take the form of modules. When you need new functionality for your Drupal site, search for existing contributed modules. If you find a module that matches except for a bug or an additional needed feature, change the module and contribute your improvements back to the project in the form of a "patch". Create new custom modules only when nothing existing comes close to what you need. More about developing: * Search for existing contributed modules: http://drupal.org/project/modules * Contribute a patch: http://drupal.org/patch/submit * Develop your own module: http://drupal.org/developing/modules * Follow best practices: http://drupal.org/best-practices * Refer to the API documentation: http://api.drupal.org/api/drupal/7