-
Notifications
You must be signed in to change notification settings - Fork 27
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
sass processor? #47
Comments
Yes, or maybe. Since I'm not a user of sass or other CSS preprocessor, I cannot give you a clear answer. There should be many ways to implement the sass plugin, but the only idea I can come up with right now is to put the main functionality in
Several things to consider:
|
I would advocate for a hook specifically to accommodate sass and other transpilers. Considering how close Serum is to Jekyll if sass was supported one could import Jekyll templates very easily which would make Serum a very attractive static site generator |
I currently don't have any plans to make Serum Jekyll-compatible, or attractive to those who have used Jekyll. And I don't want people to regard Serum as "an Elixir implementation of Jekyll" or something else like that. Of course, I might be convinced to make such changes later, but that's a story of the future, far, far from now. |
Would you accept a PR for a transpiler build step for plugins? |
@Dalgona, may i ask what's wrong with that package? |
Honestly I have not checked the package yet, due to my personal schedules and lots of crazy stuffs after moving to Seoul 💦 I'll take a look at the package and see if it's an appropriate one for this project. |
Can the plugin system be used for processing sass files?
The text was updated successfully, but these errors were encountered: