Skip to content

Nota Bene

Our Wordpress Toolbox - what's in it?

September 17, 2019

We were building with Wordpress in 2003 - site is still up and running http://morningforum.org/2003/09/01/fall-2003/.  We migrated from Multisite Wordpress to Drupal https://mrsec.org/highlights/2006/.  We built Multisite Wordpress for seamless integration with Drupal for Stanford Law School in 2011.  We built https://www.cardinalservice.org/ for seamless integration for Haas Center for Public service. 

Yes, we build with Wordpress and we do have Wordpress Toolbox - here it is.

Themes

  • AccessPress Parallax - simple parallax, sticky header
  • Polestar - stricktly business, sticky header, extended typography
  • Kale - minimalistic/artistic
  • Stanford Lagunita theme

Plugins

  • WP All Import Pro for integration with other sources
  • User Role Editor for managing permissions
  • The Events Calendar for events
  • Share Buttons by AddThis
  • MyFontsWebfontsKit   for custom fonts
  • Quick Page/Post Redirect Plugin for custom redirects
  • Search exclude for search optimization
  • Widget Context for custom placement of widgets
  • EasyChron for scheduling
  • WP Data Tables for advanced data

Site bulders - oh, no....

  • Divi
  • SiteOrigin
  • Elementor
  • Beaver Builder Plugin

Example websites

  • https://www.landapllc.com/ 
  • http://www.natashasilkart.com/ 
  • https://www.healinghealthcarenow.org/

DrupalCamp Colorado 2019

August 23, 2019

Great presentation with Martin Keereman on progress on feeds_migrate on Friday and contrib day on Saturday. 

https://2019.drupalcampcolorado.org/sessions/feeds-ui-migrate-engine-dream-migrations-and-imports.html

This year we celebrate 4 years since Drupal 8 was released. A one-click upgrade from older versions is one of its greatest features, thanks to the Migrate module being in core. While Migrate is powerful, it lacks a good UI. In contrib, we have Feeds for importing content. This module does have a UI usable for site builders, but it defines its own import framework. Wouldn’t it be great if the two frameworks could be combined together?

This would be a win-win solution for everyone, because:

  • Developers would only have to maintain one import framework;
  • Site builders could use the power of Migrate without having to write code;
  • Content managers gain the flexibility to import their content without the need to go through another round of development effort.
  • Two years ago, the maintainers of both import frameworks discussed the idea and that eventually resulted into the Feeds Migrate module being developed.

Today we will demo what has been completed, what still needs to be done and how everyone in the Drupal community benefits from this effort.

Presentation - https://drive.google.com/file/d/11Gwtctx70csBQ8BXTEewyeJ80DJ6Nnzk/view?usp=sharing
Module https://www.drupal.org/project/feeds_migrate

How to Know It's Time to Re-Vamp Your Website

June 7, 2019

If you're reading this, your company, department, or organization probably already has a website. That website probably works. But how do you know when it's time to make some changes?

As a design and development agency, we see a lot of different websites. Sites should be built, and maintained, in such a way as to fulfill the needs of your business or organization. The short answer to when it's time for a new website is when your old website is no longer fulfilling those business needs. But how do you know? The best way to know for sure is to do a site-wide audit of all of your content and features... (and if you're looking for someone to provide that service, do reach out to us!) However, short of doing a full audit, there are some key triggers that should make you start thinking about a re-vamp. 

  1. Your business model has changed. We recently had a long-time client approach us for a website re-vamp after only about a year. Naturally, we had a major question: Why? We wanted to know what wasn't working about their current site. They quickly told us that their current site was working great, except that they had completely changed the model of their organization and were moving away from published papers to more collaborative, on-going projects. That means their site wasn't working for them anymore. We quickly embarked on a new information architecture to highlight the new focus of their organization.
     
  2. Your audience has changed. Working with a lot of higher ed clients means that we're very familiar with the effect that a turnover in student body can have on audience motivations and needs. While of course college campuses have turn-over in their audience often, this applies to most organizations. Our audiences are all becoming more tech-savvy, and they're increasingly using devices other than traditional desktop computers. While responsive web design has now become de rigueur, we must all prepare for whatever is next. Maybe your audience is using screenless smart home devices to access their information, or maybe they're using a new operating system that you haven't optimized for. Google Analytics can offer you some of this information, and directly interacting with your constituents can let you know that your site is no longer serving your audience. Maybe the vehicle for the information is fine, but your new audience members want different resources and language than you've been using. 
     
  3. Your content editors are frustrated. We've seen this happen many times. You build a site that's perfectly optimized for content entry and everyone's happy. Flash forward a bit, and your content editors keep complaining about how "clunky" it is to enter content. Usually, this means content needs have changed. For instance, you've built a beautiful event content type optimized for a single-day event with multiple sessions. Now, your organization has grown and you hold multi-day events with different tracks for different attendees. Of course the content entry will feel clunky... You need to re-build the content type! If you have clear documentation and your content editors are increasingly frustrated with making updates, it's probably time to do some internal focus groups and consider a re-vamp.
     
  4. Your values have changed. Design and language reflect values. As organizations grow and change, sometimes a website will just stop "feeling right." This is likely a sign of value-clash. Maybe there are bright colors on your site that seem to clash with your mindful approach to education. Maybe long paragraphs of text are clashing with your organization's desire to feel approachable. This sort of re-vamp requires a lot of organizational soul-searching, but ultimately makes a big impact on how you appear to the world. 
     
  5. It's been 3 years. There's no hard and fast rule about how often you should update your website. How often do you re-organize your living room? Some people do it every spring like clock-work; some people are constantly moving things around and updating old furniture and decor; and some folks can live in a space for several years before even getting so much as a new throw pillow. Likewise, every organization has a different tolerance to design that feels old-fashioned and features that aren't optimized to current practices. We've found that most companies that haven't done any re-thinking of their site for 3 years are in the position of gaining quite a lot by totally re-imagining their entire site at that point. Your mileage may vary, but we've seen a lot of dusty websites :)

Getting ready for Amsterdam DrupalCon

June 6, 2019

10 in 2009 years ago I met Dries at OSCON - it was fun to find this picture whle I am getting ready for 2019 DrupalCon.