Welcome to the NZRT Wiki Podcast. Today we’re looking at Content Strategy.

If you work with NZRT’s website or digital content, understanding how everything fits together will save you a lot of time. That’s exactly what today’s episode covers — the thinking behind how NZRT creates, organises, and publishes content across its platforms.

Let’s start with the big picture. NZRT’s content strategy is built around five core ideas. First, content is organised around modules — specifically Dolibarr modules, which are the backbone of NZRT’s business operations. Think of it like each part of the business gets its own dedicated section of the website. Second, visual content plays a major role. You’ll find heavy use of tools like SmartSlider, along with video and imagery woven throughout the site. Third, the strategy goes beyond static pages — it actually pulls in live data from Dolibarr and displays it alongside content, keeping things current and relevant without manual updates every time something changes. Fourth, content is tailored based on who’s reading it. NZRT uses a role-based access approach, meaning the virtual agents — the AI roles that power NZRT’s operations — see content suited to their specific function. And fifth, everything is structured with search visibility in mind, so SEO is baked into the site architecture from the ground up.

Now let’s talk about what kinds of content actually live on the site, because there’s more variety than you might expect.

You’ve got your standard pages — these are the static module pages covering areas like Customer, Sales, Finance, and other core business functions. Then there are blog posts, which handle news, tutorials, and general updates. Video content is a significant part of the mix too — think product demos, how-to tutorials, and customer testimonials in video form. Speaking of testimonials, those are actually their own dedicated content type, separate from blog posts, and they focus specifically on customer success stories. Case studies work similarly — they get their own space for highlighting project outcomes. And finally, there are resources, which cover things like guides, whitepapers, and downloadable documents.

So you’ve got six distinct content types all working together: pages, blog posts, videos, testimonials, case studies, and resources. Each one serves a different purpose in the overall mix.

Now, how does all of this get published in an organised way? That’s where the content calendar comes in. Rather than publishing things whenever they happen to be ready, NZRT plans content on a structured schedule. Module pages get updated as the underlying Dolibarr data changes, so the site stays in sync with what’s actually happening in the business. Blog posts go out either weekly or monthly depending on the period. Video content publishes as it’s produced. And news or announcements go live as needed, so there’s built-in flexibility for time-sensitive information.

The important thing to understand is that this isn’t a generic website content plan — it’s directly tied to how NZRT runs as an organisation. The content structure mirrors the Dolibarr module structure, which means when something changes in the ERP system, there’s a clear update path on the website. The virtual agent roles are also factored into the strategy, so content reaches the right audience at the right level. And all of it ties back to NZRT’s broader business objectives.

If you’re ever figuring out where a piece of content belongs, it helps to ask yourself a few quick questions. Does it relate to a specific Dolibarr module? Then it likely belongs on a module page. Is it informational or educational? That points you toward a blog post or a resource document. Is it demonstrating real-world value — a project outcome or a satisfied client? That’s your case study or testimonial territory.

For anyone who wants to go deeper, the NZRT wiki has closely related notes on the NZRT Site Overview, the Virtual Agents System, and SmartSlider Templates — all of which connect directly to what we’ve covered today.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.

Welcome to the NZRT Wiki Podcast. Today we’re looking at 🎨 ColorChart Reference.

So let’s talk about how NZRT keeps its visual identity consistent across everything it builds and publishes. If you’ve ever wondered why certain pages, modules, or design elements feel like they belong together, the answer lives in the NZRT color chart. The master reference for all of this is a document called ColorChart dot PDF, sitting inside a folder called ColorChart and Images. That’s your go-to source whenever you need an exact color value.

Now, NZRT organizes its colors into a few distinct groups, and it’s worth understanding what each group is for. First, you have the primary brand color. This is the main color that represents NZRT as a whole — think of it as the anchor of everything visual. Then there’s a secondary accent color, which is used to complement the primary without overpowering it. After that, you’ve got a range of neutral grays. These handle the everyday stuff — body text, backgrounds, anything where you want to support the content rather than compete with it. And finally, there are module-specific colors, which is where things get really practical for day-to-day work.

