Editing Website refresh

==Background==
'Website refresh' is a project underway since early 2023.

The aims are twofold:
# To resolve existing navigation and maintenance issues with the current site, and
# Update structurally to better reflect development of the Wellbeing model and other changes in K'aute service delivery.

==Current state==
The current live site is at https://www.kautepasifika.co.nz/.

===Issues===
Issues that have been formally identified with this site are:
# Focus on video content is welcoming, but makes quick navigation hard or confusing
# Actual content is superficial
# Site is hard to update/change as necessary
# Site does not allow effective dissemination of news, or marketing info
# Site uses a CMS<ref>[https://umbraco.com/ Umbraco], also currently an unsupported version.</ref> which is not widely used and harder to support, extend and customise
# Service content is contract-focused and may not be optimal for our community seeking assistance
# Lack of ability to properly integrate other services that may be useful - for example, Careers/Job ads, ELC and enrolment, Primary care and MyIndici/enrolment, Healthpoint, etc.

==Formal design work==
K'aute have worked with [https://www.bettle.co.nz/ Bettle], in drafting a new website design. This has gone through several iterations, and the most recent draft for approval can be found [https://xd.adobe.com/view/2e55ed00-bd96-47ef-964e-7a0b9208f7a9-7b06/ here].

A stocktake/review session on 24/7/2024<ref>Attended by Ma, Raewyn, Roz, Shannon and Dianne.</ref> revealed that this draft hadn't yet been shared widely with stakeholders, and there was a feeling that it needed substantial rework.<ref>The team were happy with branding and design; criticism was mainly about layout, navigation and functionality.</ref>

This session ended with an agreement to capture the below key points, and to draft a test/wireframe for further review and feedback:

# Too much focus on contracts
# Wrong focus on 'facilities' vs services
# Does not reflect Wellbeing model and K'aute's future aspirations around service design and delivery
# Does not have an appropriate focus on "how can we help you?"
# Does not quickly guide people through to accessing relevant information or services
# Some key components missing (donation and careers functionality, as well as stories/case studies, for example).

==Test sites==
In response to above feedback session, K'aute proposed to develop basic test site versions internally, which can then be used for further feedback and review. The idea being that stakeholders can actually 'touch and feel' as opposed to working with draft design documents, and relying on external designers to move us forward.

Test site is running on a t2.micro instance in K'aute AWS account. Domain name and DNS managed via [https://aws.amazon.com/route53/ Route 53]. SSL managed via [https://certbot.eff.org/ Certbot].

===v0.1===
First revised draft of site available at v0.1 URL https://site.kautepasifika.com/.

Feedback session occurred on 11/11/2024.<ref>Attended by Raewyn, Longo, Dianne and Solomon.</ref> 

Feedback summary:
* Need 'Events' functionality, also permitting registration/signup (and possibly reminder notifications).
* Specific Fale booking capability (currently only available as an interim solution at https://kautepasifika.co.nz/services/village-fale/booking-the-fale/).
* News items should be tagged so users can refine what they see.<ref>This item incorporated an assumption that there would be a Marketing role in place to manage News and keep this maintained.</ref>
* 'Facilities' should be changed to show 'Our Village', and simply present the K'aute Village with relevant information - possibly graphically.
* ELC currently is a separate site, but this should be incorporated somehow into new version<ref>Specifically, to represent it as a part of K'aute and the Village, rather than a separate entity.</ref> The ELC 'micro-site' should include broader content commonly found on brochure sites, such as 'About us', 'Services', etc.
* Need a place for 'Case Studies' or success stories separately to 'New and events'.
* Need a process to initiate a complaint, or provide feedback.
* 'Contact' form has much lower friction for users than the current referral process. However, there may be a corresponding Reception workload in interpreting and actioning any requests. Need to consider this tension in more detail.
* Useful to have 'donation' capability, but this should not be prominent.
* 'Services' needs to be reconsidered:
** There should be minimal jargon
** Focus on practical ways we can help families, using plain language.
** Keep away from too much detail, and encourage users to get in touch.
** Consider a structure which follows a 'life course' model instead.

==References==