Skip to main content

2 or 3 approaches to build a homepage or landing page through Drupal

Please include any limitations & considerations of each approach

Building a homepage a few options to consider and should against a business case:

 

1. Article

An article – create a new node (assuming a least one content type exists), then using Basic Site Settings (admin > config > system), scroll down to Front Page and enter the node.nid value or alias.

  • Pros:
    • Fast to apply
  • Cons:
    • Limited to only having one node appearing on the home page

 

2. Views

Create a view that references a collection of nodes using one or more content types.  This approach can also utilise Solr, if the dev has set up Solr on the server.

  • Pros:
    • Relatively easy to create;
    • Have more than one node appearing;
    • Filters can be applied in the set-up of the view, or if you really want they can also be exposed at the front-end;
    • More features and functionality can be applied
  • Cons:
    • Front-end work will be required to manage the layout unless you have a flexible and well-prepared theme

 

3. Custom module

Want something completely different on the home page.  Custom away.

  • Pros:
    • Huge flexibility in what you want to create
  • Cons:
    • Time-consuming;
    • As code updates are applied to the core, the risk increases in having to maintain your code.  Due to an update where you have deprecated functions.
       

Related articles