couchdb-marketing mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy Wenk <andyw...@apache.org>
Subject Re: [NEWS] This weeks's CouchDB News are ready for feedback
Date Tue, 24 Jun 2014 11:58:45 GMT
I am perfectly fine with WP also. Bonus points for being able to use
Markdown.

Thanks for laying out your opinions. I think we can keep that short and
move on with using WP? I hope Dave is not too disappointed :) ...

Cheers

Andy


On 24 June 2014 12:24, Jan Lehnardt <jan@apache.org> wrote:

>
> On 24 Jun 2014, at 12:20 , Lena Reinhard <lena@thehoodiefirm.com> wrote:
>
> >> Dave, as you know I did some work with Hugo in the Swirl project. My
> blog
> >> on the other hand is now created with jekyll. I have to admit, that
> jekyll
> >> is way easier to use and is also based on git (
> >> https://github.com/andywenk/andywenk.github.io). So my conclusion is
> that
> >> hugo is great for usage as a documentation tool and jekyll fits better
> for
> >> a blog.
> >>
> >> On the other hand, the software on blog.couchdb.org is already a WP.
> So do
> >> we need to change that?
> >
> > Although I heard Jekyll and Hugo are nice, I'd say:
> > - Community management hat: I'd love to choose a tool that keeps entry
> barriers low, also for future committers. I know that many marketing people
> are used to WP and I'd definitely love to get more non-coding committers on
> board and reduce dependencies. It's bad for devs if marketing people have
> to ask for help frequently, also regarding lack of focus, and can tend to
> be frustrating for marketing people, too. And the more we can reduce that
> from the beginning, the better for the community.
> > - Personal hat: happy with anything, but used to WP :))
> > - Marketing hat: whatever makes migration easiest. Plus: WP could be
> good as it's already there, and makes administration etc. easy. Also: tools
> preferred that enable independence.
> >
> >>>> And who wants to do the data migration?
> >>>
> >>> I can do it, I like tedious repetitive tasks that can be done whenever
> >>> a few spare minutes appear.
> >>
> >>
> >> he he :)
> >>
> >>
> >>> I should be able to revert the current
> >>> HTML versions into markdown via pandoc without too much pain.
> >>>
> >>
> >> oh yes - I was wondering how we can manage that and pandoc should be
> >> perfect.
> >>
> >> When using pandoc in the way Dave proposed, it is maybe a good idea to
> >> rethink WP but I have to admit that I don't know with what format one
> can
> >> feed WP for content. Maybe also Markdown?
> >
> > WP can't be fed with Markdown yet, unfortunately. WYSIWYG-editor-only.
>
> In fact, since this is hosted on wordpress.com, Markdown is supported :)
>
> Best
> Jan
> --
>
> >
> > Else: what Jan says :)
> >
> >>
> >>
> >>> A+
> >>> Dave
> >>>
> >>> [1]: http://hugo.spf13.com/
> >>> [2]: http://octopress.org/
> >>> [3]: http://jekyllrb.com/
> >>
> >>
> >> Cheers
> >>
> >> Andy
> >>
> >>
> >> --
> >> Andy Wenk
> >> Hamburg - Germany
> >> RockIt!
> >>
> >> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
> >>
> >> https://people.apache.org/keys/committer/andywenk.asc
>
>


-- 
Andy Wenk
Hamburg - Germany
RockIt!

GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588

 https://people.apache.org/keys/committer/andywenk.asc

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message