Let’s walk through those module colors, because this is probably the part you’ll reference most often. Each module in Dolibarr has its own associated color to help users quickly orient themselves visually. Customer and Sales work uses blue. Finance and Accounting is green. HR Management is purple. Supplier and Purchase functions are orange. Product Management uses red. And the EDM module, which handles electronic document management, is represented by gray.

So how do you actually apply all of this in practice? There are four main usage guidelines to keep in mind. For primary elements — things like calls to action, links, and headers — you use the primary brand color. That’s what draws the eye and guides the user toward action. For module pages, you pick up the module-specific color and use it for page accents, giving users that instant visual cue about where they are. For text, neutral gray is your friend for body copy, while headings shift to black for maximum readability and contrast. And for backgrounds, you stick with white or light gray — this keeps things clean and easy to read without any visual noise competing with the content.

Why does all of this matter for NZRT specifically? Because the color chart isn’t just about making things look nice. It’s the glue that holds visual consistency together across three key areas. First, the NZRT WordPress site. Second, SmartSlider templates, which are used for dynamic visual content. And third, the theme customization layer that sits underneath everything. When all three of these are pulling from the same color definitions, you get a cohesive experience whether someone is reading a blog post, looking at a slideshow, or navigating the Dolibarr interface.

If you want to explore further after this, there are three related notes in the wiki worth checking out. Color Scheme and Branding gives you the broader branding context. RetroTube Theme covers the WordPress theme layer. And SmartSlider Templates shows you how these colors get applied in practice within the slider tool. Together with the ColorChart PDF, those four resources give you the full picture.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.

Welcome to the NZRT Wiki Podcast. Today we’re looking at Media Management.

If you work with content at NZRT, you are going to be touching media files constantly. Images, videos, documents — they all live in a managed system built around WordPress and a handful of carefully chosen plugins. Today we are going to walk you through how that system works, how files are organised, and what the rules are for different types of media.

Let’s start with the big picture. NZRT uses the WordPress media library as the central hub for uploaded files. On top of that, there are a few key plugins doing important work. Featured Image Plus handles the automatic cropping and sizing of featured images. SmartSlider Three is used for building and displaying hero sliders, including video sliders. There is also a YouTube importer that pulls in video content from YouTube. Together, these tools give you a solid, repeatable workflow for managing visual content across the site.

Now let’s talk about how media is organised, because structure matters here. Every piece of media belongs to a combination of three things. First, a module. The modules at NZRT are Customer, Sales, Finance, HR, Supplier, and EDM. So when you are uploading something, you should know which of those modules the content belongs to. Second, media is categorised by type. That means images, videos, or documents. And third, it is sorted by purpose — whether it is a hero image, a thumbnail, or a background image. Keeping those three dimensions in mind when you upload or label anything will save a lot of confusion later.

On to image sizing, because this is where a lot of people get tripped up. There are three sizes you need to know about. Featured images should be twelve hundred by eight hundred pixels. When you upload at that resolution, the Featured Image Plus plugin will automatically crop and position it correctly wherever it appears on the site. You do not need to manually crop — the plugin handles it for you. Thumbnails are three hundred by three hundred pixels and those are also auto-generated from your upload, so again, you do not need to produce those separately. The third size is the original full-size file. You should always keep this in the library as an archive copy, even if it is larger than what the site currently displays. That archive copy gives you flexibility if requirements change down the line.

Now let’s cover video, because NZRT supports a couple of different approaches depending on where the video lives. If the video is on YouTube, you embed it using the YouTube importer shortcode. You do not download and re-upload YouTube content — you link to it. That keeps file sizes down and lets YouTube handle the streaming. If you have a self-hosted video, that goes in as an MP4 file directly into the WordPress media library, just like any other upload. And if you are working with the hero sliders on the site, those are managed through SmartSlider Three, which can display both image and video content as part of its slider templates.

So where does the actual content live on the back end? There are a few places to know about. First, there is a folder called ColorChart and Images — this is where you will find the module category JPGs and the colour chart PDF that support NZRT’s visual brand standards. Second, there is a SmartSlider folder that holds the images and templates specifically used by the slider plugin. And third, everything that gets uploaded to the site lands in the WordPress media library itself. Those three locations together form the complete picture of where media assets are stored.

