From f744ac67529c7cf05ac5bdf517a5a3fb1d535874 Mon Sep 17 00:00:00 2001 From: "Luke W. Johnston" Date: Mon, 8 Dec 2025 15:21:33 +0100 Subject: [PATCH 1/2] feat: :sparkles: add content to the landing page --- index.qmd | 37 +++++++++++++++++++++++++++++++------ 1 file changed, 31 insertions(+), 6 deletions(-) diff --git a/index.qmd b/index.qmd index ed436b8..c88e5dc 100644 --- a/index.qmd +++ b/index.qmd @@ -1,13 +1,38 @@ -# Welcome! +# Welcome! {.unnumbered} -Guidebook is about... +::: callout-caution +These documents are very much a work in progress and very much +incomplete. We work on it slowly and when we can. +::: + +This guidebook walks you through how we develop and release research +software, build data infrastructures, create content on websites, and +work together as a team. We've written this to collect best practices +and lessons learned as we've built products and worked as a team. + +We cover topics that range from what the contribution workflow looks +like, how we write code, how we ensure our products are secure and +reliable, how we collaborate and manage our work, and more. ## Who you are as the reader We've written these documents considering a few people in mind who we think will read the documents: -- **New contributors/team members**: ... -- **Research software/data engineers**: ... -- **Managers or leaders**: ... -- **Research or development operations personnel**: ... +- **New contributors/team members**: This is who we are primarily + writing for. If you are new to working with us on the Seedcase + Project, these documents are designed with you in mind. +- **Research software/data engineers**: If you work in another + organization or group, we write these documents to share our + practices with you. You can use this either as a guide or as a + reference to help you improve and learn how others work. +- **Managers or leaders**: If you are in a position where you have + control or power to influence how work is done and organised, these + documents can serve as inspiration for how to structure teams, + workflows, and practices to build products more effectively, + reliably, quickly, and securely. +- **Research or development operations personnel**: For those who are + responsible for maintaining infrastructure or operational aspects of + a research organisation, these documents can provide insights into + best practices for managing and deploying research software and data + systems in a way that hopefully reduces your workload and stress. From afa7eab5f16397c464386c384b9c1ccb4259331d Mon Sep 17 00:00:00 2001 From: "Luke W. Johnston" Date: Mon, 8 Dec 2025 16:43:55 +0100 Subject: [PATCH 2/2] fix: :pencil2: edits from review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Signe Kirk Brødbæk --- index.qmd | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/index.qmd b/index.qmd index c88e5dc..2ab00c3 100644 --- a/index.qmd +++ b/index.qmd @@ -5,13 +5,13 @@ These documents are very much a work in progress and very much incomplete. We work on it slowly and when we can. ::: -This guidebook walks you through how we develop and release research +This guidebook walks you through how we, in the [Seedcase Project](https://seedcase-project.org/), develop and release research software, build data infrastructures, create content on websites, and work together as a team. We've written this to collect best practices -and lessons learned as we've built products and worked as a team. +and lessons learned as we've built products as a team. -We cover topics that range from what the contribution workflow looks -like, how we write code, how we ensure our products are secure and +We cover topics that range from our contribution workflow, +how we write code, how we ensure our products are secure and reliable, how we collaborate and manage our work, and more. ## Who you are as the reader @@ -25,14 +25,14 @@ think will read the documents: - **Research software/data engineers**: If you work in another organization or group, we write these documents to share our practices with you. You can use this either as a guide or as a - reference to help you improve and learn how others work. + reference to help you improve and learn how we work. - **Managers or leaders**: If you are in a position where you have control or power to influence how work is done and organised, these documents can serve as inspiration for how to structure teams, workflows, and practices to build products more effectively, - reliably, quickly, and securely. + reliably, and securely. - **Research or development operations personnel**: For those who are responsible for maintaining infrastructure or operational aspects of a research organisation, these documents can provide insights into best practices for managing and deploying research software and data - systems in a way that hopefully reduces your workload and stress. + systems in an effective way that hopefully reduces your workload.