Skip to content

🚀 Migration of existing fleetoptimiser website content to os2.eu Domain #4

@sissekaliaswendyfan

Description

@sissekaliaswendyfan

Objective

To ensure consistent branding, improve accessibility, and enhance visibility of OS2fleetoptimiser, we propose creating a dedicated page on the os2.eu domain for the product. The new page should serve as a central hub for:

  1. Informing visitors about OS2fleetoptimiser's purpose, features, and benefits.
  2. Simplifying the onboarding process for new organizations.
  3. Promoting the product to encourage broader adoption across municipalities.

Currently, information about OS2fleetoptimiser is hosted on [Aarhus Municipality's domain](https://fleetoptimiser.aarhus.dk/). We aim to migrate this content to a new URL on the OS2 website: [os2fleetoptimiser | OS2 – Offentligt digitaliseringsfællesskab](https://www.os2.eu/os2fleetoptimiser) .

This migration involves:

  • Transferring all relevant content (text, media, and links).
  • Deciding on the structure of the new page to ensure clarity and usability.
  • Aligning the design with the OS2 website's overall visual identity.

Reasons for Migration

  1. Consistency: Hosting the product information on the os2.eu domain aligns OS2fleetoptimiser with other OS2 products.
  2. Accessibility: Centralizing information on a trusted, familiar domain enhances discoverability and improves user trust.
  3. Scalability: The OS2 domain is better suited to support future updates, cross-product marketing, and community engagement.
  4. Autonomy: Managing the content internally on the OS2 platform reduces dependencies on external domains.

Discussion Points

  1. Timeline: What is the optimal timeline for completing the migration?
  2. Content Review: Should the existing content be updated or revised before migration?
  3. Page Structure: What is the ideal structure for the new page? Should it include sub-pages for specific user groups or use cases?
  4. Technical Migration: What is the best approach for transferring content and ensuring no loss of functionality?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions