How can we help?


DNN Evoq Training Services

Since 2004, i2Integration has designed, implemented and supported over 700 DNN websites worldwide. In that time, we have trained hundreds of organizations on the administration of DNN.


Whether our clients need basic admin training on the day-to-day content management of DNN, or advanced training including module and theme development as well as server maintenance, our staff of DNN experts are available when you need us.


Onsite or Remote DNN Training


i2Integration can provide either on-site training at your facility, train remotely via web conferencing, or utilize our on-site facility with capacity for up 100 attendees, along with web conference on our fiber network.

DNN Evoq Training Topics


Here’s a list of training topics typically covered:

  • DNN structure (theme, pane, module, container)
  • Admin modes
  • Page creation and management
  • Module placement and management
  • Theme management
  • Security management (users, roles, permissions)
  • Content administration
    • Core DNN modules
      • HTML, documents, links, images, anchors, video
      • Style sheet explanation
    • Add-on Modules
      • Third-party module training
    • Short code
      • Content coding within off-the-shelf theme
  • Search Engine Optimization (SEO)
    • Page level
    • Content level
  • Site administration
    • Site settings
    • File management
    • Page management
    • Site log
    • Event viewer
    • Recycle bin
  • Advanced
    • New module installation
    • Modifying theme (skin), including pane creation and modification
    • Editing CSS
    • Server maintenance and support
    • New portal creation
    • DNS


Need DNN Evoq Training?


Call us at 517.371.3931

Email us at



Front-end, Back-end and Why It Matters

You need a web development company for your upcoming project. So who do you pick? A critical question to ask is: do you need a front-end developer, a back-end developer, or both? Matching the right company to the right need can make all the difference between your project’s success or failure.


First, what the heck is a front-end and back-end developer?


A front-end developer deals with what the user sees. We’re talking

  • Website design
  • User interface design and experience
  • Mobile responsiveness
  • Design coding, including HTML, CSS stylesheets, Javascript, JQuery, etc.



This is everything to do with branding, look-and-feel, consistency and flow. You know: warm and fuzzy.


Then there’s the back-end developer. They come into play when the website “has to do something,” such as

  • Integrate with your CRM or an internal system (inventory, member database, etc.)
  • Establish single sign-on
  • Register, sell, create, process
  • Do custom reporting
  • Capture, push or pull data
  • Mobile app development


This is what we call the “heavy lifting” part of web development. Hardcore geek stuff.


Some website projects need both skill sets, of course. Others need emphasis on only one. For instance, if you’re looking at a refresh of your brand and design, finding a web development company that is weighted toward front-end development will yield better results, whereas that same company might struggle and fail if the project requires complex back-end programming.


Just like in medicine, things have become pretty specialized when it comes to web development -- and for good reason, as the fields of expertise and rate of technology change have become increasingly complex for any one firm. For that reason, some developers today aren’t afraid to partner with others in order to fill in where they are less experienced or staffed.


A successful project all comes down to choosing the right developer, or group of developers. Asking where their specialties are more focused (front-end vs. back-end) will allow you to make a far more informed decision… ultimately saving you time and the green stuff. Not to mention creating a much stronger product in the end.



Client Analytics: The Next Big Thing

If your organization is like most, you’ve probably got all these individual components you work with in a given day, clicking back and forth like a mouse-wielding ninja: your website, your client or member database (or both), your email marketing provider, and so on. And you wish there was a way to tie all that data together to get an accurate picture of the true engagement of your clients / members. Instead, you know only that you had X number of views on your website and that X number of people opened your last email newsletter, but none of that is tied to your client database. 


Cue the parting clouds and choir music. i2Integration is building tools to be able to tie all that together. Client analytics: This is going to be “a thing.”


Let’s say your association has an upcoming event. You create a registration page for the website and a Constant Contact campaign to promote it. By implementing these new tools, here are some things you could find out: that associate-level members opened the email, clicked on the link to the website but did not register, but affiliate-level members from Florida opened the email, clicked to the site and did register. Or that a majority of premiere-level members started the registration process but didn’t finish. Maybe affiliate members require a different email campaign? Maybe associate members would rather register by phone? This allows you, in real time, to analyze the data and make informed decisions in the future. And as you capture this data, you establish a level of engagement and track it over time. Wouldn’t that be nice to know when dues time rolls around?


None of this is “out-of-the-box” right now, because everyone is running a different combination of systems, which means it requires some customization via coding. 


Before you ask, no, this won’t require a second mortgage. But when it comes to saving you in more accurate segmented marketing, eliminating false starts, redundancies, errors and inefficiencies created by moving data from one medium to another, it will pay for itself very quickly.