Zooming out to the bigger context — all of this media work exists to support NZRT’s content strategy. The goal is consistent visual branding across the site, with imagery that is appropriate for each module and video content that adds value to the pages where it appears. When you follow the organisation structure and the sizing rules, you are not just keeping things tidy — you are making sure the site performs well and looks consistent no matter which page a visitor lands on.

If you want to dig deeper into any of this, the related areas to look at are the Content Strategy documentation, the SmartSlider Templates reference, and the Featured Image Plus notes. Those three resources give you the detail behind the decisions covered in today’s episode.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.

Welcome to the NZRT Wiki Podcast. Today we’re looking at 🎪 SmartSlider Templates.

If you’ve spent any time on the NZRT WordPress sites, you’ve probably noticed the sliders — those eye-catching image and content carousels that sit on the home page, product pages, and beyond. Today we’re going to walk you through how NZRT manages those sliders consistently across the site using SmartSlider3 Pro templates.

Let’s start with what’s actually stored in the template library. NZRT keeps its SmartSlider templates in a dedicated folder, and inside that folder you’ll find three template files. The first is called ICS — this is the default slider template used across the site. The second is the Iteasel template, which offers an alternative design style. And the third is called Customer Sales Management, which is a module-specific template built for that particular area of the site. Each of these is saved as an ss3 file, which is just the native format SmartSlider3 uses to package up all the settings and layers of a slider template.

Now, once you have a template set up and a slider created from it, how do you actually put it on a page? That’s where shortcodes come in. A shortcode is a short piece of text you drop into a WordPress page or post that gets replaced with the full slider when the page loads. You can reference a slider in two ways: either by its numeric ID, or by referencing it by name — for example, using the name ICS instead of a number. Both approaches work, and the one you choose just depends on whether you’re working with a specific slider instance or referencing a named template directly.

Let’s talk about what each of these templates actually contains. Every SmartSlider template NZRT uses is built with a consistent set of six elements. First, slide layouts, which control the spacing and proportions of each slide. Second, a color scheme aligned to the specific module or page the slider is designed for. Third, typography settings covering font family, sizes, and weights so text looks consistent everywhere. Fourth, animations that define how slides transition from one to the next. Fifth, layer defaults, which set up the standard elements you’d expect on each slide — things like call-to-action buttons and text overlays. And sixth, responsive breakpoints that make sure everything looks right whether you’re on a mobile phone, a tablet, or a desktop screen. So when you use one of these templates, you’re getting all of that built in from the start — you’re not starting from scratch every time.

What if you need to tweak a template? The customization process is straightforward and takes just five steps. You open your WordPress admin panel and navigate to the SmartSlider3 menu. From there you select the template you want to edit. Inside the editor you can adjust layers — those are the individual content blocks on each slide — as well as animations and colors. When you’re happy with your changes, you save, and those updates flow through to anywhere that template is in use.

Now let’s look at where these sliders actually show up on the NZRT sites. You’ll find them in four main places. The home page uses sliders to showcase featured products and services — it’s often the first thing a visitor sees. Module pages use sliders to highlight and demonstrate what each module does. The blog uses a content carousel format, which is a great way to surface recent or featured posts in a visual way. And product pages use image gallery sliders so visitors can browse visuals without leaving the page. Each of these placements has its own purpose, and having a dedicated template for each context means the design always feels intentional and on-brand.

If you want to go deeper on any of this, the wiki points you to three related topics worth exploring. SmartSlider3 Pro covers the plugin itself in more detail. Color Scheme and Branding is worth reading alongside today’s notes because the template colors tie directly into the broader NZRT branding guidelines. And Content Strategy gives you the bigger picture context for how sliders fit into the overall content plan across the sites.

So to recap — NZRT keeps three slider templates on file, each targeting a different area of the business. You can drop them onto any page using a simple shortcode, either by ID or by name. Each template comes pre-loaded with layouts, colors, fonts, animations, button and text defaults, and responsive design rules. Customization happens right inside the SmartSlider3 editor in WordPress. And you’ll find these sliders running on the home page, module pages, blog, and product pages.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.