Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
nocodesissi opened this issue Dec 5, 2024 · 2 comments

Comments

@nocodesissi
Copy link

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?
@nocodesissi
Copy link
Author

Hi @sobuos 👋

While working on this task I realized the need for broader collaboration 🎁

We've already had a brief dialogue about this - as I'm practising my GitHub skills I would v much like to continue the dialogue here 😄

@sobuos
Copy link
Collaborator

sobuos commented Dec 19, 2024

Hi @nocodesissi,

That sounds like a great idea! I think we should look into this the next time I come physical to your workspace in January? As I have told you previously, I am not a fan of a complete migration and we will keep the project site for some purposes, but a lot of the content will definitely make sense to migrate 😄

Merry Christmas and Happy New Year to you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants