discussion: blogpost support? #209

Open
suntong opened this Issue Mar 17, 2013 · 10 comments

Comments

Projects
None yet
6 participants
@suntong

suntong commented Mar 17, 2013

I know that there are static site generation tools exist e.g. Awestruct, but that's more a enterprise level solution.

Hope your team can implement blogpost alike for asciidoctor -- a tool for individual person to post their blog to some exiting blog sites. E.g.,

Stuart's blogs are 100% generated by AsciiDoc (via blogpost) https://srackham.wordpress.com/

Here's the example article from the AsciiDoc distribution and the blogpost README:

https://srackham.wordpress.com/asciidoc-example-article/
https://srackham.wordpress.com/blogpost-readme/

Please consider.

Thanks

@lordofthejars

This comment has been minimized.

Show comment
Hide comment
@lordofthejars

lordofthejars Apr 8, 2013

Member

Hello, see this project https://github.com/asciidoctor/asciidoctor-backends there we are providing some backends for generating custom output html files. I have implemented the deckjs backend using haml, but of course you can see that you can still use slim (thanks of Tilt gem) so feel free to fork the repo, implement a backend that generates a valid blogspot site, and share with all of us 😆 If you have any problem do not hesitate to ask me.
👍

Member

lordofthejars commented Apr 8, 2013

Hello, see this project https://github.com/asciidoctor/asciidoctor-backends there we are providing some backends for generating custom output html files. I have implemented the deckjs backend using haml, but of course you can see that you can still use slim (thanks of Tilt gem) so feel free to fork the repo, implement a backend that generates a valid blogspot site, and share with all of us 😆 If you have any problem do not hesitate to ask me.
👍

@mojavelinux

This comment has been minimized.

Show comment
Hide comment
@mojavelinux

mojavelinux Apr 11, 2013

Member

If you want a site where the content is 100% generated by AsciiDoc, then I recommend using Awestruct. That's why we worked on that integration.

The blogpost extension for AsciiDoc is actually using the WordPress API to submit the post into WordPress, thus only acting as a client. Personally, I'm not interested in working on that feature. However, if someone would like to do it, I recommend making a separate repository that we can add to the Asciidoctor organization that hands posting AsciiDoc files via an API. I think a single repository that has a directory for each provider (i.e., service) is the right way to go.

Member

mojavelinux commented Apr 11, 2013

If you want a site where the content is 100% generated by AsciiDoc, then I recommend using Awestruct. That's why we worked on that integration.

The blogpost extension for AsciiDoc is actually using the WordPress API to submit the post into WordPress, thus only acting as a client. Personally, I'm not interested in working on that feature. However, if someone would like to do it, I recommend making a separate repository that we can add to the Asciidoctor organization that hands posting AsciiDoc files via an API. I think a single repository that has a directory for each provider (i.e., service) is the right way to go.

@jasonbrooks

This comment has been minimized.

Show comment
Hide comment
@jasonbrooks

jasonbrooks Sep 13, 2013

I started looking into asciidoc because of asciidoctor -- the "just write" message really appealed to me.

Interestingly, though, before I could really "just write," I had to figure out a way to "just publish" my writings, and awestruct is, IMO, way too raw. I've been writing all my blog posts in asciidoc markup, but, because of blogpost.py, it's asciidoc that renders my writings, not asciidoctor.

If the project is counting on awestruct to bring asciidoctor to the masses, well, it's going to be an uphill climb.

I started looking into asciidoc because of asciidoctor -- the "just write" message really appealed to me.

Interestingly, though, before I could really "just write," I had to figure out a way to "just publish" my writings, and awestruct is, IMO, way too raw. I've been writing all my blog posts in asciidoc markup, but, because of blogpost.py, it's asciidoc that renders my writings, not asciidoctor.

If the project is counting on awestruct to bring asciidoctor to the masses, well, it's going to be an uphill climb.

@mojavelinux

This comment has been minimized.

Show comment
Hide comment
@mojavelinux

mojavelinux Sep 13, 2013

Member

On Fri, Sep 13, 2013 at 2:51 PM, Jason Brooks notifications@github.comwrote:

I started looking into asciidoc because of asciidoctor -- the "just write"
message really appealed to me.

Interestingly, though, before I could really "just write," I had to figure
out a way to "just publish" my writings, and awestruct is, IMO, way too
raw. I've been writing all my blog posts in asciidoc markup, but, because
of blogpost.py, it's asciidoc that renders my writings, not asciidoctor.

If the project is counting on awestruct to bring asciidoctor to the
masses, well, it's going to be an uphill climb.

Hey Jason!

I totally get that point, and there's no doubt about it. We have to look at
Awestruct as an emerging option, but also appeal to more widely used
publishing platforms like Wordpress--in particular--and Drupal.

The nice part is that the logic for integrating AsciiDoc (or Asciidoctor)
with the Wordpress API is already done, thanks to blogpost.py. All we need
to be able to do is rework it--likely in Ruby--so that it uses Asciidoctor
instead.

Is anyone interested in writing this script, which is practically
guaranteed success and widespread usage? Who's up for the challenge?

Here's the starting point for anyone interested:

http://code.google.com/p/blogpost/source/browse/blogpost.py

To be honest, it wouldn't even be that difficult to swap out the call to
AsciiDoc's pseudo-API for a commandline invocation of asciidoctor.

-Dan

Dan Allen | http://google.com/profiles/dan.j.allen

Member

mojavelinux commented Sep 13, 2013

On Fri, Sep 13, 2013 at 2:51 PM, Jason Brooks notifications@github.comwrote:

I started looking into asciidoc because of asciidoctor -- the "just write"
message really appealed to me.

Interestingly, though, before I could really "just write," I had to figure
out a way to "just publish" my writings, and awestruct is, IMO, way too
raw. I've been writing all my blog posts in asciidoc markup, but, because
of blogpost.py, it's asciidoc that renders my writings, not asciidoctor.

If the project is counting on awestruct to bring asciidoctor to the
masses, well, it's going to be an uphill climb.

Hey Jason!

I totally get that point, and there's no doubt about it. We have to look at
Awestruct as an emerging option, but also appeal to more widely used
publishing platforms like Wordpress--in particular--and Drupal.

The nice part is that the logic for integrating AsciiDoc (or Asciidoctor)
with the Wordpress API is already done, thanks to blogpost.py. All we need
to be able to do is rework it--likely in Ruby--so that it uses Asciidoctor
instead.

Is anyone interested in writing this script, which is practically
guaranteed success and widespread usage? Who's up for the challenge?

Here's the starting point for anyone interested:

http://code.google.com/p/blogpost/source/browse/blogpost.py

To be honest, it wouldn't even be that difficult to swap out the call to
AsciiDoc's pseudo-API for a commandline invocation of asciidoctor.

-Dan

Dan Allen | http://google.com/profiles/dan.j.allen

@lordofthejars

This comment has been minimized.

Show comment
Hide comment
@lordofthejars

lordofthejars Sep 13, 2013

Member

Well another option could be creating a backend for blogspot

El divendres 13 de setembre de 2013, Dan Allen ha escrit:

On Fri, Sep 13, 2013 at 2:51 PM, Jason Brooks <notifications@github.com<javascript:_e({}, 'cvml', 'notifications@github.com');>

wrote:

I started looking into asciidoc because of asciidoctor -- the "just
write"
message really appealed to me.

Interestingly, though, before I could really "just write," I had to
figure
out a way to "just publish" my writings, and awestruct is, IMO, way too
raw. I've been writing all my blog posts in asciidoc markup, but, because
of blogpost.py, it's asciidoc that renders my writings, not asciidoctor.

If the project is counting on awestruct to bring asciidoctor to the
masses, well, it's going to be an uphill climb.

Hey Jason!

I totally get that point, and there's no doubt about it. We have to look at
Awestruct as an emerging option, but also appeal to more widely used
publishing platforms like Wordpress--in particular--and Drupal.

The nice part is that the logic for integrating AsciiDoc (or Asciidoctor)
with the Wordpress API is already done, thanks to blogpost.py. All we need
to be able to do is rework it--likely in Ruby--so that it uses Asciidoctor
instead.

Is anyone interested in writing this script, which is practically
guaranteed success and widespread usage? Who's up for the challenge?

Here's the starting point for anyone interested:

http://code.google.com/p/blogpost/source/browse/blogpost.py

To be honest, it wouldn't even be that difficult to swap out the call to
AsciiDoc's pseudo-API for a commandline invocation of asciidoctor.

-Dan

Dan Allen | http://google.com/profiles/dan.j.allen


Reply to this email directly or view it on GitHubhttps://github.com/asciidoctor/asciidoctor/issues/209#issuecomment-24426724
.

Enviat amb Gmail Mobile

Member

lordofthejars commented Sep 13, 2013

Well another option could be creating a backend for blogspot

El divendres 13 de setembre de 2013, Dan Allen ha escrit:

On Fri, Sep 13, 2013 at 2:51 PM, Jason Brooks <notifications@github.com<javascript:_e({}, 'cvml', 'notifications@github.com');>

wrote:

I started looking into asciidoc because of asciidoctor -- the "just
write"
message really appealed to me.

Interestingly, though, before I could really "just write," I had to
figure
out a way to "just publish" my writings, and awestruct is, IMO, way too
raw. I've been writing all my blog posts in asciidoc markup, but, because
of blogpost.py, it's asciidoc that renders my writings, not asciidoctor.

If the project is counting on awestruct to bring asciidoctor to the
masses, well, it's going to be an uphill climb.

Hey Jason!

I totally get that point, and there's no doubt about it. We have to look at
Awestruct as an emerging option, but also appeal to more widely used
publishing platforms like Wordpress--in particular--and Drupal.

The nice part is that the logic for integrating AsciiDoc (or Asciidoctor)
with the Wordpress API is already done, thanks to blogpost.py. All we need
to be able to do is rework it--likely in Ruby--so that it uses Asciidoctor
instead.

Is anyone interested in writing this script, which is practically
guaranteed success and widespread usage? Who's up for the challenge?

Here's the starting point for anyone interested:

http://code.google.com/p/blogpost/source/browse/blogpost.py

To be honest, it wouldn't even be that difficult to swap out the call to
AsciiDoc's pseudo-API for a commandline invocation of asciidoctor.

-Dan

Dan Allen | http://google.com/profiles/dan.j.allen


Reply to this email directly or view it on GitHubhttps://github.com/asciidoctor/asciidoctor/issues/209#issuecomment-24426724
.

Enviat amb Gmail Mobile

@mojavelinux

This comment has been minimized.

Show comment
Hide comment
@mojavelinux

mojavelinux Sep 13, 2013

Member

I've hacked the blogpost.py to support a custom AsciiDoc command. It can
now use Asciidoctor.

Source: https://github.com/mojavelinux/asciidoc-blogpost.py

Instructions:

$ gem install asciidoctor
$ git clone https://github.com/mojavelinux/asciidoc-blogpost.py
$ cd asciidoc-blogpost.py/
$ cat >~/.blogpost
URL = 'http://appname-username.rhcloud.com/xmlrpc.php'
USERNAME = 'username'
PASSWORD = 'password'

$ ./blogpost.py --asciidoc asciidoctor post sample-post.adoc

Voila!

I tested this using a Wordpress installation I setup on OpenShift.

This would make an excellent blog post for asciidoctor.org. Jason, if you
get this working and want to contribute a post, I'd be more than happy to
have you as a guest blogger!

The one missing piece is that I did not port the blogpost backend over,
which simply customizes the HTML output to be more of what Wordpress
expects. It wouldn't take much effort to create this backend using the
following repository as a starting point:

https://github.com/asciidoctor/asciidoctor-backends

Enjoy!

-Dan

On Fri, Sep 13, 2013 at 3:42 PM, Dan Allen dan.j.allen@gmail.com wrote:

On Fri, Sep 13, 2013 at 2:51 PM, Jason Brooks notifications@github.comwrote:

I started looking into asciidoc because of asciidoctor -- the "just
write" message really appealed to me.

Interestingly, though, before I could really "just write," I had to
figure out a way to "just publish" my writings, and awestruct is, IMO, way
too raw. I've been writing all my blog posts in asciidoc markup, but,
because of blogpost.py, it's asciidoc that renders my writings, not
asciidoctor.

If the project is counting on awestruct to bring asciidoctor to the
masses, well, it's going to be an uphill climb.

Hey Jason!

I totally get that point, and there's no doubt about it. We have to look
at Awestruct as an emerging option, but also appeal to more widely used
publishing platforms like Wordpress--in particular--and Drupal.

The nice part is that the logic for integrating AsciiDoc (or Asciidoctor)
with the Wordpress API is already done, thanks to blogpost.py. All we need
to be able to do is rework it--likely in Ruby--so that it uses Asciidoctor
instead.

Is anyone interested in writing this script, which is practically
guaranteed success and widespread usage? Who's up for the challenge?

Here's the starting point for anyone interested:

http://code.google.com/p/blogpost/source/browse/blogpost.py

To be honest, it wouldn't even be that difficult to swap out the call to
AsciiDoc's pseudo-API for a commandline invocation of asciidoctor.

-Dan

Dan Allen | http://google.com/profiles/dan.j.allen

