Ideas

• Have suede support symlinks, which are resolved in the release branch These actually wouldn't work* since pushes to release would be to the file, and then wouldn't be easily resolvable to their destination file. With some extra work, I guess it would be possible to (1) unsymlink the file, apply the changes, re-follow the symlink, and make the target file look like the state of the release file. Seems like a little too much magic though!
• Customize suede to be able to support branches other than release
  • Helpful for monorepo to support several languages, but have a single test bed environment
  • Maybe would work with a .suede file at the root of the repo?
• Markdown inclusion parser that uses template tag with data attributes:
  • unexpanded

# Title

Check this out:

<template data-src="./example.md" />

• expanded

# Title

Check this out:

<template data-src="./example.md">
 
## Some title

Hi!!

</template>

• inline
• Hello world
• variables
• Hello <template data-var="question" />

Example on how to make codeblocks

<template id="ts" data-match="*.ts" data-prefix="```ts\n" data-suffix="\n```" />

<template data-src="./example.ts" data-wrapper="ts" />

<template data-src="./another.ts" data-wrapper="ts" />

Example on how to create chats, and have custom wrappers based on file name:

<template id="tutor" data-match="tutor*" data-prefix="Tutor: \n" data-suffix="" />

<template id="user" data-match="user*" data-prefix="User: \n" data-suffix="" />

<template data-delimiter=" " data-src="./user* ./tutor*" data-wrapper="tutor user" data-sort="created" data-order="desc" data-limit="10" />