Portfolio Website

Public access launch date: 2014 (the project was launched much earlier internally for personal use).

This desktop web property consists of +-70 pages and +-30000 words. 🙂

 

Major Updates:

  • 20161: Migrated to SSL.
  • 2015Q1:
    • Migrated this WordPress website from Apache HTTPD to Nginx HTTPD.
    • Migrated this WordPress website to a new domain name.
    • Make an Android App for it and publish it in the Google Play Store.

 

Primary Objectives:

  • To get in contact with interested parties.
  • To make a snapshot of my skills and recent projects.

Other objectives:

  • To keep a record of interesting news.
  • To keep a record of the training history.
  • To author the list of subject areas that are relevant in the Online Marketing sector.

 

This website is primarily a content project with less focus on multimedia elements.

I decided to use a decent CMS (WordPress) because the website contains… a lot of content. If this website contained just a few pages, e.g. a simple landing page website, then I would have used a CSS Framework, such as Bootstrap, because you can produce very appealing designs with those frameworks (think of flat design, tiles, parallax, animations). But I assume that “Content Is King” for a portfolio website, right?

It is powered by the WordPress CMS Engine, a customized premium responsive WordPress theme and various WordPress plugins (some developed by me). The website adheres to the principles of Responsive Web Design.

The long listing of skills and training (ebooks, webinars, memberships, etc) are generated by a WordPress plugin that was custom made by me. The source data for this plugin is an Excel sheet. Maintaining this data within WordPress (by authoring the pages manually) would result in a maintenance nightmare hence I made this plugin.

SEO: I developed a custom WordPress plugin so that only the home page and some blog articles of this website should be indexed by the Search Engines (not the other pages such as the numerous skills pages and portfolio pages). But getting all pages indexed cannot be avoided at all times, nor denying access, especially when using the HTTPS secure protocol, even when declaring a robots.txt and the right HTTP Headers.
Try it yourself: click on the following Google Search link and see how many pages are listed in the SERPs. It should be just a few (note that the pages of the Google Analytics Spam Manager Tool are possibly listed [URL /ga-spam-manager/.*] but that is another project),
https://www.google.be/#q=site:rolf.huijbrechts.be/

 

Pleae have a look at the other projects in this portfolio for a good understanding of my skills.

Go to: