Responsive background images are always an issue since they're only possible via CSS media queries. The very useful SRCSET attribute can't be used with background images. In this article, we attempt to create an automated way to handle such images in Umbraco in order to increase speed and preserve bandwidth in mobile viewports.
Wouldn't you like to have all dictionary items on a single table that you could paste inside a spreadsheet? Even if you wouldn't, your clients probably would.
A package I created some time ago which lets you include node names from MNTP lookups into your Examine index so you can return more accurate search results where needed. Didn't understand a word? Great! :) Just read the article and you'll get the idea.
In this post you'll learn how to use Image Cropper together with the SRCSET HTML attribute in order to generate mobile-friendly, responsive images for your site. The SRCSET attribute defines a different image for each viewport size and delegates the decision on what image to load to the browser.
A simple piece of code to take care of all those lonely, template-less documents which were in place BEFORE you remembered to assign a default template for their document type - yes, it happens when you open your back-end to the client for data entry before starting to develop the front end. And yes, client requests like that do happen.
DLL mode, AppData mode, or maybe something hybrid that will allow better source control integration, freedom of choice on deployment and more control? I'm exploring a new setup, see if it suits you too.
In this article we demonstrate how to create two dependent MultiNode TreePickers (MNTPs) - the second one using the first one's selection as its root node - using some pretty XPath.
Umbraco's MultiNode TreePicker (MNTP) data type has a couple of tokens (or, more precisely, "context-aware placeholders") that can be used in the XPath query defining the starting node for the picker and represent the current or parent node - but these tokens behave differently when creating a new node than when editing an already published node. In this post we will see why and how we can make MTNP behave consistently regardless of whether the node being edited is new or existing.