Using plaintext in a template's frontmatter where you've also specified a different destination filename via permalink doesn't produce a renamed txt file. It only applies the permalink configuration to the html output.
Steps
Configure plaintext in your maizzle config to produce html and plaintext templates:
/*
|-------------------------------------------------------------------------------
| Production config https://maizzle.com/docs/environments
|-------------------------------------------------------------------------------
|
| This is where you define settings that optimize your emails for production.
| These will be merged on top of the base config.js, so you only need to
| specify the options that are changing.
|
*/
// since the base config is merged in with this during production builds
// and our base config uses env vars for configuring, we don't need overrides for production
module.exports = {};
3. Create a `testing.html` template and configure `permalink` and `plaintext` in its frontmatter:
```html
---
permalink: permalink_testing_build/permalink-override.html
plaintext: true
---
<x-main>
<h1>Permalink + Plaintext Reproduction</h1>
<p>This template ends up in permalink_testing_build/permalink-override.html</p>
<p>its plaintext version ends up living in build_local/testing.txt, though</p>
</x-main>
Run a production build
maizzle build production
Observe permalink-override.html at the provided permalink path and a testing.txt file in the original build_local directory
Reproduction Repository
Problem
Using
plaintext
in a template's frontmatter where you've also specified a different destination filename viapermalink
doesn't produce a renamed txt file. It only applies the permalink configuration to the html output.Steps
Configure
plaintext
in your maizzle config to produce html and plaintext templates:Add empty production config
// since the base config is merged in with this during production builds // and our base config uses env vars for configuring, we don't need overrides for production module.exports = {};
Run a production build
maizzle build production
Observe
permalink-override.html
at the provided permalink path and atesting.txt
file in the originalbuild_local
directoryDay late, but here's the repro I put together: https://github.com/joeyfigaro/maizzle-permalink-repro
Build results for .txt and .html outputs