Ten years ago, nobody knew what a content management system was. Now everyone does, and nearly everyone has one. In a matter of years, every website will be doing Client Analytics as a matter of course.


Want to know more? Just ask!




Four Ways to Trim Your Website Redesign Cost

Reducing costs shouldn’t mean sacrificing quality. And when it comes to web redesign, there are reasonable compromises that can be made in order to get what you need and keep the project within budget.


  1. Go with a template design. What used to be one of the major expenses in a website redesign was the actual design, because lo’ those many years ago, every website was created from scratch. Now there are thousands of templates available that you can leverage and with only minimal changes, can make them look completely your own. The nice thing also, is that most themes already have mobile-responsiveness and UI/UX goodies baked into them. Going with a pre-designed theme won’t completely eliminate design, but it will definitely reduce the time needed in coding the architecture of the design.

  3. Migrate your own content. One of the major time-sinks in a site redesign is moving content from the old site to the new or placing new content. This isn’t usually a difficult and technical task, but just extremely time consuming. We see anywhere from half an hour to 45 minutes per page to clean and move content. With a little bit of training, this task could easily be done in-house by your staff and potentially save hundreds of hours in cost.

  5. Reduce custom development. As soon as you want to build anything custom, the ol’ cost-o-meter starts spinning. Is there a way to leverage something that’s already out there? And if what’s out there can’t do everything you need it to do, is there one that is open source -- meaning you get access to the original code -- , one that could be modified without having to build from scratch? One question to ask your developer when they tell you “This may be custom” is, “Is there something already out there we can modify?”

  7. Think of your redesign as a sprint, not a stroll. If you keep the project within a tight timeline and have all your ducks in a row before the redesign begins, costs can be kept to a minimum. If, for whatever reasons, your schedule is more loose than it could be or you don’t have all your content ready, the timeline can drag out. In a lot of cases, drawing a redesign out over a longer period of time only draws out more costs. Making the timeline aggressive can keep costs in line.



RFPs: Why they suck and don’t work.

Our company responds to anywhere in the neighborhood of 20 to 30 RFPs a year, and we’ve been in business more than 20 years. That’s a lot of RFPs. It’s also a lot of time contemplating their effectiveness. Or their lack thereof. 


The inherent problem with RFPs is that they force the organization that doesn’t have the expertise to do the work themselves to write the specifications for the project. In application and web development, that involves a lot of technology experience from people whose business isn’t technology. It’s the equivalent of a patient arriving at a hospital and saying, “I need brain surgery. Here’s how I want you to do it.” 


Based on that, three not-so-good things happen:

  1. The customer ends up asking for something that may or may not be the right fit
  2. The vendor must respond to the specs of the RFP whether or not it’s the right fit
  3. The customer may not be getting a realistic quote


In addition, there are probably key details that will be missed in the bid and those could affect the price. So even the comfort of having a fixed price RFP is a sort of myth in itself. Worse, some companies exploit that and low-ball the bid, knowing there will be significant overages later on.


In our experience, RFPs are bad for the client, bad for the vendor and bad for the project.


But there is hope. And a good solution. Here’s a scenario using an alternative approach to the RFP:


Say you need your website redesigned and you’ve found 4 developers that might fit the need. Instead of writing an RFP, have them submit an expanded Request For Information (RFI). You say to those vendors, “Here are the goals of the project, here is what we want to achieve (more web traffic, convert visits to sales, etc etc).” Then, ask the vendors for the standard credentials (number of employees, how long they have been in business, similar clients, etc).


But here’s where the expanded RFI blows the RFP out of the proverbial water: Ask the vendors, “Knowing our goals and looking at what we are doing now, and based on your experience, what are your recommendations? What are your observations? What are your ideas? And based on similar projects you have done, what were the costs for those projects?"


With this approach, the customer gets the vendors’ recommendations based on their expertise rather than a regurgitation of your specs. Also, you get insight into their thought processes and thoroughness, as well as an estimate of the cost of a similar project.


Now, here’s the big closer: once you’ve chosen the vendor who most closely matches your needs, together you then build the final specs for the project and from that, develop a firm, final quotation. This is the vendor who will guide you through the pitfalls, and can save you costs, save you time and save you a lot of the headaches that are endemic to the web development RFP world. You get what you want and what you need.



Newsletter Sign-Up

This isn't your grandpa's newsletter. You won't find fluff. Or news about who won the golf tournament. No, in our newsletter you'll find meaty information that will help you run your business better. Click here to sign up.