Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a media type and extension/template that can be used as passthrough #967

Closed
daveaglick opened this issue Oct 15, 2021 · 0 comments
Closed
Labels
General Enhancement New feature or request

Comments

@daveaglick
Copy link
Member

daveaglick commented Oct 15, 2021

Sometimes we've got files that we want to process as content including processing front matter, but we don't want to actually render anything in the body. There's currently no good way to handle this. Add a .statiq extension and corresponding media type and template.

Basically we want to be able to pass this check for files that don't need to be rendered by an actual template:
image

It's assumed that most files with a .statiq extension would also have a DestinationPath set since we likely don't actually want to output the .statiq extension. Perhaps .statiq extensions should even be removed by default (I.e. foo.txt.statiq would get an automatic output path of foo.txt and foo.statiq would become foo). Make sure to document this.

Also see if we can't modify the default InputFiles globbing pattern to include underscore files with a .statiq extension. That way, a file like _redirects.statiq would automatically be included, get processed, and output to _redirects.

These files should default to ContentType.Asset unless an alternate ContentType is specified in front matter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
General Enhancement New feature or request
Development

No branches or pull requests

1 participant