{
  "savedAt": "2026-06-03T05:03:25.882Z",
  "receivedAt": "2026-06-03T05:11:23.714562+00:00",
  "source": "sitemap-builder-questionnaire",
  "questionnaireId": "starter-update-questionnaire-v1",
  "questionnaireTitle": "IGNITE Starter Sitemap Builder Update Questionnaire",
  "responses": {
    "starterVersionName": "",
    "sourceCatalogueDate": "",
    "reviewOwner": "sylvain",
    "targetUse": "",
    "mustNotAssume": "Don't assume grouping or categorisation. the naming is mostly to help clients know what they can add. e.g. even though the footer is a footer element, we call it a section as it is added within the main page context, and not an inner component or something.",
    "recommendedComponents": "It will depend on the site. We try to create the components useful for every site, but we couldn't say some should be preferred",
    "discouragedComponents": "modal components and form components. Those are specific to some use cases",
    "componentPurposeCorrections": "",
    "componentAvoidWhen": "",
    "preferredSectionOrder": "always Hero first, unless it's a more custom page like a blog listing. Then for home or a landing-style page, we often go with Section / Intro Text, otherwise Section / Text Content is usefull to introduce the page. after that it depends on the page. Section / Next Pages is always the last section before the footer, though often we'll integrate it into the footer component. Section / CTA is usually close to, if not at the end.",
    "globalVariantRules": "Not that i can think of. the names depend on the context of the component a bit",
    "heroVariants": "Always primary on the home page. Inner landing-style or gateway pages will often use it too. The rest, excluding /blog or /news use secondary.",
    "ctaVariants": "Whether an image is present or not would be more based on the content. If the content feel like it lends itself to an image, we often add it. Image position will depend more on the page context - if the previous section has a right image, the cta should have a left image",
    "twoColumnVariants": "Should alternate image left or right down the page, accounting for similar components that also have the left/right option. Image bottom is a full width image, good for a large image/video to break up the page.",
    "otherVariantCorrections": "Will depend on the variant, but usually the default will be fine, unless some context is inferred from the variant name that says otherwise",
    "variantsNeedingHumanReview": "We'll have to monitor this as we go",
    "pageSlotRules": "the page slot defines the sections that a client can shuffle around, add to, remove, etc. Everything outside of that is fixed in place. that's why the hero goes above, and something like section / next pages would usually go below, if used.",
    "slotChildRules": "Sometimes we define this as a slot-accepts attribute on the slot itself. I don't think we catalogued these, but that would be a good start. on the next questionnaire though, let's go over this section by section",
    "nestedSlotLimits": "Cards - min 3, FAQs - min 3, max 5 in most cases. Tabs - min 2 max 5",
    "slotWarnings": "any combination is techincally possible and most should be avoided, we'll need to nail this down as we go. Most often slots should be left empty by default though",
    "requiredProps": "Headings are pretty much required when present. Most other props are configured to hide the element when the prop is empty. so e.g. if an eyebrow is left empty, the prop won't show. So if the section should not have an eyebrow, we'd need to override the default text with no text.",
    "optionalPropsToOmitWhenBlank": "don't quite understand the question but see previous",
    "linkRules": "Don't understand the question. We should link to relevant pages based on the content where appropriat, or use the external link features when needed",
    "richTextRules": "most of the time rich text will just be a plain paragraph. we usually use rich text when the client should be able to add links or easily make the text bold or whatever.",
    "imageAssetRules": "I don't think image props are supported yet so leave blank",
    "propNameCorrections": "Could be but not sure, will monitor as we go",
    "homepageRecipe": "no default, will be custom per project",
    "admissionsRecipe": "learn as we go",
    "learningRecipe": "learn as we go",
    "contactRecipe": "usually just a hero, form section, then footer. ",
    "otherRecipes": "learn as we go",
    "mergePolicy": "cross check data and override where there have been changes",
    "newComponentPolicy": "infer as much as possible. set up a questionnaire just like this one to get other info and share the link",
    "removedComponentPolicy": "usually will be replaced by another prop, often based on new prop features. ask questions through questionnaire when needed",
    "approvalThreshold": "none. we could perhaps keep a changelog, to stay up to date",
    "notesForIggy": "remember to keep learning as we go, storing info on patterns and conventions, etc. use this questionnaire format for confirmation, avoid assuming too much"
  },
  "notes": "Exported by Sylvain after local questionnaire submit returned 404."
}