From 682b843503f2d382d04edc8c1a2db75e40c23da1 Mon Sep 17 00:00:00 2001 From: "Luke W. Johnston" Date: Mon, 21 Sep 2026 14:37:15 +0200 Subject: [PATCH] =?UTF-8?q?refactor:=20=F0=9F=93=9D=20clarify=20that=20WP?= =?UTF-8?q?=20protocol=20is=20made=20with=20template-website?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/protocol/index.qmd | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/docs/protocol/index.qmd b/docs/protocol/index.qmd index 9b4b6d0..a385821 100644 --- a/docs/protocol/index.qmd +++ b/docs/protocol/index.qmd @@ -15,7 +15,11 @@ process much easier and sometimes can be set up to be done automatically. These work package protocols are (generally) kept in stand-alone repositories, so that they can be directly built into a website and automatically uploaded to -Zenodo whenever changes are made. +Zenodo whenever changes are made. Generally, it's best to have someone from the +management group create the repository for the protocol, as its better to set it +up using the [Template Website](https://template-website.seedcase-project.org) +from [Seedcase](https://seedcase-project.org) that requires some admin settings +after creating the repository. These protocols are bigger and broader in scope, as they represent the overall activity within a work package. They also will have more people working on them, @@ -25,7 +29,8 @@ branch (and built onto the website) will already have been approved and is "publishable" in the current state. Sections within work package protocols may be more diverse compared to protocols -for research projects, which have a template to follow. +for research projects, which have a template protocol file included with +instructions and suggestions. ## Research project protocols @@ -76,7 +81,8 @@ graph TB pr("Create pull request
when protocol is
ready"):::yours review["Protocol review
and approval"]:::ours zenodo["Protocol uploaded
to Zenodo"]:::ours - branch --> write --> pr --> review --> zenodo + update["Update metadata
in 'dp-next.yml'"]:::ours + branch --> write --> pr --> review --> zenodo --> update classDef ours fill:#ADD8E6; classDef yours fill:#FFA07A;