Content driven components about plenti

[jimafisk]

This can be accomplished like so:

Example data source /content/pages/about.json

This is one example, but the data source key/value structure is flexible so do whatever works for you:

{
  "components": [
    {
      "component": "red",
      "fields": {"title": "I'm red"}
    },
    {
      "component": "green",
      "fields": {"title": "I'm green"}
    },
    {
      "component": "blue",
      "fields": {"title": "I'm blue"}
    }
  ]
}

Example dynamic component import in /layout/content/pages.svelte

<script>
  export components;

  async function loadComponent(component) {
    let path = "../components/" + component + ".svelte";
    return await import(path).then(res => res.default);
  }
</script>

{#if components}
  {#each components as { component, fields } }
    {#await loadComponent(component)}
    {:then co}
      <svelte:component this="{co}" {...fields} />
    {:catch error}
    {/await}
  {/each}
{/if}

Example imported component /layout/components/blue.svelte

<script>
  export let title;
</script>

<h1>{title}</h1>

<style>
  h1 {
    color: blue;
  }
</style>

However, the internal gopack does not support dynamic imports so you currently have to go into public/spa/content/pages.js after building and convert the .svelte extension in the loadComponent() function to be .js manually.

Currently Gopack actually checks that static import paths exist in the filesystem, this will be challenging to implement with dynamic imports since they can use variables that we'd have to get the value of. For now the easiest thing to do would be a simple string replace of .svelte to .js when they match regex import(); with single or double quotes inside the brackets and a sub-pattern of .svelte. This won't account for paths defined outside the import like in the example above and doesn't guarantee that the converted path won't throw an error. Down the road it would be nice to make this better.

It would also be nice to move the loadComponent() function into the /layout/scripts/ folder of the starter since this is something a lot of folks might be interested in using.