Refine results
Status
Category
Technology
Confidence Level
  • In scope
    High

    The GI website will be a completely standalone WordPress install

    Section: Platform and technical architecture

    Assumption: Governance Intelligence will be built as a completely standalone WordPress site with no shared functionality or inherited logic from IR Impact. Any reuse will be limited to design patterns and intentionally selected approaches, not shared code, data, or behaviour.

    Agreed item: Confirm that the GI website will be a completely standalone WordPress install.

    • Correct

    Source: GI website scoping workshop notes (12 Jan, 10–12pm)

    No comments to show.
  • In scope
    High

    No application logic, automations, or functional code will be shared with, and continue to be shared with, the IR Impact site

    Section: Platform and technical architecture

    Assumption: Governance Intelligence will be built as a completely standalone WordPress site with no shared functionality or inherited logic from IR Impact. Any reuse will be limited to design patterns and intentionally selected approaches, not shared code, data, or behaviour.

    Agreed item: Confirm that no application logic, automations, or functional code will be shared with, and continue to be shared with, the IR Impact site.

    • Understood

    Source: GI website scoping workshop notes (12 Jan, 10–12pm)

    No comments to show.
  • In scope
    High

    There are no planned future dependencies where functionality added to one site is expected to affect or surface on the other

    Section: Platform and technical architecture

    Assumption: Governance Intelligence will be built as a completely standalone WordPress site with no shared functionality or inherited logic from IR Impact. Any reuse will be limited to design patterns and intentionally selected approaches, not shared code, data, or behaviour.

    Agreed item: Confirm that there are no planned future dependencies where functionality added to one site is expected to affect or surface on the other.

    • For events, sometimes the webinars have the same audiences across both GI and IR. This is more about content not code/functionality.
    • Discussion re canonical – shared content. This is only really events, but only occasionally. Alice suggests articles should be edited to be different for both sites. If duplicates, we need canonical links and a user front end message to say there is a duplicate.

    Source: GI website scoping workshop notes (12 Jan, 10–12pm)

    No comments to show.
Andy White, Freelance WordPress Developer London