-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Adding a pelican-newpost script #1410
Comments
Hi Ben. Thanks for the thoughtful comments. In light of #800, such a feature would most likely find a warm reception as a submission to the soon-to-be-created |
Oh, great! I'll hold off on working on this until that happens, then. |
Did this every happen @TC01 ? |
It did not; I was waiting for the pelican-tools repository to get created.
|
I've created the repository as a first step: https://github.com/getpelican/pelican-tools would really appreciate if someone could contribute a pull request for #800 to get things started. |
@kylef what's the state of this? I could try my hand at a pelican-newpost script for pelican-tools if that was going to be supported, but right now pelican-tools looks abandoned. |
cc @justinmayer ^ I already have a new-post script for my workflow, based on a jinja tamplate here. Would gladly update and PR it. Is the deserted pelican-tools repo ever going to be used? |
Who would like to volunteer to submit a pull request to the Pelican Tools repository to add this feature? |
Hi, @justinmayer I'd like to give it a go. |
That would be great, Luigi. Let us know if you get stuck on anything! 💫 |
Hi, @luigibertaco I recently wrote a newpost.py script for my own blog site. I also wrote a short blog post about it. The script only supports markdown and is tailored to my own need. Maybe a start point for your effort. |
Hi, @georgexyz19 Thanks for that, I am trying to open the PR today but I'll definitely have a look at your implementation to make it as production-ready as possible. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your participation and understanding. |
Closing in favor of getpelican/pelican-tools#6 |
So, this is something I'd be interested in working on, but I'm not sure exactly what the right way to do it would be:
I maintain two Pelican sites (currently). It didn't dawn on me until now how useful a script that automatically sets stuff like the date and prompts the user for title/category/slug/author/etc would be.
I was imagining something like pelican-quickstart, which prompts the user directly for most arguments. After having the idea, though, a quick search through the repository found a pull request #1085, which added a script called pelican-article that does something very similar, although it takes command line arguments.
The request was rejected for other reasons, and as far as I can tell hasn't been resubmitted by the original author since then? (If I am wrong, please correct me).
As I'm interested in this feature: would it be permissible for me to take @icyleaf's script as a starting point, modify it, and resubmit it under a different name? I mean, I might do things slightly differently, but his script is probably a decent starting point.
The text was updated successfully, but these errors were encountered: