Editing Website refresh (section)

==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.