Dan Allen | http://google.com/profiles/dan.j.allen

Member

mojavelinux commented Sep 13, 2013

I've hacked the blogpost.py to support a custom AsciiDoc command. It can
now use Asciidoctor.

Source: https://github.com/mojavelinux/asciidoc-blogpost.py

Instructions:

$ gem install asciidoctor
$ git clone https://github.com/mojavelinux/asciidoc-blogpost.py
$ cd asciidoc-blogpost.py/
$ cat >~/.blogpost
URL = 'http://appname-username.rhcloud.com/xmlrpc.php'
USERNAME = 'username'
PASSWORD = 'password'

$ ./blogpost.py --asciidoc asciidoctor post sample-post.adoc

Voila!

I tested this using a Wordpress installation I setup on OpenShift.

This would make an excellent blog post for asciidoctor.org. Jason, if you
get this working and want to contribute a post, I'd be more than happy to
have you as a guest blogger!

The one missing piece is that I did not port the blogpost backend over,
which simply customizes the HTML output to be more of what Wordpress
expects. It wouldn't take much effort to create this backend using the
following repository as a starting point:

https://github.com/asciidoctor/asciidoctor-backends

Enjoy!

-Dan

On Fri, Sep 13, 2013 at 3:42 PM, Dan Allen dan.j.allen@gmail.com wrote:

On Fri, Sep 13, 2013 at 2:51 PM, Jason Brooks notifications@github.comwrote:

I started looking into asciidoc because of asciidoctor -- the "just
write" message really appealed to me.

Interestingly, though, before I could really "just write," I had to
figure out a way to "just publish" my writings, and awestruct is, IMO, way
too raw. I've been writing all my blog posts in asciidoc markup, but,
because of blogpost.py, it's asciidoc that renders my writings, not
asciidoctor.

If the project is counting on awestruct to bring asciidoctor to the
masses, well, it's going to be an uphill climb.

Hey Jason!

I totally get that point, and there's no doubt about it. We have to look
at Awestruct as an emerging option, but also appeal to more widely used
publishing platforms like Wordpress--in particular--and Drupal.

The nice part is that the logic for integrating AsciiDoc (or Asciidoctor)
with the Wordpress API is already done, thanks to blogpost.py. All we need
to be able to do is rework it--likely in Ruby--so that it uses Asciidoctor
instead.

Is anyone interested in writing this script, which is practically
guaranteed success and widespread usage? Who's up for the challenge?

Here's the starting point for anyone interested:

http://code.google.com/p/blogpost/source/browse/blogpost.py

To be honest, it wouldn't even be that difficult to swap out the call to
AsciiDoc's pseudo-API for a commandline invocation of asciidoctor.

-Dan

Dan Allen | http://google.com/profiles/dan.j.allen

Dan Allen | http://google.com/profiles/dan.j.allen

@jasonbrooks

This comment has been minimized.

Show comment
Hide comment
@jasonbrooks

jasonbrooks Sep 13, 2013

Excellent, Dan -- I'll check it out!

Excellent, Dan -- I'll check it out!

@metasean

This comment has been minimized.

Show comment
Hide comment
@metasean

metasean Mar 22, 2015

For other users looking for a more friendly front-end, and mad-crazy-easy installation process, checkout https://github.com/HubPress/hubpress.io . It's still very much in early development, but the early development is clearly moving toward the front-end I am looking for.

For other users looking for a more friendly front-end, and mad-crazy-easy installation process, checkout https://github.com/HubPress/hubpress.io . It's still very much in early development, but the early development is clearly moving toward the front-end I am looking for.

@mojavelinux

This comment has been minimized.

Show comment
Hide comment
@mojavelinux

mojavelinux Mar 30, 2015

Member

👍 HubPress.io is definitely one of the official methods of publishing a blog in AsciiDoc. You might also consider a static site generator like Middleman or JBake.

Member

mojavelinux commented Mar 30, 2015

👍 HubPress.io is definitely one of the official methods of publishing a blog in AsciiDoc. You might also consider a static site generator like Middleman or JBake.

@tiensonqin

This comment has been minimized.

Show comment
Hide comment
@tiensonqin

tiensonqin Jun 3, 2018

Hi, you can also try Hidifferent.

It has some blog features (Github sync, RSS, Tags), this is mine:
https://hidifferent.com/@tiensonqin

Hi, you can also try Hidifferent.

It has some blog features (Github sync, RSS, Tags), this is mine:
https://hidifferent.com/@tiensonqin

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