#display suite

[throughjo]

luxury gold, minimal grey, dark blue...

Sales office for NV/9 ARTKVARTAL by Alexander Volkov Architect

[devekko-blog]

Page Builder Dark Magic Locked Forever

Page Builder Dark Magic Locked Forever

A free of paid Page Builder for Drupal and WordPress, at first feel like magic, but the Light can soon turn to Darkness.

Web CMS like Drupal and WordPress save development time and this thinking leads to the magic of Page Builder. But is this bait and switch? Does complexity and increased total cost of ownership follow this initial simplicity? Are you locked in forever with a Page Builder?

Page…

View On WordPress

[torchboxdrupal]

Display Suite code fields

We've been using code fields for all little while now so I thought it best to do a little write up on how we've recently used them.

We have a site which used a list field to select which background image to use on a field. It was to illustrate what kind of specie the page was about. It was straight-forward and worked well. But the client wanted to adapt on this and make each illustration of the species, this would mean having at least 80 different images in the CSS file and the client would have to come to us when they wanted it updating. Not really ideal.

So with the power of two new fields and a Display Suite code field we created them something they could manage themselves.

Firstly, we added two image fields, one for each hover state. We decided not to use sprites because it would mean the client would need to make them and the less work they have to do the better.

Then we created the code field. This is the code we put into Field code

<?php if (!empty($entity->field_custom_illustration_hover)) : ?> <div class="illustration-ds-field" style="background-image: url([node:field_custom_illustration_hover])"> <a href="[node:url]"><img src="[node:field_custom_illustration]" /></a> </div> <?php endif; ?>

What we are doing here is saying if the hover field isn't empty then add a div with a background of the custom illustration hover field and a link to the node URL and display an image of the custom illustration.

One field I really recommend filling in on the Display Suite code fields is Limit field. If you use a lot of fields, DS ones or otherwise, they soon build up in your content type. So seeing as we only want to use this field in our Species content type and on our slider view mode we've got a value of species|slider, you can use * for selecting all which is handy.

Then back in our slider view mode we should find the new field, simply replacing the old one for this one and a few CSS tweaks to line up the background image with the image and a bit of opacity hover magic and it working like the old slider did but now the client is in control of the images.

[katelomax]

My new favourite demo site.

(Not really sure what my old favourite demo site was, but anyway...)

[nonprofit-design]

Display Suite allows site builders to customise how content is displayed. When I say content, I mean nodes, users and taxonomy pages as a basic example. At a lower level, you are modifying the display of an entity. All major pieces of content like nodes, users and taxonomy terms are simply entities.

[kkdev]

Drupal question: Giving content editors more power

Here's a longer question that doesn't fit into 140 characters. I've got a project with an emphasized requirement for content editors to be able to handle the day-to-day management of the site. Basically, they don't want the developers to be a bottleneck for things to change.

Writing content is a given, and Drupal has that covered, but it seems like they'll basically need Panels/Display Suite/Context (or a similar interface) to change some layout-based things. What is a good way to grant them access to these tools without overwhelming them? I guess I'm looking to give them some of the ease of use of Concrete5 without actually building the site in Concrete5 (which I haven't learned yet). At the same time, I don't want them to shoot themselves in the foot.

To give you something more concrete, let's just say the initial requirements are:

User-friendliness, e.g. understandable how to make changes

Upload pictures/videos/media

"Change backgrounds"

Administer forums

Of those, I think a bit of power to manage the layout is all they really need. But lots of in-context editing prompts would be good; I think the backend tends to scare people.