Once you choose a font you can click to the “Type Tester” section to see how any specific words you type will look in your selected font. You can easily increase or decrease the font with the slider and you can also view how the font looks in various browsers on the “Browser Samples” tab as shown in the screenshot below.
Typekit uses “kits” to organize fonts for usage by designers. It’s really easy to create a new kit. Simply hover the kit section and click “Add New Kit”. As you can see from the screenshot below, I've created a kit for each site on which I use custom fonts. You can see how to add a new kit in the below screenshot.
Now that the "kit" is ready I need to add some fonts to it. Once you decide on a font you simply hover over the font and click “Add to Kit” and the font will be added to the kit for which you are currently viewing as denoted in the below image.
After you add a font to a kit you can go into the "kit editor" to further customize. Once you’re inside the kit editor you can customize various settings and styles that make the custom fonts appear on your site. You can simply add the CSS selectors that you’re using on your site & they will then render showing the custom font that you've just selected in Typekit. Notice in the below screenshot where I'm adding " .ANewSelector " class in Typekit's editor.
If you wanted to access specific weights & styles via your skin.css file you can click on the “Using weights & fonts in your CSS” option which will give you the below screen allowing you to copy the CSS necessary for your specific font & weight.
Now if you did click the “Copy CSS” option you would end up with some CSS that resembled the below:
font-family: "atrament-web",sans-serif; font-style: normal; font-weight: 400;
Once you click publish you will be ready to go. I should also mention that if you want to develop or test out styles locally you can also enter “localhost” in your kit editor settings and that will make your local sites work with the new custom fonts.
If you were concerned about how your styles would display on mobile devices you can click into the "Mobile Settings" section of the Typekit editor as seen in the below screenshot.
Now to make all of this active we need to click the big green “Publish” button at the bottom right hand corner of the kit editor screen which you can see in the below screenshot.
Then in my HTML Module I simply referenced the CSS classes that I specified earlier in the Typekit selectors area.
And that's all it takes to get everything lined up. You can see an example of the redesigned home page (running locally) using the custom font “Atrament web” that I selected earlier.
Typekit makes it extremely easy to use custom fonts in your site. If you’re a Creative Cloud member you should check it out. I hope this blog has been helpful to you with integrating custom fonts in your DotNetNuke sites.
In the past few years I’ve been getting into IOT. You may have seen tweets or blog about the Tech-Turkey project I’ve been working on or flame throwing pumpkins at Halloween. I’ve learned and used Arduinos, Raspberry Pi’s, and Particle Photons and Electrons. It has been fun to learn more and get into the connected world… the internet of things!
I’ve been keeping ServoCity in business and even recently worked to get a custom PCB created. Every step of the way I’ve been learning different things and realizing just how much more there is to learn. Recently I’ve started learning more about Splunk.
What is Splunk If you don’t already know what Splunk is, Splunk is a software company based in San Francisco that produces software for searching, monitoring, and analyzing machine generated big data via a web style interface. Splunk’s software helps organizations with operational intelligence, log management, application management, enterprise security and compliance.
Side note: In my first exploration into Splunk I wrote a blog about using Splunk with DNN that may interest you.
Particle & SplunkDNN is a web application, but what if I wanted to get data from an IOT device? That’s when we call on Particle. If you’re not familiar with Particle, it makes it really easy to bring real world objects online. Particle is one of my favorite IOT platforms. It makes awesome microcontrollers, provides a nice IDE, has awesome documentation, and a great community. Connecting to Particle’s cloud is straight forward and even southerners can do it! See my presentation at our user group on DNN & Particle.
If you’re not familiar with Splunk, it makes it really easy to pull in data (machine data) and make sense of it. I’m talking about parsing vast amounts of data, creating visualizations and/or alerts and making it simple to understand. Even southerners can use it too!
Both Particle and Splunk are industry leaders and have some really big names behind their companies and as clients of their companies.
So why not bring Particle & Splunk together?
Reading Temperature with ParticleTo use the awesomeness that both solutions bring us we’ll first need to read the temperature and post it to a webservice. Here again, Particle makes this easy. I used a basic temperature reader in a bread board layout for this experiment.
Then, in Particle’s IDE I used the basic tutorial level code to read an analog value and post it to a Particle cloud variable. Cloud variables are accessible via web services. That is, I can make a GET request and parse the JSON object to get the data. Epic.
Now we were cooking with oil! The next step was to get this data into Splunk.
Getting Particle’s RESTful Data Into SplunkGetting RESTful data into Splunk is really straightforward thanks to Splunk’s extensibility. Splunk has an extensions gallery that can be found on the Apps and Ad-Ons sections of the Splunk website. I tell you this because ultimately, I followed a blog by Damien Dallimore on getting REST data into Splunk which used a modular input extension and that was all it took. I simply completed the required fields in the Splunk REST Modular Input as shown below.
After clicking save, the data from my Particle temperature reader was showing up in Splunk!
Creating Dashboards from the Particle DataOnce data shows up in Splunk you can literally perform any search query you want on the data and create/configure dashboards, panels, reports, alerts and more. Splunk is very powerful in this regard and scale to infinity. However, for this scenario I just wanted log the temperature over time from one device, as well as the temperature’s highest, lowest, and average. Splunk, again, made this very simple.
After clicking on the “result” field I created some visualizations and voila! Out popped some neat dashboards showing all my data in a way that’s easy to understand.
If you are like me, you kind of want to see things in action. So for those of you like me who are visual learners, here’s a quick video of the solution in action.
An IOT Combination That’s Hard to Beat!As you can see, both solutions are awesome and the opportunities are endless. Consider the possibilities here… Particle is easy to deploy and post data to the net and Splunk can easily connect, suck in data, and bring instant insights. The more data you give to Splunk the more knowledge you’re going to have. Splunk can handle this at scale too… I mean massive scale. Why not connect thousands of devices and pump all the data into Splunk and tune it to your liking! I believe that’s what they refer to as operational intelligence 😊 Now my mind is spinning with possibilities. Is yours?
If you ever need to put some custom styles in the Telerik Rad Editor of DotNetNuke HTML module it can be a little frustrating if you don't know exactly where to put the files. It's actually a simple process. I cut a quick video walking through this process and wanted to post here in hopes of helping someone who may encounter this same issue.
Have you ever seen a small pixel in your Pulsar Thermal optic’s screen that you wish wouldn’t stick out like a sore thumb? If you fire your gun a lot these pixels-that-need-repair occasionally occur, but fear not, Pulsar has anticipated this and provided a way to resolve it. I had one on my screen for a few months before I investigated it and the good news is that it’s simple to correct!
A “defective pixel” is a pixel within your viewfinder or screen that is “degraded”, sticks out, and won’t go away even after your scope calibrates. I’ve owned a Pulsar Trail XP-50 for over 2 years and in this time, I’ve only had 2 defective pixels. Though, when it does happen, over time it will bother you enough to want to know how to fix it.
Here’s a screenshot of one of my defective pixels while in “White-Hot” mode
In this screenshot, the defective pixel may not seem like a big deal, but when you’re hunting and looking through the viewfinder it can become distracting to your eye over time, especially if it’s near the crosshairs. While hunting with the defective pixel shown in the screenshot above there were several times I panned the horizon and mistook the small white dot for being an animal that was a great distance out.
The first thing to do if you notice a defective pixel or something that doesn’t look correct in your viewfinder is to calibrate the optic. If you haven’t changed any settings on your scope then your Pulsar thermal optic will automatically calibrate every so often to ensure what you’re seeing is accurate, clear, and crisp. Calibrating the optic makes the clicking sound that you may have grown accustomed to hearing by now if you own a thermal optic.
These calibrations can be forced by pressing the power button in the Trail models. If my screen ever gets hazy or I notice something not sharp in the viewfinder I simply calibrate the scope. With all that said, the first thing to do if you notice a defective pixel is to force a calibration because generally that will fix it.
If calibrating the optic doesn’t resolve the issue then repair the defective pixel by going to one of the last menu options in the menu system, the “Defective Pixel Repair” option.
Once you choose this option it’s simple. The system presents you with a pixel selector and provides you with the ability to move the X & Y coordinates. This task feels very similar to sighting in the scope.
Just move the X & Y coordinates until you are right on top of the defective pixel. As you update the values for the X & Y coordinates the pixel selector will move across the screen as shown below. The pixel selector surrounded by the box is like the Picture-In-Picture feature and is a magnified (zoomed in) version of the pixel selector.
The goal is to move the defective pixel selector on top of (or as close as possible to being on top of) the defective pixel.
Once you have the defective pixel lined up you then need to hit the record button, yes, the record button. The system will repair the pixel and respond with an “OK” message.
Note: You can also use the remote control to do this as shown in this video by Michael Bennett
And that’s all there is to it! Note that depending on your unique situation, it may take repairing multiple pixels to get the screen back to the desired state. In one of the previous defective pixel scenarios, I had to repair 2 pixels before it was back clear, and the pixel was no longer bothering me.
I also made a quick video walking through this process. You can see the video below:
I hope you found this content helpful. If so, leave me a comment below.