Ideas and insights
Ideas and insightsIdeas and insights
Ideas on content, experience, design and website planning. Start with a specific question and find a direction worth exploring.
Plan and confirm
Record suitability, sources and the next owner. Implementation follows the agreed project scope.
Related practical notes
Practical notes
Shared goals in a design project
Sales may want more enquiries, designers may want a distinctive brand, and developers may prioritise reliable maintenance. These are compatible aims, but they can compete for space when nobody agrees what a visitor should accomplish. Start by describing what the customer needs to understand and do after reading the page.
Practical notes
Design systems and page consistency
A design system is more than a set of colours and buttons. It helps information do a consistent job: a page title names the subject, section headings organise it, body copy explains it, and buttons identify the next action. Visitors still have to guess if those roles change between pages, even when every page uses the same palette.
Practical notes
Evaluate AI around a business problem
We need AI is not yet an actionable requirement. Identify the slow step, its input and the result you need. Turning approved product material into a page draft is a different task from inventing product benefits, with different review needs.
Related practical notes
Practical notes
Organise content around search needs
Collect questions from sales conversations, enquiry emails and project discussions. Customers may ask what you do, which businesses you serve, what they need to supply and how to discuss timing or budget. Keep their original wording before grouping similar questions into topics.
Practical notes
Plan human review for AI content
Generating a whole website and then looking for someone to check it encourages a rushed review. Decide beforehand which material is available, which statements need approval and who can publish the result. The draft can then be built around information that is possible to verify.
Practical notes
Using AI tools with sound judgement
Separate organising existing information from making a new business decision. Summarising notes, drafting alternatives and rephrasing approved descriptions have identifiable inputs. Product promises, pricing and delivery conditions require someone who understands the business to decide.
Related practical notes
AI-powered search is rewriting the rules – What does it mean for the creative and media industry?
Track ten real customer questions and record mentioned brands, cited sources and missing information. Repeat the same set instead of treating one generated answer as a stable ranking.
How to create a digital strategy roadmap
Separate current problems, near-term improvements and later experiments, with owners and evidence. Keep the rationale for roadmap changes traceable.
How to reduce your website’s carbon footprint
Compress images, remove unused scripts and reduce automatic video loading. Retest on the same device to ensure useful information remains available.
Shape the project
Practical notes
How to create a digital strategy roadmap
Separate current problems, near-term improvements and later experiments, with owners and evidence. Keep the rationale for roadmap changes traceable.
Practical notes
Adapting visual trends to a brand
Choose typography, colour or composition that suits the content and test readability. Maintain relationships between sections instead of piling up fashionable elements.
Practical notes
Demystifying UX and industry terminology
Explain journeys, wireframes and prototypes through problems, structure and interaction testing. Use one shared page example so the team does not work from conflicting definitions.
Practical notes
The 7 secret ingredients for digital project success
Agree goals, audience, scope, inputs, ownership, budget and acceptance before starting. Write each as a checkable statement instead of relying on verbal agreement.
Related practical notes
Practical notes
How to brief a digital agency
State the business, audience, pages, available material and decision-maker. Clarify budget and timing conditions and identify specific reference sections.
Practical notes
How to budget for a large website
Separate layouts, migration, integration, testing and maintenance. Add discovery for unknown requirements instead of promising a fixed scope without adequate inputs.
Practical notes
How to lay the right foundation for your digital asset
Establish models, routes, permissions and release recovery before adding personalisation or automation. Late foundational problems create broader rework.
Related practical notes
Practical notes
Building a martech stack
Map acquisition, content, email, analytics and customer records, including existing tools. Before adding a system, check export, synchronisation and maintenance ownership.
Practical notes
How to choose the right CMS
Use an article, product and approval as sample tasks. Have real editors author, preview and restore content and record assistance and maintenance costs.
Practical notes
Choosing a DXP: Kentico Xperience or Optimizely
Prototype the same content model, approval task and integration list on each platform. Separate licensing, implementation and operational costs rather than comparing feature-list length.
Practical notes
Headless v Traditional CMS - which one is right for you?
Compare the same multi-page editing task, including preview, reuse and publishing. Include additional frontend maintenance in the decision.
Planning headless CMS content
Download this editable planning headless cms content to record current work, open questions and owners. OXOAK examples can be adapted to the project.
Practical notes
Choosing between Kentico Xperience and Kontent.ai
Compare authoring, preview, approval and release with the same update. Include frontend implementation and integration ownership in the evaluation.
Related practical notes
Ideas on content, experience, design and website planning. Start with a specific question and find a direction worth exploring.
Practical notes
Shared goals in a design project
Sales may want more enquiries, designers may want a distinctive brand, and developers may prioritise reliable maintenance. These are compatible aims, but they can compete for space when nobody agrees what a visitor should accomplish. Start by describing what the customer needs to understand and do after reading the page.
Practical notes
Design systems and page consistency
A design system is more than a set of colours and buttons. It helps information do a consistent job: a page title names the subject, section headings organise it, body copy explains it, and buttons identify the next action. Visitors still have to guess if those roles change between pages, even when every page uses the same palette.
Practical notes
Evaluate AI around a business problem
We need AI is not yet an actionable requirement. Identify the slow step, its input and the result you need. Turning approved product material into a page draft is a different task from inventing product benefits, with different review needs.
Practical notes
Recording evidence in an AI-search project
Fix query samples, dates and sources and record content changes. Report visibility separately from business outcomes and avoid claims from a single answer.
Practical notes
Preserving search entry points during migration
Keep a URL mapping and verify important copy and images. Recheck redirect chains and broken links rather than sending every old address to one page.
Practical notes
Setting boundaries for experience analytics
Define questions before events and sampling. Mask sensitive form content and establish access and retention before enabling collection.
Practical notes
Validating specialist AI implementation capability
Use a real brief to demonstrate data retrieval, human approval and failure recovery without exposing unauthorised customer information.
Practical notes
Learning from a community activity
Document real needs, coordination and unresolved issues. Ground public summaries in verifiable actions instead of turning a single event into a long-term support claim.
Practical notes
Testing an agent-assisted marketing workflow
Test the full path from inputs to approved release on one campaign. Verify that missing information or insufficient permission produces a clear stop.
Practical notes
Reviewing workplace experience beyond rankings
Check responses to feedback, task clarity and workload. Record external rankings separately from internal improvement.
Practical notes
Comparing AI agents for marketing tasks
Use the same campaign brief to compare research, drafting and release preparation. Record provenance, editability and authorisation requirements alongside speed.
Practical notes
Designing venue information for search-led visits
Make event times, transport, ticket conditions and FAQs self-contained. Search visitors need current information and an authoritative confirmation route.
Practical notes
Keeping long-term collaboration healthy
Review workload, feedback channels and learning opportunities each quarter. Experience should bring clearer ownership and support, rather than an endless queue of emergency tasks.
Practical notes
Plan human review for AI content
Generating a whole website and then looking for someone to check it encourages a rushed review. Decide beforehand which material is available, which statements need approval and who can publish the result. The draft can then be built around information that is possible to verify.
Practical notes
Protecting recognition during a rebrand
Inventory changes to names, marks, domains and product terminology. Retain explanations and redirects where existing customers need continuity.
Practical notes
What Optimizely's Agent Platform actually does in 2026
Map retrieval, drafting, proposed execution and approved execution to permissions. Test failures and retain human approval and logs for consequential actions.
Practical notes
Every CMS is agentic now. So what does ‘agentic CMS’ even mean?
Authorise retrieval, generation, editing and release separately and keep unapproved work in draft. Trace inputs, decisions and changes for each execution.
Practical notes
Testing the llms.txt file: Does it help AI discover content?
Separate availability, retrieval and influence on answers. Use repeated observations and source checks rather than treating a file’s presence as guaranteed visibility.
Practical notes
Most marketing AI is all coach, no players
Assign an execution target, permission and acceptance result to each recommendation. Distinguish drafting, release and business records.
Practical notes
Your next slide deck might be a web page
Provide a direct URL, keyboard navigation and print styling. Keep content readable without motion and test offline, export and presentation needs separately.
Practical notes
Navigating the environmental challenges of AI
Inventory calls, generations, storage and repeated work and reduce unnecessary retries. State measurement methods instead of substituting efficiency claims for data.
Practical notes
Washington switched off the frontier. Did your business even notice?
Inventory dependent functions, alternatives and export paths. Provide clear errors and human support when an external API changes or closes.
Practical notes
Explaining the design of a venue website
Analyse event discovery, transport and venue services and explain supporting navigation. Exclude unsupported recognition and growth figures.
Practical notes
Explaining upgrade impact to technical decision-makers
Map runtime, hosting, extension and API changes with validation owners. Give unresolved compatibility a research plan rather than a promotional conclusion.
Practical notes
AI doesn’t change your strategy – it changes how you deliver it
Keep business goals and evaluation criteria explicit while using AI for drafting, classification or comparison. Preserve inputs and assign final output approval to an owner.
Practical notes
Assessing a CMS release for marketing work
Have editors test authoring, campaign preview and approval. Include training and migration rather than updating technical packages alone.
Practical notes
The A-Z of AI acronyms that marketers must know
Explain models, retrieval, agents and generation through inputs, outputs and authority. Define terms instead of hiding boundaries behind acronyms.
Practical notes
Designing digital services for older users
Support text resizing, label important actions clearly and allow correction after errors. Observe real tasks instead of treating age as a substitute for usability research.
Practical notes
Architecting for performance: Integrating Optimizely and Microsoft Dynamics 365 for the MCG
Separate page reads from background synchronisation. Add retries, deduplication and alerts, and provide an understandable fallback when the business system slows down.
Practical notes
Explaining provenance in a health-data product
Show sources, periods and missing-data notes and distinguish observations from inference. Avoid implying clinical validation that has not been conducted.
Practical notes
Evaluating a content platform as its scope grows
Separate established editorial workflows from new marketing capabilities. Check interfaces, permissions and commercial boundaries before judging whether consolidation reduces maintenance.
Practical notes
Explaining data use in an agricultural technology product
Explain sources, decisions and environmental limits. Separate product illustrations from field validation.
Practical notes
Designing work tools for neurodiverse users
Allow adjustable density, notifications and task breakdown with clear recovery. Validate with participants rather than assuming uniform preferences.
Practical notes
The realities of tracking brand visibility in AI search in 2026
Fix queries, region and sampling method and retain answers and sources. Use repeated observations rather than claiming stable ranking from one mention.
Practical notes
Making innovation projects comparable
Use problem, audience, prototype and evidence as consistent dimensions. Avoid letting promotional copy length determine presentation priority.
Practical notes
Reviewing responsible-business practices
Separate commitments, completed actions and supporting evidence. Describe practices without claiming certifications that have not been supplied.
Practical notes
Preparing nonprofit content for AI-assisted work
Clarify services, eligibility and sensitive-data boundaries and approve knowledge sources. Generated content cannot replace organisational responsibility for facts.
Practical notes
Planning validation for an Umbraco upgrade
Record content structure, extensions and deployment requirements, then test an isolated copy. Establish compatibility from documentation and project samples.
Practical notes
Connecting CMS AI features to editorial work
Benchmark one task such as classification, summaries or translation. Compare time saved with review and rework before increasing investment.
Practical notes
Choosing a DXP: Optimizely vs Sitecore
Use the same models, pages and approval tasks and record the workflow. Estimate platform costs, custom development and maintenance separately.
Practical notes
What is server-side tagging – and why do you need it?
Inventory fields, purposes and recipients entering and leaving the server. Moving collection does not automatically create consent or remove disclosure responsibilities.
Practical notes
Planning experiments for digital change
Compare manual and tool-assisted approaches on a low-risk workflow. Record quality, time and rework, and expand only when results are consistent.
Practical notes
Umbraco: From friendly CMS to serious DXP contender
Preserve core editing and add only needed analytics or automation. Record data, permissions and maintenance for each module.
Practical notes
Keeping reusable learning from an annual review
Capture decisions, recurring rework and effective collaboration. Turn the review into a checklist rather than a sequence of project covers.
Practical notes
AI agents: Embracing the new world order
Separate what an agent may read, recommend and execute. Payments, publishing and deletion need explicit authority and records; a correct answer is not permission to expand access.
Practical notes
Avoiding unconscious bias in marketing
Review representation, labels and default scenarios for narrow assumptions. Test copy against varied real use cases without inventing customer identities.
Practical notes
Designing task-based AI training
Cover input preparation, output review and permission boundaries. Require an independent task and an explanation of when to stop using the tool.
Practical notes
Organise content around search needs
Collect questions from sales conversations, enquiry emails and project discussions. Customers may ask what you do, which businesses you serve, what they need to supply and how to discuss timing or budget. Keep their original wording before grouping similar questions into topics.
Practical notes
Writing clear innovation submission requirements
State eligibility, deadlines, materials and review criteria. Update the action when submissions close rather than directing visitors to an unusable form.
Practical notes
Turning marketing-event ideas into a checklist
Record the problem, conditions and validation behind an idea and choose one pilot. Do not claim attendance or experiences that have not been verified.
Practical notes
Humans v AI: The future of website testing
Use tools for repeatable rule checks and people for real customer journeys. Record both kinds of evidence; a clean scan cannot establish content quality.
Practical notes
Strategy can’t survive alone in the wild
Translate goals into page, content or feature work with ownership and review dates. Revisit statements that do not lead to action.
Practical notes
Micro-retirements: What this emerging trend means for digital strategy
Agree handover material, replacement ownership and emergency boundaries. Centralise records so people on leave do not need to remain online for scattered details.
Practical notes
Assessing platform partner credentials
Assess partner status alongside delivery staff, verifiable work and support. Credentials do not replace a prototype of the actual requirements.
Practical notes
AI-powered search is rewriting the rules – What does it mean for the creative and media industry?
Track ten real customer questions and record mentioned brands, cited sources and missing information. Repeat the same set instead of treating one generated answer as a stable ranking.
Practical notes
Is Google's AI Overviews in search results the beginning of the end for web traffic?
Observe impressions, qualified visits and enquiries together. Record periods and page changes rather than assigning causes from one click trend.
Practical notes
How to choose the right CMS
Use an article, product and approval as sample tasks. Have real editors author, preview and restore content and record assistance and maintenance costs.
Practical notes
Using AI tools with sound judgement
Separate organising existing information from making a new business decision. Summarising notes, drafting alternatives and rephrasing approved descriptions have identifiable inputs. Product promises, pricing and delivery conditions require someone who understands the business to decide.
Practical notes
Confirming responsibilities before a SaaS launch
Assign ownership for publishing, deployment, domains, backups and integrations. Managed hosting does not remove the need to govern access and content.
Practical notes
Turning developer-event learning into reusable work
Create a minimal example, applicability notes and failure records for a new technique. Keep demonstration code isolated until it has been validated for a client project.
Practical notes
Will AI be the ruin of digital agencies?
Compare changes across preparation, design, development and testing. Generated pages still require content approval, functional validation and maintenance.
Practical notes
How to prioritise digital initiatives
Record user impact, effort and dependencies. Prioritise blocked core tasks and distinguish visual preferences from functional failures.
Practical notes
It's time to move to Xperience by Kentico
Inventory pages, media, forms, roles and integrations and mark retained or replaced elements. Validate editorial and customer tasks as well as imported data.
Practical notes
Optimizely's Opal AI: A bright spark or just more AI hype?
Test generation, revision and publication with your own material. Revalidate demonstration steps under project constraints, including failures and permissions.
Practical notes
Connecting service touchpoints and operations
Map enquiry, confirmation and delivery. Name the owner and handover material at each touchpoint, then check whether customers can see progress while waiting.
Practical notes
Is your website running on borrowed time?
Inventory unsupported components, unowned integrations and missing recovery procedures. Plan from concrete risks and costs rather than visual age alone.
Practical notes
Is Xperience by Kentico ready?
Map required capabilities to the proposed version and validate representative workflows. List missing functions explicitly instead of promising roadmap items as current delivery.
Practical notes
Using game mechanics in a climate-action product
Tie points to explainable actions and state data sources and calculation boundaries. Let users opt out of rankings without losing the core service.
Practical notes
Building trust in a companion interface
Explain generated responses and stored data, and provide pause and deletion controls. Avoid presenting simulated emotion as human understanding.
Practical notes
Explaining evidence boundaries in a medical-technology page
Separate functionality, suitability and validation evidence. Exclude unconfirmed clinical or regulatory conclusions and provide an accountable contact.
Practical notes
Reducing decision friction in online shopping
Place sizing, materials, delivery and returns near the selection controls. Preserve filters so shoppers understand why a product is included or excluded.
Practical notes
Evaluating AI against a clear purpose
Evaluate a tool by the problem it solves rather than output volume. Check facts and brand tone in public copy, and omissions and provenance in internal summaries.
Practical notes
Recording ongoing open-source contributions
Link issues, code and documentation contributions and state maintenance status. A single contribution is not a promise of continuing support.
Practical notes
A practical guide to writing AI-friendly content
Answer one clear question per page with context and evidence for key facts. Explain tables and images in text rather than hiding answers in decoration.
Practical notes
Explaining support for a social cause
State actions, participation and contact boundaries and verify partner permission. Do not imply professional assistance without the corresponding service and qualification.
Practical notes
How AI is revolutionising the CMS landscape
Separate retrieval, drafting, review and publication permissions. Faster generation still requires factual checks, duplicate review and restoration.
Practical notes
Six ways generative AI is reshaping our search experience
Compare summary, conversational, image and conventional search tasks. Maintain readable evidence and direct answers without relying on one presentation format.
Practical notes
Defining learning outcomes in developer education
Connect exercises to code, explanations and tests with feedback and revision. Verify institutional and accreditation details before publishing.
Practical notes
Building a useful trend review
Review what was and was not supported from the previous forecast before adding hypotheses. Use consistent measures so each review builds learning rather than merely changing terminology.
Practical notes
Planning sustainable work and breaks
Agree working hours, emergency boundaries and handovers. Coordinate individual needs and team responsibilities rather than judging commitment from online status.
Practical notes
Separating annual outcomes from plans
Link released pages and place unfinished work in the backlog. Publish supported figures and assessments rather than inventing results for a review.
Practical notes
The future of AI: open source and democratisation with Meta
Check licensing, compute, data handling and maintenance and compare identical tasks. Download availability does not mean unrestricted commercial use.
Practical notes
Explaining preparation for an innovation application
Provide a materials checklist and deadline time zone. Without event authority, offer preparation guidance rather than a false application process.
Practical notes
Thinking like a futurist: building a better tomorrow with AI
Explore options under different capability, cost and governance conditions and identify shared preparation. Scenarios are discussion tools, not inevitable forecasts.
Practical notes
Explaining the limits of robotic services
Distinguish automated responses, human support and urgent-help routes. Pair demonstrations with written limits so a human-like appearance does not imply unrestricted care capability.
Practical notes
Negativity bias: how it's affecting your job
Record what works, specific issues and impact. Separate recurring defects from isolated preferences so emotion does not dictate priorities.
Practical notes
Separating credentials from delivery responsibility
Confirm the contracting party, implementation scope and maintenance owners before checking credentials. State additional purchases even where external certification exists.
Practical notes
Will AI agents and Super AI replace humans as managers?
Use tools for organisation, reminders and suggestions while authorised people own personnel and consequential decisions. Record evidence and final decisions.
Practical notes
From the SXSW stage to the boardroom: Storytelling at work
Organise a story around the problem, decision and result, including unknowns. Verify data, quotations and personal accounts separately instead of filling gaps with drama.
Practical notes
Expressing business responsibility on a website
Separate goals, actions, evidence and unfinished work. State the scope of environmental or social measures and do not present intentions as achieved outcomes.
Practical notes
Writing a useful annual event summary
Organise notes by problem rather than speaker order, with references and experiment plans. Keep unvalidated ideas as observations.
Practical notes
Building a modern web app: Unveiling the magic behind the scenes
Let the interface handle input and feedback while the server owns authorisation, validation and persistence. Preserve recoverable input on failure and base success on the server result.
Practical notes
Xperience: Kentico's next-generation DXP
Test content, preview, approval and release on one campaign, then integrations and recovery. Separate roadmap capabilities from current delivery.
Practical notes
Umbraco Spring 2024 update
Maintain checks for representative content, roles and customer journeys. Record changes and recovery sources beyond installation success.
Practical notes
Google Analytics 4 tips and tricks
Verify event names, time zones and filters before interpreting page and enquiry relationships. Label test events separately from customer activity.
Practical notes
Will it fly? How to determine if there's a market for your digital product
Test the problem, alternatives and willingness through interviews and small prototypes. Distinguish interest from willingness to pay.
Practical notes
Making charity-event responsibilities clear
Name the organiser, eligibility, venue or dietary constraints and contact route. Close registration after the event while retaining information to prevent invalid applications.
Practical notes
How to fund digital products: Part 2 - Innovation budget planning
Fund problem validation, prototyping and implementation separately, each with exit criteria. Require evidence before committing the next stage.
Practical notes
How to fund digital products: Part 1 - Traditional budget planning
Separate ongoing maintenance from new capabilities and show dependencies and payment milestones. Preserve change approval so budgets correspond to accepted deliverables.
Practical notes
What belongs on a team culture page
Show collaboration agreements, feedback channels and working rhythms. Withhold unconfirmed benefits, offices and awards rather than turning culture copy into promises that cannot be fulfilled.
Practical notes
Will AI destroy the art of human communication?
Use tools for notes and drafts and review facts, tone and commitments before sending. Check permission for personal accounts and sensitive information.
Practical notes
Separating observation from second-hand event reports
Distinguish quotations, public material and direct observations. Focus on applicable methods without inventing conversations or impressions.
Practical notes
Understanding a workplace beyond rankings
Examine allocation, feedback and development support through verifiable practices. Rankings do not guarantee every individual’s experience.
Practical notes
Designing a demonstrable internship outcome
Use a bounded project for research, production and review. Obtain approval before showing outcomes and exclude private client information.
Practical notes
Evolving your SEO strategy for Google’s upcoming AI search experience
Review valuable pages for direct answers, supporting evidence and self-contained explanations. Avoid repeating keywords purely for machine visibility.
Practical notes
Foundations of personalisation
Model topic, audience and validity dates. Recommendation rules should be explainable and editors should be able to preview each audience variant.
Practical notes
Validating changes in design tools
Test editing, sharing and handover with existing components. Check format and permission compatibility in a copy before changing the team’s main library.
Practical notes
Turning a brand review into an action plan
Review content, experience and maintenance and select issues affecting customer tasks. Assign ownership and completion criteria rather than collecting commemorative images alone.
Practical notes
Source control on Umbraco Cloud – are you doing it right?
Separate source, configuration templates and secrets and review environment differences. Test whether the repository can actually reconstruct the project.
Practical notes
Knowledge handover in long client relationships
Maintain a glossary, account ownership and decision history. Verify a handover through a real update task rather than treating a shared folder as proof of continuity.
Practical notes
Keeping team wellbeing activities voluntary
Accommodate different abilities, schedules and privacy preferences. Avoid mandatory personal-data disclosure or promises about individual health outcomes.
Practical notes
Empowering enterprises with Sitecore XM Cloud
Inventory content models, publishing roles, previews and integrations. Validate editing and release with real pages instead of checking only that an API returns data.
Practical notes
Writing a respectful technology profile
Centre confirmed work and contribution and let the person choose identity disclosure. Do not add unverified nominations or awards.
Practical notes
Regulating the use of generative AI in the workplace
Specify permitted inputs, prohibited uses, reviewers and incident handling. Distinguish internal assistance from public release and provide concrete examples.
Practical notes
Should businesses be in the business of driving social change?
Explain concrete actions and boundaries relevant to the business. Do not speak for partners without permission or present opinions as completed outcomes.
Practical notes
Verifying annual partner achievements
Compile scope, releases and permissions and evidence recognition separately. Use methods rather than achievement announcements when records are unavailable.
Practical notes
Defining a community programme on a website
Separate intentions, scheduled work and completed actions. Keep eligibility and contacts current and avoid unconfirmed partner marks.
Practical notes
Tracking with consent: what you need to know about cookie pop-ups
Describe actual purposes and make choices affect scripts. Check network behaviour after refusal rather than only dismissing a banner.
Practical notes
Adapting visual trends to a brand
Choose typography, colour or composition that suits the content and test readability. Maintain relationships between sections instead of piling up fashionable elements.
Practical notes
Umbraco Cloud Australian data centre welcomes first commercial customer
Inventory data, audience and dependencies and record storage and processing locations. Hosting location alone does not describe every data path.
Practical notes
Separating predictions from delivery commitments
Keep forecasts in a watch list and confirmed needs in a delivery plan. Give uncertain initiatives an experiment budget and stop criteria rather than promising unavailable capabilities.
Practical notes
Grounding a team review in real work
Select documented collaboration, delivery and learning moments and include improvement needs. Do not rebrand another organisation’s history as your own.
Practical notes
Assessing emerging technology through design
Map entry, correction and exit before designing the spectacle. Emerging technology should not make a previously simple customer task harder to understand.
Practical notes
The age of too much information
Lead with the answer needed for the task and provide expandable detail and sources. Use search and clear headings rather than adding more choice overload.
Practical notes
Applying cross-disciplinary ideas to a website
Define the task and constraints and identify what an analogy explains. Validate a small prototype rather than copying an entire novel example.
Practical notes
Testing ideas after a technology event
Break an event example into its problem, conditions and outcome. Compare your content volume, budget and team constraints before designing a small experiment.
Practical notes
Explaining a nonprofit innovation pilot
State the problem, participants, pilot scope and evaluation. Distinguish fundraising, support intentions and completed implementation.
Practical notes
Social contracts give everyone a voice
Collect independent views before discussing trade-offs and record why alternatives were not adopted. Limited speaking time is not absence of input.
Practical notes
Resolving Rich Text in Astro and Next.js
Map headings, links, images and embeds to explicit renderers and restrict untrusted markup. Test missing data, long content and invalid links.
Practical notes
Next level content delivery with Optimizely Graph
Limit fields and depth and document caching and permissions. Test missing and cyclic relationships with representative content before release.
Practical notes
Putting the AI in Kontent.ai
Save generated copy as a draft with provenance and revision history. Assign approval for product specifications, prices and policy statements.
Practical notes
Design Fidelity & Prototyping
Use low-fidelity wireframes for information order and realistic content for reading and brand questions. Avoid polishing every shadow before the structure has been validated.
Practical notes
There's still a place for the all-in-one DXP
Compare system count, editorial workflows and integration ownership. Independent replacement brings flexibility but also requires clear boundaries for failures, identities and suppliers.
Practical notes
Making supportive communication part of daily work
Provide accessible help without requiring public personal disclosure. Clarify responses and avoid assigning unqualified colleagues professional counselling responsibilities.
Practical notes
Connecting a fundraising story to its purpose
Explain why the campaign exists, how support is used and how outcomes can be checked. Emotion cannot replace fund and participation rules.
Practical notes
Writing an accurate distributed-team introduction
Explain languages, time-zone coverage and contact arrangements. Do not infer addresses, headcount or employment relationships from photographs.
Practical notes
Keeping technical supplier relationships transparent
Explain platform, implementation and hosting responsibilities, costs and support routes. Make account ownership and data location clear.
Practical notes
Is the home page dead?
The homepage establishes identity and main routes; detail pages answer specific questions. Check that search visitors can understand the brand and next step without visiting home first.
Practical notes
Generative AI: How to prepare for the next evolution in organic search
Write service scope, contact routes and FAQs as self-contained explanations. Test answer completeness with real questions rather than adding markup alone.
Practical notes
Why conducting a content audit is essential
Record URL, topic, owner, validity and action. Distinguish duplicates, outdated material and unsupported claims rather than deciding from traffic alone.
Practical notes
Defining the purpose of event participation
Define learning questions, contacts and review methods. Separate planned attendance from completed activity and outcomes.
Practical notes
What are Design Tokens and why do you need to know about them?
Name colour, typography and spacing semantically and distinguish primitives from component roles. Check all usages and background variants after changes.
Practical notes
Respecting ownership in cultural content
Confirm who supplied names, images and accounts and what permissions apply. Invite relevant contributors to review community narratives.
Practical notes
Writing an accurate nonprofit design showcase
Analyse goals, structure and donation journeys and source genuine outcomes. Placeholder imagery is not proof of a client relationship or award.
Practical notes
Using content reuse to simplify publishing
Model shared facts once and preview affected pages after updates. Reuse reduces entry work but still requires channel-specific context checks.
Practical notes
Google Analytics 4 (GA4) vs Universal Analytics (UA): Your questions answered
Document differences between old and new metric definitions and observe them in parallel. Check collection conditions before combining trends.
Practical notes
All you need to know about online A/B testing in 2023
Predefine the hypothesis, primary measure, assignment and stopping rule. Avoid concurrent changes and record anomalies and missing data.
Practical notes
Headless v Traditional CMS - which one is right for you?
Compare the same multi-page editing task, including preview, reuse and publishing. Include additional frontend maintenance in the decision.
Practical notes
Your customers sell your product better than you do!
Verify permission, provenance and moderation rules and offer withdrawal. Distinguish customer comments from brand copy without inventing endorsements.
Practical notes
Using industry evaluations in platform selection
Check evaluation scope, criteria and period, then validate real tasks. Ranking does not replace budget, implementation and editorial assessment.
Practical notes
Optimizely as a headless CMS
Verify retrieval, preview, routing and release triggers with appropriate API boundaries. The frontend still needs independent design and validation.
Practical notes
Sell the story, not the product
Explain the problem, solution and suitability while keeping specifications and limits accessible. A story should lead to concrete decision information.
Practical notes
Designing an inclusive themed event
Allow participation across locations, schedules and communication preferences. Summaries should identify reusable changes rather than treating event photos as evidence of lasting practice.
Practical notes
Upgrading Kentico Xperience to Xperience by Kentico in 2023
Sample articles, products, media and multilingual pages for field and link mapping. Validate both editorial and customer journeys before release.
Practical notes
How to use Optimizely to personalise your website
Verify audience rules, defaults, previews and exit controls. Compare task outcomes rather than treating variant impressions as business improvement.
Practical notes
What happens to advertising when the cookie crumbles?
Inventory required events and purposes and minimise identifiers. Plan provenance, consent and retention rather than adding scripts to compensate for uncertainty.
Practical notes
How to harness AI without being a rocket scientist
Start with one internal task with clear data boundaries and compare results manually. Define permitted inputs, reviewers and stop conditions before expanding.
Practical notes
What is MACH? And what does it mean for the future of the CMS?
Assess responsibilities introduced by services, APIs, cloud operation and separation. Matching an acronym does not establish project fit.
Practical notes
What’s next after Google Optimize’s sunsetting?
Export hypotheses, variants, audiences and outcomes and remove obsolete scripts. Validate measurement definitions before comparing a replacement tool.
Practical notes
Me, myself and AI: How marketers can embrace an AI future
Define permitted inputs, reviewers and revision records. Separate research, drafts and release so tools cannot silently bypass approval.
Practical notes
Maintaining a useful technology glossary
Provide definitions, project examples, owners and dates. Retain mappings for obsolete names to prevent confusion between systems.
Practical notes
Why do we buy?
Separate needs, concerns and decision criteria and provide corresponding information. Discounts cannot replace suitability and service conditions.
Practical notes
Turning trend forecasts into testable hypotheses
Give each forecast an observable signal, such as a change in search acquisition or mobile enquiries. Revisit the signal before converting a prediction into a purchase commitment.
Practical notes
SEO copywriting: How to write for users and not their clicks
Use customer language naturally in headings and answers. Avoid repeating paragraphs or creating pages without distinct purposes solely for keywords.
Practical notes
Showing solution capability in a portfolio
Show goals, constraints, decisions and validation, stating connected systems. A clickable mockup is not an operating business system.
Practical notes
How to reduce your website’s carbon footprint
Compress images, remove unused scripts and reduce automatic video loading. Retest on the same device to ensure useful information remains available.
Practical notes
Finding relevance for FMCG brands online
Separate specifications, usage, suitability and purchase channels. Keep images consistent with packaging information and retire expired promotions.
Practical notes
Offsetting our carbon footprint in Bali
Preserve project provenance, periods and associated activity data. Describe direct resource reductions separately from other evidenced measures.
Practical notes
Optimizely multi-site best practices: a presentation by MVP Ynze Nunnink
Separate global fields, site overrides and permissions and test change propagation. Check all referencing sites before removing shared content.
Practical notes
UX v SEO: Friends or Foes?
Use headings for customer questions, direct answers and clear onward navigation. Avoid keyword-only pages and excessive simplification.
Practical notes
Making technical-community contributions verifiable
Link public writing, discussions or contributions and explain the individual’s role. Leave unsupported titles and awards unpublished.
Practical notes
A multi-brand strategy in Optimizely DXP
List shared components, brand-specific assets and publishing permissions. Check that brand switching does not accidentally transfer another brand’s cart, form draft or tracking identity.
Practical notes
Reporting progress in a charity challenge
Separate goals, completed activity and received support, with update dates. Preserve evidence and avoid counting the same contribution twice.
Practical notes
Turning a business mission into checkable actions
Connect principles to purchasing, content and collaboration rules and track implementation. Visuals and slogans alone do not establish social outcomes.
Practical notes
Mentoring the next wave of female developers
Connect learning goals to small real tasks with review criteria. Give actionable feedback and retain revisions and questions for the next session.
Practical notes
.NET Core 3.1 approaches end of life
Inventory dependencies, hosting and update ownership and test an isolated upgrade. Preserve recovery sources and validation rather than changing a version number alone.
Practical notes
Preparing records for a domain change
Record registrant ownership, renewal, DNS and email settings. Export configuration and name a rollback owner before changing the website domain.
Practical notes
AI-powered content recommendations with a headless CMS
Define taxonomy, visibility and exclusion rules before connecting recommendations. Similarity must not expose expired, paid or unpublished content.
Practical notes
Writing a grounded personal charity story
Use real experiences and verifiable progress, with permission for others’ accounts. Present unfinished goals as plans rather than achieved results.
Practical notes
The Xperience Adopter Program (XAP) has arrived
Define scope, support, exit and export, with permission before using production data. A successful trial does not validate every release requirement.
Practical notes
We rebuilt our website on the Jamstack (without changing CMS)
Separate retained models from changed frontend routes and test preview, release and caching. Retaining an API does not automatically preserve old URLs.
Practical notes
Designing a useful short internship
Separate observation, assisted work and independent output, with feedback at each stage. Interns should not carry sole responsibility for unreviewed public releases.
Practical notes
Umbraco cDXP targets enterprise market
Validate multisite, roles, approval, integration and maintenance separately. Enterprise labels do not replace real content and editor testing.
Practical notes
Umbraco introduces composable DXP offering
Define interfaces for content, search, analytics and identity and preserve export and replacement paths. Test failure isolation before adding more systems.
Practical notes
Choosing between Kentico Xperience and Kontent.ai
Compare authoring, preview, approval and release with the same update. Include frontend implementation and integration ownership in the evaluation.
Practical notes
Why you should upgrade to Optimizely CMS 12
Inventory extensions, APIs and deployment constraints and regress representative content and roles. Confirm current documentation rather than treating historical guidance as current advice.
Practical notes
Explaining a developer’s contribution in a portfolio
State owned modules, collaboration and disclosure boundaries. Separate project outcomes from personal contribution and omit unsupported credentials.
Practical notes
Xperience by Kentico technology highlights
Convert each capability into a task and failure case with evidence. Product descriptions inform questions; acceptance needs actual results.
Practical notes
How do you handle online forms with Kontent.ai?
Let the CMS provide page content while a protected endpoint validates and stores submissions. Keep administrative keys out of the frontend and preserve recoverable input.
Practical notes
Where is my data anyway? Data sovereignty challenges in a world of SaaS and Cloud
Inventory storage, backups, logs and support access across services and regions. Check contracts and settings rather than primary hosting location alone.
Practical notes
How to lay the right foundation for your digital asset
Establish models, routes, permissions and release recovery before adding personalisation or automation. Late foundational problems create broader rework.
Practical notes
How to budget for a large website
Separate layouts, migration, integration, testing and maintenance. Add discovery for unknown requirements instead of promising a fixed scope without adequate inputs.
Practical notes
Behavioural design – An NFP case study
Connect donation purpose, amount selection and confirmation. Defaults should aid understanding rather than exploiting unclear information to drive uninformed choices.
Practical notes
Four common risks to SEO during migrations – and how to mitigate them
Check URL mapping, indexing settings, lost content and internal links. Preserve a pre-migration inventory and verify destination pages individually rather than redirecting everything to the homepage.
Practical notes
The next generation of Xperience by Kentico is coming
Map content, forms, search and roles to the proposed system and record gaps. List unconnected modules instead of hiding feature loss behind an upgrade label.
Practical notes
What is a composable DXP?
Map data flows between content, search, analytics and identity with failure owners. Replaceability requires real export and recovery paths.
Practical notes
Hot tips for upgrading to Kentico Xperience 13
Back up content and configuration, inventory extensions and custom code, then test representative pages. Verify editing, search and forms after upgrading.
Practical notes
Explaining an innovation project
Separate the technology used from the problem and audience it serves. Show the working flow, input conditions and limitations instead of relying on technical labels.
Practical notes
Why you should be modelling content
Store repeated names, specifications and contact facts as shared fields with page context. Check references after updates to avoid stale values.
Practical notes
Our new social contract
Collect expectations and concerns, then document decisions, feedback and conflict handling. Keep the agreement revisable with a clear update process.
Practical notes
What you need to know about moving from Google’s Universal Analytics to GA4
Map events with triggers, parameters and tests. Avoid combining differently defined metrics into one trend during parallel reporting.
Practical notes
Building a martech stack
Map acquisition, content, email, analytics and customer records, including existing tools. Before adding a system, check export, synchronisation and maintenance ownership.
Practical notes
Accessibility design in practice
Specify focus states, error messages and image-description responsibilities beside components. Review a complete keyboard journey as well as static frames.
Practical notes
Maintaining accountability after a public commitment
Assign an owner, evidence and review date to each commitment. Keep unstarted work as planned rather than automatically reporting annual progress.
Practical notes
Is this digital agency right for me?
Compare communication, scope, maintenance ownership and verifiable examples. Use a small task to assess collaboration before expanding the engagement.
Practical notes
What is the role of the Product Owner in Agile?
Own prioritisation, trade-offs and acceptance while distinguishing implementation responsibilities. Share decisions to prevent verbal scope drift.
Practical notes
What is the point of buying an NFT?
Explain usage rights, transfer terms and costs. Scarcity does not replace value information and uncertain returns must not be guaranteed.
Practical notes
The 7 secret ingredients for digital project success
Agree goals, audience, scope, inputs, ownership, budget and acceptance before starting. Write each as a checkable statement instead of relying on verbal agreement.
Practical notes
Explaining the output of agile training
Describe audience, exercises and feedback, with certificates explained separately. Do not imply accreditation where it has not been established.
Practical notes
Six steps to a successful client-agency relationship
Agree inputs, consolidated feedback, decision ownership and acceptance. Explain scope-change impact and cost before implementation.
Practical notes
Defining outcomes in an education partnership
State questions, student responsibilities, deliverables and publication permissions. Keep unconfirmed partnerships as plans rather than public credentials.
Practical notes
Checking entry points before a domain change
Inventory old domains, email addresses, QR codes and external links. Verify email delivery separately: working website redirects do not establish that mail still works.
Practical notes
Tips for choosing a digital agency
Compare requirement understanding, samples, revision boundaries and maintenance. Use the same scope when comparing prices.
Practical notes
The fundamentals of designing for accessibility
Start with headings, links, buttons, inputs and errors. Check recognition and operation in default, focused and disabled states.
Practical notes
Choosing a DXP: Kentico Xperience or Sitecore
Compare editing, approval, multisite and integration using the same tasks. Platform names cannot replace project-fit validation.
Practical notes
CMS technology trends
Separate visual editing, structured content, automation and channel requirements. Establish what the team will actually use in the next year before considering expansion.
Practical notes
Explaining cloud capabilities beyond badges
Describe deployment, monitoring, recovery and access work. Without credentials, explain implementation practices rather than implying qualification through badges.
Practical notes
Choosing a DXP: Kentico Xperience or Optimizely
Prototype the same content model, approval task and integration list on each platform. Separate licensing, implementation and operational costs rather than comparing feature-list length.
Practical notes
What does .NET Core mean for me and my DXP?
Inventory runtime, extension and deployment compatibility. Distinguish upgrades, migrations and rebuilds rather than treating a runtime change as an automatic replacement without testing.
Practical notes
UX: The art and science of problem solving
Record goals, journeys and hesitation before proposing testable changes. Ground decisions in observation rather than internal taste alone.
Practical notes
Choosing a DXP: Kentico Xperience or Umbraco CMS
Have real editors create, preview and restore a page. Record where development assistance is needed and include everyday editorial work in the platform decision.
Practical notes
Reviewing the design of a product configurator
Check dependencies, unavailable-option explanations and the configuration summary. Customers should be able to revise choices without losing dimensions or contact details.
Practical notes
Demystifying UX and industry terminology
Explain journeys, wireframes and prototypes through problems, structure and interaction testing. Use one shared page example so the team does not work from conflicting definitions.
Practical notes
How should I upgrade Kentico Xperience?
Compare existing models, custom code and editorial pain points. Separate retained and rebuilt elements before estimating migration and testing.
Practical notes
Writing a grounded volunteering story
Confirm accounts and photo permissions with participants. Prioritise the organisation’s needs and exclude unsupported impact figures.
Practical notes
Umbraco releases v9
Validate runtime and extensions separately from model changes. Back up and test both workstreams independently to isolate failures.
Practical notes
Explaining participation in volunteer activities
State ownership, timing, tasks and safety arrangements with an option not to participate. Publish leave or benefit commitments only when confirmed.
Practical notes
Choosing maintenance support for an open CMS
Review upgrade history, extension management and recovery practices. Establish who will maintain the project and the response boundaries.
Practical notes
Documenting a website’s evolution
Record goals, changes and recovery sources for significant releases. Distinguish old screenshots from current capabilities.
Practical notes
Defining an expanded UX service
Separate research, structure, prototypes and testing into deliverables and explain client participation. Do not label a design discussion as completed research.
Practical notes
Reviewing a Jamstack implementation
Record build time, release failures, editorial updates and dynamic-endpoint issues separately. Base benefits on project evidence rather than borrowed industry figures.
Practical notes
How understanding human mental models drives better UX design
Ask participants to group content and explain labels, then compare with navigation. Internal departments may not match how customers understand services.
Practical notes
Explaining responsible-business principles
Explain purchasing, people, customer and environmental practices with confirmed facts. Separate principles from external certification.
Practical notes
Configuring Web Spotlight in Kontent for any scenario
Connect preview locations to the correct content items and separate preview from publishing permissions. Recheck mappings after layout changes.
Practical notes
Kontent Audit Log feature released
Record who changed which fields and when, with restricted log access. Restoration should create a new record rather than erasing evidence of mistakes.
Practical notes
Reviewing evidence of technical innovation
Ask for a problem definition, working prototype and validation records. Evaluate demonstration quality separately from dependable operation and avoid unverified business results.
Practical notes
Making a resource-management product traceable
Show provenance, update time and ownership for records and distinguish estimates from actuals. Summaries should link to inspectable detail.
Practical notes
Avoiding manipulative incentives in a behaviour-change product
Tie rewards to clear actions, with exit and reset controls. Let users manage reminders instead of relying on pressure from streak mechanics.
Practical notes
Explaining boundaries in a wellbeing product
Separate educational content, daily records and professional support routes. Explain data handling without unsupported therapeutic promises.
Practical notes
Building an evidence-based employer profile
Describe work practices, applications and feedback concretely. Verify certification validity rather than adopting a badge visible in an image.
Practical notes
Keeping community-support requests clear
Explain purpose, beneficiaries and fund handling and verify figures. Use distinct actions for participation, donations and volunteering.
Practical notes
Separating responsible-business aims from certification
Present working principles separately from verifiable certification. Without evidence, describe practices rather than adopting certification as an identity.
Practical notes
Striving for balance combats biases and creates opportunities
Define criteria before gathering feedback across use cases. Retain counterexamples and limits instead of treating one preference as universal.
Practical notes
How to create an ergonomic home office set-up
Review screen position, seating, lighting and breaks. Adjust to individual comfort and real tasks rather than prescribing one desk arrangement for everyone.
Practical notes
Keeping customer entry points resilient
Maintain direct URLs, email and social entry points alongside internal search. Avoid making information access depend on one external platform.
Practical notes
Using AI to power smart content recommendations for your headless CMS
Provide editorial pins, exclusions and a fallback list. When behavioural data is sparse, curated suggestions can be more useful than forcing personalised recommendations.
Practical notes
The power of user stories
State the role, task and reason and add success and failure conditions. Tie the story to an inspectable outcome.
Practical notes
A/B testing, personalisation and marketing automation with Umbraco 8
Fix one page and one primary measure before comparing two clearly different variants. Record the variants, audience rules and observation period together.
Practical notes
Agile ways of working with distributed teams
Write asynchronous updates as completed work, decisions needed and blockers. Use synchronous meetings for decisions rather than repeating status across time zones.
Practical notes
The QR code finally has its time to shine
Provide a clickable URL and purpose beside the code and ensure a mobile-friendly destination. Test before printing and maintain an appropriate post-event page.
Practical notes
Building a feedback loop in service partnerships
Keep the problem, resolution and confirmation for support requests. Review recurring issues and turn repetitive fixes into product or content improvements.
Practical notes
Packages in Umbraco 8
Inventory provenance, version, licensing, data access and removal impact. Test installation and recovery in a copy before release.
Practical notes
Designing an innovation submission form
Collect only eligibility and review information and provide a preparation checklist. Confirm submission and explain how corrections can be requested.
Practical notes
Maintaining continuity in remote collaboration
Keep decisions and progress in shared records and document changes after meetings. Absent members should be able to identify next steps without reconstructing chat history.
Practical notes
Is a headless CMS good or bad for SEO?
Check rendered content, distinct URLs and metadata. An architecture label does not determine search performance; inspect the delivered page.
Practical notes
Introducing a collaborator professionally
Confirm names, roles, work and photos with the person before publication. Focus on responsibilities rather than inventing experience or clients.
Practical notes
Helping people navigate health information
Separate information, service eligibility and contact routes, with ownership and dates. Promotional slogans cannot replace important conditions.
Practical notes
Mapping the impact of a major CMS change
Review editing, models, roles, APIs and deployment separately. Verify changes through representative tasks rather than release marketing alone.
Practical notes
Best practices for peak traffic
Separate static assets, dynamic endpoints and external dependencies in capacity planning. Test queueing, retry and duplicate handling for enquiries as well as homepage delivery.
Practical notes
GILT or GUILT – Localisation crimes
Separate language, dates, currency, reading direction and form rules. Review translated pages with real data for length changes and local meaning.
Practical notes
Designing participation in an online charity event
Place participation rules, fund use and closing dates near registration. Explain success and next steps on confirmation so people do not resubmit or miss essential updates.
Practical notes
Showing both the purpose and limits of innovation
Structure the introduction around users, flow, evidence and limitations. Exclude unsupported market results and recognition.
Practical notes
Recording evidence for environmental goals
Define scope and period before collecting activity data. Record reductions, substitutions and offsets separately without extending a limited result to an entire organisation.
Practical notes
Explaining results in a product visualiser
Label colours, materials and scenes clearly and distinguish illustrative results from actual products. Let customers retain a summary and ask follow-up questions.
Practical notes
Web Spotlight - visual page editing in Kontent (in less than a day)
Verify the selected content item, save and inspect the public result. Editable preview and successful publication are separate checks.
Practical notes
Designing fair participation in a charity challenge
Offer activity, communication or volunteer participation and optional public results. Keep support records separate from exercise data.
Practical notes
Explaining conditions in a decision-support tool
Expose inputs, alternatives and limitations and allow revision. Provide a professional consultation route where specialist judgement is needed.
Practical notes
Validating an accessibility tool
Observe varied users completing the same task before and after enabling a tool. Automated repair messages do not replace content and component checks.
Practical notes
Protecting contributors on a crowdsourced story platform
Separate public accounts, identity details and verification records. Explain permission and withdrawal before publication rather than relying on preselected consent.
Practical notes
Creating effective teams
Agree who decides, where feedback lives and what completion means. Record disagreements and evidence rather than interpreting silence as consensus.
Practical notes
Reducing uncertainty in appointment-based services
Show coverage, time options, confirmation and cancellation before booking. Distinguish a request from a confirmed appointment.
Practical notes
Using Zoom Breakout Rooms for training and workshops
Give groups consistent tasks, output formats and timing and a return route. Preserve unresolved disagreements when consolidating decisions.
Practical notes
Recording the outcome of a charity campaign
Keep participation, received funds and expenditure evidence separate. Check the reporting date and duplicates before publishing figures; registrations are not donations received.
Practical notes
Bringing security requirements into website scope
Inventory data, access roles, suppliers and processing flows, then have the responsible compliance team confirm applicable requirements. A general website brief cannot establish institutional compliance.
Practical notes
Reducing your carbon footprint in the home office
Inventory idle devices, repeated downloads and unnecessary video work. Measure environmental effects rather than presenting habits as verified reductions.
Practical notes
Why Design QA should not be an afterthought
Compare typography, spacing, images and states as components are implemented. Test mobile and long English copy separately before release.
Practical notes
Reducing misunderstandings across regions
State time zones in invitations and describe observable behaviour in feedback. Record holidays and language preferences early to avoid last-minute delivery disruption.
Practical notes
Working from anywhere
Check connectivity, devices, access and hours and keep shared records. Distributed work should not scatter sensitive files across unmanaged devices.
Practical notes
Why it’s time for the Jamstack to shine – the technology perspective
Test builds, releases, caching and dynamic requests separately. Architecture labels cannot guarantee unlimited free capacity.
Practical notes
The long, slow death of the WYSIWYG editor
Use rich text for narrative and distinct fields for prices, authors and reusable facts. Preserve final-page preview so structured editing remains understandable.
Practical notes
What is Kentico Xperience and where should I start?
List editorial, approval, marketing and integration tasks and identify the relevant product and version. Validate actual workflows rather than product descriptions alone.
Practical notes
Presenting a developer’s contribution
Show maintained components, technical explanations and verifiable contribution links. Do not add certifications or awards that have not been supplied and verified.
Practical notes
Xperience by Kentico - a new name for an established Digital Experience Platform
Map names, versions and APIs and confirm migration and licensing. Similar names do not establish direct replaceability.
Practical notes
Writing a time-bounded workplace notice
State dates, locations and accountable contacts and update links when rules change. A general notice does not replace professional safety arrangements.
Practical notes
Benefits of the Jamstack – from buzzword to business ready
Static delivery suits content that can be prepared ahead of time. Live pricing, stock and authentication need separate data paths; draw that boundary before choosing an architecture.
Practical notes
How to give and receive feedback
Identify the page, observed problem and task to improve. Agree on the issue before proposing a solution rather than making personal preference the sole requirement.
Practical notes
Analysing a financial-services design
Analyse services, eligibility, risk information and contact journeys. Exclude unverified credentials, relationships and recognition.
Practical notes
Showing content-platform implementation capability
Explain modelling, migration and editorial training with inspectable examples. Exclude unconfirmed partnership status from public descriptions.
Practical notes
Recognising isolation in remote work
Provide regular one-to-one check-ins and an asynchronous route for concerns. Focus on workload and access to help rather than time shown as online.
Practical notes
E-Commerce in Umbraco 8
Assign ownership for products, stock, pricing, orders and payments. Editorial access should not automatically grant refund authority or unrestricted customer-record access.
Practical notes
Sitecore Marketers Meetup: Taming Content
Inventory duplicates, expired facts and unowned material before merging, updating or archiving. Preserve URL relationships and revisions.
Practical notes
How we're maintaining morale with a remote workforce
Clarify tasks, workload and feedback and make help accessible. Social activities can support connection but cannot replace sound working arrangements.
Practical notes
Running remote workshops with distributed teams
Share questions and materials early for asynchronous participation. Preserve decisions and unresolved issues rather than whiteboard screenshots alone.
Practical notes
Maintaining project continuity through disruption
Confirm contacts, access, delivery order and urgent handling. Public updates should describe real impact and available routes without unsupported response promises.
Practical notes
Active Listening: The art of not ‘just hearing’
Restate the problem and constraints before proposing a solution. Translate “make it premium” into examples, audience expectations and disliked treatments to reduce subjective rework.
Practical notes
Sitecore personalisation – where to start
Choose a page with sufficient traffic and a clear task, then define segments and fallback content. Make the pilot independently reversible.
Practical notes
Organising a set of technical contributions
Organise contributions by problem, method and inspectable result. Preserve attribution and confirm names and disclosure with contributors.
Practical notes
What you need to know about personas
Describe needs from interviews, behaviour and tasks, separating observations from assumptions. Avoid deriving preferences from demographic labels alone.
Practical notes
Showing verifiable technical expertise
Use public documentation, code or implementation notes and state contribution boundaries. Do not transfer unverified personal recognition to OXOAK.
Practical notes
Attributing technical work clearly
Distinguish authors, reviewers and implementers and confirm names and titles. Let technical explanation carry the article rather than relying on awards.
Practical notes
The (free) content planning tools I can’t live without
Keep topics, owners, assets and status in one primary content register, then add a calendar if needed. Avoid conflicting copies of the same planning information.
Practical notes
Our social contract
Explain channels and confirmation at kickoff and refer to the agreement during disagreements. Review whether it still matches real work.
Practical notes
Explaining the purpose of a technical event
State the topic, audience, schedule and registration outcome, with a route for changes or cancellation. Use only confirmed partner marks.
Practical notes
Organising information across community activities
Record dates, purposes and participation separately before summarising outcomes. Use photos and participant details within permission boundaries.
Practical notes
Umbraco Heartcore launch
Test retrieval, media, previews and publication delay with missing-content states. Managed hosting does not replace frontend and search-content validation.
Practical notes
Reducing harm and misleading patterns in digital products
Review defaults, cancellation and disclosure for fairness. Make important conditions visible before a decision and avoid obstructive exit journeys.
Practical notes
Internationalisation and localisation tips
Test long headings, names, addresses, dates and errors with distinct language URLs. Recheck buttons and text inside images after translation.
Practical notes
Agile ways of working: Continuous improvement through retrospectives
Choose one recurring issue and record its trigger, a controllable change and an owner. Check whether the change happened before adding more improvement commitments.
Practical notes
Why data is your friend for email marketing
Clean duplicates, invalid addresses and records with unclear provenance before analysing campaign performance. Retain audience rules for each send to explain changes in engagement and unsubscribes.
Practical notes
Updating a team knowledge base after an event
Document changes relevant to current projects with examples and differences from previous practice. Date obsolete notes so new members do not follow outdated rules.
Practical notes
Social contracts: Working out how to work together
Define disagreement, escalation and revision processes. Return to the task and evidence rather than personal labels during conflict.
Practical notes
Serving content to IoT devices with a headless CMS
Reuse facts while adapting order and interaction to device tasks. Check length and confirmation separately for small-screen, voice and screenless output.
Practical notes
Distinguishing sponsorship from recognition
Distinguish organising, sponsoring, entering and winning and verify logo permission. Participation is not certification or a favourable judging outcome.
Practical notes
Maintaining documentation after a platform rename
Maintain a name mapping and check documentation, configuration and training links. A rebrand does not automatically establish model or API compatibility.
Practical notes
If technical debt is a disease, SXA is the cure
Define content, style and variant boundaries for reusable components. Check all usages after a change rather than maintaining conflicting page copies.
Practical notes
Controlling the cost of technology experiments
Set time, data and budget limits with one verifiable outcome. Record failure conditions so the same experiment is not repeated under a new name.
Practical notes
Sitecore personalisation from Day One
Complete default content and journeys before evidence-based segmentation. Retain a shared version when data is insufficient.
Practical notes
VR: gimmick or game changer?
Compare the task with a standard page before assessing equipment, discomfort and alternatives. Provide an exit and a non-immersive route.
Practical notes
Getting your head around headless content management
The content system owns structured material while the frontend owns presentation. Connect preview, release and cache invalidation into one tested workflow.
Practical notes
Preparing a headless CMS demonstration
Demonstrate authoring, API delivery and page updates with one model. State applicability and exclude real credentials and private content from examples.
Practical notes
Recording a planting activity with clear scope
Verify locations, counts, execution records and maintenance. Do not convert planting counts into unmeasured emissions claims.
Practical notes
Infographic: Australia’s Digital Carbon Footprint
Inventory image, video, font and third-party script sizes and load frequency. Repeat measurements under the same conditions instead of equating fewer files with verified emissions reductions.
Practical notes
Explaining an emerging food product
Prioritise ingredients, intended use, storage and verifiable information. Health or environmental claims need appropriate evidence and conditions.
Practical notes
Learning from website evolution
Identify navigation, content and customer entry points that still work in an older site. Preserve those journeys during visual changes and compare whether the new layout improves understanding.
Practical notes
Writing bounded environmental statements
State the subject, period and method, distinguishing reduction from offsetting. Do not present unverified results as certification conclusions.
Practical notes
Making project coaching useful
Set a learning goal around real work and schedule demonstration, practice and feedback. Turn coaching notes into a checklist for completing the next task independently.
Practical notes
The future of food delivery
Explain delivery area, time windows and exceptions before ordering. Distinguish order receipt, payment and fulfilment confirmations.
Practical notes
Making team experience reusable
Document recurring problems, resolutions and decision criteria. Emphasise transferable methods rather than unconfirmed tenure claims.
Practical notes
Web design trends for 2019: Part III – Interface smarts
Explain automatic suggestions and allow editing and undo. Users should not need to guess what the system did.
Practical notes
Will conversational interfaces sound the death knell for websites?
Use conversation to clarify intent, then provide readable pages and confirmations. Complex comparisons, conditions and submission results should be retainable outside the chat history.
Practical notes
7 digital marketing metrics every marketer should be measuring
Separate traffic, acquisition, engagement, enquiries, conversion, cost and retention. Select measures that will change the next decision rather than filling a dashboard.
Practical notes
Stop trying to be all things to all people
Answer a primary audience’s core question first and give secondary services distinct routes. The homepage should guide rather than contain everything.
Practical notes
Explaining a wearable product
Explain fit, compatible devices, battery conditions and support. Provide written specifications so customers can compare products without playing promotional media.
Practical notes
Web design trends for 2019: Part II – Bold visual styling
Choose a visual focus and a clear sequence for headings, copy and actions. Test strong contrast and large type with real content.
Practical notes
Will self-driving cars cause traffic armageddon?
Separate supported contexts, human takeover and exceptions and distinguish demonstrations from actual capability. Verify safety and regulatory conclusions independently.
Practical notes
7 tips for a successful digital roadmap
Give each initiative a user problem, owner, dependencies and acceptance criteria. Plan verifiable stages rather than committing every future idea at once.
Practical notes
Web design trends for 2019: Part I – Purposeful motion
Use motion to explain entry, change or feedback without blocking reading. Keep content and tasks available with reduced motion.
Practical notes
How to create a digital strategy roadmap
Separate current problems, near-term improvements and later experiments, with owners and evidence. Keep the rationale for roadmap changes traceable.
Practical notes
Evaluating a CMS release
Match capabilities to real editorial problems and record upgrade impact and recovery. New features alone do not establish an immediate need to upgrade.
Practical notes
Keeping themed fundraising records accurate
Separate registrations, pledges and received funds and show update dates. Obtain permission for stories and photographs.
Practical notes
Customising Episerver Forms
Verify field rules, record storage and notification delivery separately. Base confirmation on persistence and do not imply that saved data was lost when a notification fails.
Practical notes
Agile is not a process
Each iteration should produce something reviewable and use feedback to adjust priorities. More meetings without visible pages do not create a useful learning loop.
Practical notes
A tutorial on building a .NET Core website with Umbraco Headless
Isolate content retrieval and separate preview credentials from public read access. Define fallbacks for missing fields so an editorial update cannot unexpectedly break an entire page.
Practical notes
Episerver Personalization with persistent anonymous profiles
Separate temporary session preferences from persistent identifiers and provide a reset. Unidentified visitors should not receive content that depends on personal records.
Practical notes
Communicating a payroll policy clearly
Confirm eligibility, implementation and exceptions with the responsible team. Do not adopt another organisation’s benefits as your own employment promise.
Practical notes
Kentico now recommends the MVC development model - what does this mean?
Inventory coupling between templates, business logic and retrieval. Migrate independently testable modules and preserve old paths until replacements pass.
Practical notes
Improving work experience through regular feedback
Collect workload, collaboration barriers and development needs separately, then communicate actionable changes. Surveys do not replace follow-up.
Practical notes
Collecting useful feedback through an interactive survey
Ask one concept per question, use distinct options and allow comments. Deduplicate and describe the sample before treating participation as representative evidence.
Practical notes
Collecting privacy requirements for a website
Inventory fields, purposes, access roles and deletion routes, then obtain review of applicable requirements. Copying another website’s notice does not establish compliance.
Practical notes
Generating image metadata and SVG thumbnails with Episerver DXC Azure Blob storage
Store dimensions, format, alternative text and permissions, retaining originals when creating thumbnails. A successful upload does not establish suitability for every crop or device.
Practical notes
Handing over a completed rebrand
Collect marks, fonts, image permissions and page rules with editable sources. Confirm released pages and recovery material before closing temporary routes.
Practical notes
We built our new site using Kentico Cloud (and a few other microservices)
Record each service’s purpose, ownership and failure handling. Test the publication chain and keep accountability clear across providers.
Practical notes
Showing the practical value of education pathways
Keep eligibility, learning routes and application entry points on the main journey. Recognition may support the story but should not displace practical course information.
Practical notes
Rebrand Q&A
Explain the reason for change, continuing services, old entry points and contact. Help existing customers confirm continuity quickly.
Practical notes
Aligning pages and content during a brand update
Update navigation, titles, copy and contact together and check old URLs and image permissions. Replacing a logo does not make borrowed facts your own.
Practical notes
What's in a name?
Check headers, titles, mail, files and social profiles against one naming convention. Preserve explanations and URL mappings during a rename.
Practical notes
Translating technology buzzwords into project questions
For each term, state the problem, prerequisites and limitations. Keep concepts without a concrete task out of committed scope.
Practical notes
How to perform a website audit
Sample navigation, copy, images, forms, search and mobile tasks. A successful response establishes reachability, not correct content or behaviour.
Practical notes
Should we fear Artificial Intelligence?
Separate disclosure, factual error, authority and irreversible-action risks and assign controls. Match review intensity to the task.
Practical notes
Validating airport-site integrations through user tasks
Check update times and sources for flights, parking and transport, distinguishing live data from static information. Provide explicit fallbacks.
Practical notes
A future without screens
Split a voice task into short prompts, confirmation and a result. Provide a readable confirmation for money or data submissions instead of relying only on spoken memory.
Practical notes
Keeping recognition information accurate
Record provenance and publication dates and review current terminology. Rebranding a page must not transfer another organisation’s facts.
Practical notes
Why upgrading to Kentico 11 is a no-brainer
Compare maintenance, business needs and implementation cost. Record risks and mitigation when deferring an upgrade.
Practical notes
Why it’s time to change your thinking on Amazon’s arrival in Australia
Compare marketplace acquisition with owned content, customer relationships and service information. Retain direct communication routes despite platform changes.
Practical notes
The future of web is voice: Are you listening?
Use voice to find services and readable pages for confirmation and comparison. Allow correction and a switch to touch or keyboard.
Practical notes
7 reasons why content calendars fail
Check that each topic has an owner, required assets and a release date. Keep unconfirmed ideas in a backlog rather than filling every calendar cell with undeliverable work.
Practical notes
Reviewing a cloud content workflow after launch
Review editing time, release failures and reuse, separating platform behaviour from implementation decisions. Architecture labels alone do not explain every problem.
Practical notes
Using a consistent method to review designs
Record audience, primary task, visual strategy and interaction evidence for each project. Use consistent criteria instead of treating volume as proof of quality.
Practical notes
Protecting privacy in community-support stories
Verify permission and minimise identifying sensitive details. Focus on the organisation’s work rather than using personal hardship for promotion.
Practical notes
Assigning responsibilities in a distributed team
Organise work around owners and handovers instead of making location an information barrier. Keep asynchronous decision records across time zones.
Practical notes
Connecting brand history to current services
Keep history concise while making current services, work and contact prominent. Do not invent tenure to build a brand narrative.
Practical notes
Upgrading v rebuilding your Kentico website
List retained assets, rebuilt content, interface changes and tests. A clear problem inventory helps identify what should remain.
Practical notes
Making workplace activities optional and inclusive
Explain timing, noise and relevant allergy or space constraints, and provide an alternative working arrangement. Obtain permission before publishing participant photos.
Practical notes
Digital disruption – are you ready?
Start with a frequent process that has clear inputs and measurable outputs. Retain manual handling and exception routes while establishing reliable automation.
Practical notes
Email Marketing in Kentico - FAQs
Test audience selection, template rendering, trial sending and unsubscribe handling separately. API success does not establish inbox delivery, so report results precisely.
Practical notes
Kentico sneaky feature: diff your CI XML files with Git
Commit configuration separately from content and review removals and permission changes. Validate in isolation and exclude environment secrets from version control.
Practical notes
How to brief a digital agency
State the business, audience, pages, available material and decision-maker. Clarify budget and timing conditions and identify specific reference sections.
Practical notes
Contact Management in Kentico - FAQs
Establish where contacts come from, why they are retained and who can access them. Test deduplication, correction and deletion; interest in content is not automatically marketing permission.
Practical notes
Kentico 10 – Should you upgrade?
Compare support status, issues, extension compatibility and testing cost. Include maintenance ownership and rollback preparation in the decision.
Practical notes
What is Kentico Kontent? And why should I care?
Model reusable facts, page composition and media separately. Validate authoring and preview before expanding rather than putting everything into one rich-text field.
Practical notes
Reviewing a charity event without overstating it
Summarise actions, received support and follow-up, including unmet goals. Do not reuse previous photos or figures as new outcomes.
Practical notes
5 content-related ‘crimes’ against accessibility
Check heading order, image alternatives, link names, table headers and form labels. A link should explain its destination without relying on “click here”.
Practical notes
Why UX is not optional
Define audience tasks and current difficulties at kickoff and test journeys early. Scale research to the budget without omitting the problem definition.
Practical notes
Debunking the myths of remote work
Compare delivery quality, waiting time and clarity rather than using office attendance as the only measure. Identify work that suits asynchronous communication and reduce unnecessary meetings.
Practical notes
Checking a regional business page before release
Confirm scope, contact hours and the operating entity. State remote communication where no physical location exists instead of publishing an example address.
Practical notes
Presenting design work beyond trophies
Show the user problem, key design decisions and interaction views. Recognition needs verifiable names and dates; use design analysis when that evidence is unavailable.
Practical notes
Balancing expressive and usable interactive content
Distinguish story chapters from primary actions. Essential information and contact routes should remain available when animation is reduced or video skipped.
Practical notes
Are you ready for website personalisation?
Confirm sufficient content, explainable segmentation and a measurement plan. If every segment receives effectively the same material, improve the base content before adding personalisation.
Practical notes
Dealing with 404s in your Kentico Event Log
Group failures by path, referrer and frequency. Distinguish broken content links from scanners and historical assets, and avoid returning a success page for every missing URL.
Practical notes
Kentico Request Filtering Module
Define allowed paths, methods and sizes with meaningful failure states. Verify against real forms to avoid blocking legitimate submissions.
Practical notes
5 personalised websites that prove you don’t have to be Amazon to do it
Start by adapting content to a business type that visitors explicitly select. Offer a reset and avoid silently guessing personal identities.
Practical notes
Is your website a bad customer servant?
Check pricing context, service conditions, FAQs and contact feedback. Missing self-service information often becomes repetitive support work.
Practical notes
Upgrading to Kentico 9
Inventory extensions, custom fields and interfaces and test essential capabilities. Include adaptation and regression in upgrade estimates.
Practical notes
Evolution of the Digital Marketer
Inventory research, content, channel and analysis skills separately. Tools may change while goal definition and outcome assessment still need accountable owners.
Practical notes
Evaluating digital marketing trends
Give a new channel one audience, one content sample and an end date. Preserve the learning when it produces no useful visits or enquiries instead of extending the trial indefinitely.
Practical notes
Turning conference notes into project tasks
Record applicability, validation requirements and an owner for each learning. Keep unverified demonstrations in research rather than client commitments.
Practical notes
Keeping a themed charity campaign clear
Pair a creative headline with practical participation details, including the beneficiary and submission method. A shareable slogan should not replace campaign rules.
Practical notes
Connecting design recognition with user value
Show design decisions and their validation methods. When recognition lacks evidence, focus on experience analysis rather than promotional claims.
Practical notes
Speeding up Kentico Websites with Rackspace CDN and Origin Pull
Test origin fetches, cache hits, updates and invalidation separately. Do not apply static caching rules indiscriminately to private or user-specific responses.
Practical notes
How not to be shy on stage: Fixing a Kentico 'Gotcha'
Inspect dependencies, processing order and errors in a copy. Check partial application before retrying to avoid duplicates or overwriting newer content.
Practical notes
Showing evidence of technical delivery capability
Show verifiable scope, testing records and maintenance practices. Publish partner levels or audit conclusions only with supporting evidence.
Practical notes
Kentico Website Speed Optimisation Basics
Separate response time, database work, rendering and asset weight. Change one major factor at a time and compare under consistent conditions.
Practical notes
Kentico Event Log Digest
Group by severity and recurrence and link back to original records. Highlight actionable exceptions rather than forwarding every event.
Practical notes
Dynamic robots.txt files in Kentico
Separate production, preview and test environments and inspect the file actually returned. robots.txt is not access control; private information still needs server-side authorisation.
Practical notes
Presenting design choices in a housing website
Organise by layout, location, budget context and enquiry, with conditions for illustrations. Exclude unsupported awards and sales claims.
Practical notes
Publishing project recognition accurately
Verify project, year, category and issuing body and preserve evidence. Present the design without recognition claims when those details are unconfirmed.
Practical notes
Team Development + Continuous Integration in Kentico
Separate shared models, environment configuration and content data. Add deployment checks and prevent unapproved development data from overwriting live records.
Practical notes
Writing a useful technical-lead profile
Explain decisions owned, review responsibilities and collaboration, with approved work or public references. Do not substitute unverified titles for concrete capability.
Practical notes
Top Level Domain / .Melbourne | .Sydney
Compare memorability, audience and renewal ownership. Plan email, redirects and name protection alongside the domain choice.
Practical notes
Xero & Salesforce API Integration for CGU Insurance
Define authoritative data, field mapping and deduplication with retry and traceability. Avoid storing full sensitive records in logs.
Practical notes
Updating website information after a location change
Update contact pages, maps, footers and external listings, with dates for old-address notices. Use confirmed operational details.
Practical notes
Responsive Images Best Practice
Provide sizes appropriate to display width and reserve aspect ratio. Enlarging a small source cannot create real detail; retain its clarity limits.
Practical notes
Evaluating a digital experience
Assess comprehension, task completion, visual consistency and error recovery separately. Attractive screenshots cover only part of the evidence; retain the interaction journey as well.
Practical notes
Documenting maintenance for an older Kentico site
Inventory versions, extensions, custom modules and deployment dependencies, with known issues and recovery steps. Revalidate upgrades rather than relying solely on historical experience.
Practical notes
Connecting retail experiments with customer insight
Form hypotheses for filtering, product detail and enquiries and observe real difficulties. Keep results tied to their test conditions.
Practical notes
Accessibility Best Practice in Responsive Design
Check reading order, focus order and menu names on narrow screens and at zoom. Provide touch and keyboard access for information otherwise exposed only on hover.
Practical notes
Designing Navigation for Responsive Websites
Prioritise primary tasks and place secondary categories in expandable groups. Mobile navigation should show the current page and support keyboard closing with focus returned to its trigger.
Practical notes
Why is context important in Responsive Design?
Compare tasks on the move, on slower connections and at a desktop. Prioritise essential information and load heavier interaction when needed.
Practical notes
How Much Does a Responsive Web Design Cost?
Estimate distinct layouts, content entry, device adaptation and functional testing separately. Repeated-layout pages differ from independently designed pages.
Practical notes
Planning an anniversary website update
Verify dates, historical image permissions and current service information. Keep primary navigation and contact routes available so a commemorative feature does not obstruct everyday tasks.
Practical notes
Benefits of Responsive Design
Compare the same enquiry task on phone, tablet and desktop. Record missing information, steps and recovery, rather than checking only whether columns stack.
Practical notes
What is Responsive Design?
Test headings, forms and images across widths and recompose mobile reading order. Narrowing a layout must not remove content or controls.
Practical notes
Mobile Strategy Options
Assess offline use, notifications, device needs and frequency. Browsing and enquiry services do not automatically justify an installation barrier.
Practical notes
Browser Support - Mission Impossible?
Agree browser and device combinations from audience needs, including acceptable functional and visual differences. Verify real tasks rather than recording browser names alone.
Practical notes
Counting delivered projects responsibly
Define projects, versions and maintenance updates and remove duplicates. Preserve evidence and do not count template inventory as completed client work.
Practical notes
Making a student idea submission understandable
Provide sample materials, evaluation criteria and feedback timing, including ownership terms. Avoid collecting sensitive information unrelated to selection.
Practical notes
Amazon Cloudfront vs Cachefly in Australia - CDN Comparison
Compare the same regions, file sizes, cache states and sampling periods. Report cold-cache and cache-hit responses separately instead of blending them into one average.
Practical notes
Explaining the value of a content product
Explain the audience problem, information structure and maintenance model. Financial or growth figures need evidence; otherwise discuss observable product qualities.
Practical notes
Making a public report readable and traceable
Provide a summary, contents and version date with sources for important conclusions. Label file format and size and keep download actions relevant.
Practical notes
Connecting maintenance with sustainability goals
Reduce unused assets, repeated requests and idle environments, then record repeatable measurements. State scope instead of equating bug fixes with emissions reductions.
Practical notes
A practical website year-in-review
List released content, broken journeys and unresolved requests. Separate output counts from improvements to customer tasks, and prioritise the latter in the next planning cycle.
Practical notes
Keeping a milestone page useful
Verify dates and historical material and retain current service and contact links. Mark closed activities rather than accepting invalid submissions.
Practical notes
Tips for recycling old computer equipment
Back up needed data and sign out before following device-specific erasure procedures. Record the handover and use an appropriate disposal route.
No matching results
Try another keyword or reset the filters.