This tutorial will provide you the necessary steps in order to change the Background Image of the SItecore Admin Login Screen. Changing the background image for the admin login screen is a great way to personalize an experience for the content authors, provide agency or corporate branding, or provide additional information about the site (by embedding the information into the image).
Step 1: Create / Select a New Background Image
Create a new image to use as the login screen background image. To accommodate a variety of screen sizes, it is recommended the image is 2560x1600px in dimensions. Once you have obtained the image, add it to the project so that it will be deployed with the rest of the website’s assets.
Note: When the background image is presented on the screen, it is set via the following CSS rules:
Step 2: Create a Patch File
To set the new image, you need to create a new configuration patch file within the App_Config project folder. The patch file should contains the following code.
Step 3: Deploy and Test
With all files saved and added to the project, simply deploy the code and visit the login screen in order to verify everything is configured correctly.
For the last 5 years, I’ve been focusing a lot of my professional time around designing experiences around Sitecore. For the last 3 of those years, I’ve been doing a large amount of development in the platform as well. After that time, I still find the platform has much to learn and with every new release, another body’s worth of features and potential comes with it.
Sitecore, as a platform, is unlike any CMS platform I’ve worked with up to this point. There are competing platforms for an enterprise level CMS; however, with so much to offer and my primary languages of choice being .Net and Node, Sitecore is an amazing platform to work within. From a User Experience perspective, no other platform that I’ve used has the capabilities for personalization, analytics, and optimization built into it out of the box. In many ways, it’s an ideal platform for someone like myself who has experiences with Marketing Technologies, Design Research, and Development.
As I continue to work within the platform from the perspective of each of these 3 areas, I plan to document a variety of tutorials and strategies here. This is for my own reference; however, like any public blog – I also hope someone will discover such and find value from such as well.
It’s been a long while since I last blogged on the site. A lot has happened in my life and my career changed in order to focus more on the human side of technology. However, those aren’t excuses for the absence I have had from this blog. If I ever had an excuse was simply writer’s block as nothing has inspired me to write. But that’s changing. Old habits are returning and that means more blog posts and more content.
To start – my 4 main / current NPM packages have been updated in order to get them up to speed with Node v0.12 as well as to make them compatible with Browserify. I may add Bower support later but right now, it is what it is. Along with these changes, I updated the interface making a couple of them 2.0 releases. You can find more information about the packages at the links below.
In addition to updating those packages, I’m also resurrecting some old Node.js projects that I had worked on over the last 2 years and begin to add them to Github. Lastly, you can expect more Node.js and iOS development posts on here with a sprinkling of UX. I believe in the importance of transparency in learning and I can practice my development skills a lot easier than my User Experience skills.
Every once in a while, I come across an article about someone talking about how antiquated the floppy disk icon of Save has become. They talk about how many office documents of today would not have fit onto the 1.44mb capacity of a floppy disk and as new generations of computer users arrive onto the scene, many have never used a floppy disk. Obviously the icon needs redesigned these individuals discuss; however, I say it doesn’t need redesigned – the button itself needs to be removed altogether.
So it’s been a while since I’ve added any new content (nearly 6 months). Between the holidays, focusing a lot more at work, and also blogging for work I have been neglecting my personal brand and blog for too long. So what does that mean?
It’s October and that means many retailers are beginning to finalize their Holiday plans and queuing everything up for release in the next month or so. While some retailers have their Christmas and other holiday decorations up already, most e-commerce websites won’t be rolling that out for another month. It’s also around this time of year that I remember how terrible of an experience gifting digital downloads remains.
Back in April of 2012, I did a presentation at the Kansas City Developers Conference on tips and tricks to finding and landing your dream job. Having been through a number of interviews as both an interviewer as well as someone trying to get hired over the last handful of years, I have had the opportunity to see what things are important to both sides of the table. In the end, both parties need to make sure that the other side is right for them and it’s not just a one-way relationship.
One of the largest things that I have loved about working in Node.js is the ability to create utilities that work on both the server and within the browsers. Being able to create packages for NPM and then reuse them in both environments has lead to a lot of shared and unified code. However, the general experience involving installing a package and moving it to the client left a lot to be desired. Thankfully, NPM offers a possible solution through it’s use of scripts.
The more that I use Node.js, the more I enjoy it; however, there I have seen an issue in a couple of projects. In these projects, some modules import in a large number of other modules that reside in single directory. While it could be argued that the code could be refactored differently, scenarios exist where you may need to import in a number of modules that all exist in the same directory.
If you’ve worked on websites for any amount of time, there is a decent chance that you’ve encountered the need to validate credit card numbers at some point. While there are a lot of compliance and security guidelines for working with credit card numbers, these don’t reduce the need for ensuring the user entered a valid credit card number into the form. Some places will validate just length and ensure only numeric digits were provided; however, did you know there’s an algorithm that most credit cards are based on?