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.

Sign up for GitHub

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

Jump to bottom

Moving from jade to pug #39

Closed
ghost opened this issue Apr 19, 2016 · 6 comments
Closed

Moving from jade to pug #39

ghost opened this issue Apr 19, 2016 · 6 comments
Assignees
@ahmadnassri

Comments

@ghost
Copy link

ghost commented Apr 19, 2016

As this issue mentions jade is changing to pug. Are there any plans to use pug instead of jade(now or in the future)?
@ahmadnassri
Copy link
Owner

indeed, we should update the dependencies ...

@ahmadnassri ahmadnassri self-assigned this Apr 20, 2016
@Surgo
Copy link
Contributor

Surgo commented Jul 19, 2016

Renaming a published module are not supported by npm.
Can I fork and publish metalsmith-pug?

@Surgo Surgo mentioned this issue Jul 19, 2016
Merged
7 tasks
@ahmadnassri
Copy link
Owner

I'll look into this today

@ahmadnassri
Copy link
Owner

@Surgo I'm ready to merge, deprecate and publish, we also have to make a PR on https://github.com/metalsmith/metalsmith.io (I can do that once the PR is merged, this acts as a note to self)

@ahmadnassri
Copy link
Owner

@luksprog @Surgo all done! metalsmith-pug is now live!

@ahmadnassri
Copy link
Owner

ref for metalsmith.io site: metalsmith/metalsmith.io#180

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ahmadnassri ahmadnassri

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Surgo @ahmadnassri