3 ms·

Thanks for sharing. For those who might be wondering, using OP's GitHub repo as example, the first post in the issue thread[1] gets converted to a blog post[2]

Thanks for sharing. For those who might be wondering, using OP's GitHub repo as example, the first post in the issue thread[1] gets converted to a blog post[2]. That's pretty cool! Though, it will be tough to pry myself away from my blogging flow that uses Org mode as content source and uses all of the Org+Emacs functionality :) [1]: https://github.com/dbriemann/blog/issues/2 https://github.com/dbriemann/blog/issues/2 [2]: https://dbriemann.github.io/blog/2-introducing-glyph-static-site-generator-powered-by-github-issues-and-pages.html https://dbriemann.github.io/blog/2-introducing-glyph-static-...

fileeditview 9y ago
Sadly I don't have experience with emacs/org mode. Would this feature help in any way: https://github.com/dbriemann/glyph/issues/1 https://github.com/dbriemann/glyph/issues/1 ?
- kaushalmodi 9y ago
  No worries, I wasn't suggesting that you support that. I have a very well established blogging flow and I don't have any reason to move away from it. I just happened to come across this HN post, and found your project interesting.
  - fileeditview 9y ago
    I didn't want to convert you :D I just wondered if the linked feature would be useful for orgmode users or if it isn't really relevant. Maybe it would help someone else to use Glyph in a similar manner.
    - kaushalmodi 8y ago
      The linked issue is probably useful if someone using Emacs/Org exports Org to Markdown format, and then uploads to a Github issue as that feature proposes. But then I fail to see the advantage of that flow vs just committing the Markdown file to any online git repo and letting Netlify etc. take care of publishing the blog. Because.. uploading a Markdown file to a Github issue is one thing, but then what about refactoring, occasional post edits, etc.? Probably keep on overwriting the same Github issue with updated Markdown files? You don't have to reply to these questions here.. just some thought if you do invest time in implementing this feature request.
      - fileeditview 8y ago
        I just now saw your comment. You are right it takes away some benefits if you don't use the Github markdown editor to write/edit the issues. The only "benefit" I can still see then is the great commenting system that is attached to each issue. I added some more features to glyph over the last two weeks however I had not put any more thought into this feature so far. It is really low priority for me right now and I guess it's not THAT useful so that's ok :) Thanks for your input however. It is always very welcome.

fileeditview 9y ago

Sadly I don't have experience with emacs/org mode. Would this feature help in any way: https://github.com/dbriemann/glyph/issues/1 https://github.com/dbriemann/glyph/issues/1 ?

kaushalmodi 9y ago
No worries, I wasn't suggesting that you support that. I have a very well established blogging flow and I don't have any reason to move away from it. I just happened to come across this HN post, and found your project interesting.
- fileeditview 9y ago
  I didn't want to convert you :D I just wondered if the linked feature would be useful for orgmode users or if it isn't really relevant. Maybe it would help someone else to use Glyph in a similar manner.
  - kaushalmodi 8y ago
    The linked issue is probably useful if someone using Emacs/Org exports Org to Markdown format, and then uploads to a Github issue as that feature proposes. But then I fail to see the advantage of that flow vs just committing the Markdown file to any online git repo and letting Netlify etc. take care of publishing the blog. Because.. uploading a Markdown file to a Github issue is one thing, but then what about refactoring, occasional post edits, etc.? Probably keep on overwriting the same Github issue with updated Markdown files? You don't have to reply to these questions here.. just some thought if you do invest time in implementing this feature request.
    - fileeditview 8y ago
      I just now saw your comment. You are right it takes away some benefits if you don't use the Github markdown editor to write/edit the issues. The only "benefit" I can still see then is the great commenting system that is attached to each issue. I added some more features to glyph over the last two weeks however I had not put any more thought into this feature so far. It is really low priority for me right now and I guess it's not THAT useful so that's ok :) Thanks for your input however. It is always very welcome.