Lena, I'd say just go with whatever you think looks best. Design is often best left to a single person. :)
On 25 June 2014 17:57, Andy Wenk <[email protected]> wrote: > +2 for http://publishdemo.wordpress.com/ > +1 for http://trulyminimaldemo.wordpress.com/ > -0 for the rest > > But we will have the CouchDB Logo will we :) > > Thanks Lena > > Cheers > > Andy > > > On 25 June 2014 17:42, Lena Reinhard <[email protected]> wrote: > >> I'd suggest keeping things as simple as possible for now. If we find a >> designer who'd want to create a nice design, we could still do a relaunch. >> >> Thus, I'd suggest just using one of the free WP themes. >> I have already taken a closer look at available Wordpress themes, there >> would be e.g.: >> http://trulyminimaldemo.wordpress.com/ >> http://publishdemo.wordpress.com/ >> http://en.wordpress.com/themes/syntax/ >> http://tonaldemo.wordpress.com/ >> More themes are here: http://en.wordpress.com/themes/type/free/ >> >> >> >> On 25.06.2014, at 12:35, Andy Wenk <[email protected]> wrote: >> >> > any idea who's going to create a simple but nice design for the new >> blog? I >> > do not have the skills to do that ... >> > >> > >> > On 24 June 2014 21:15, Jan Lehnardt <[email protected]> wrote: >> > >> >> >> >> On 24 Jun 2014, at 16:39 , Lena Reinhard <[email protected]> >> wrote: >> >> >> >>> d'oh. Updated. >> >>> >> >>> so, as far as I got it, next steps would be: >> >>> 1) data migration – Jan and Alexander, could you handle that? >> >>> 2) granting access (= creating accounts, preferrably admin accounts, if >> >> no one is opposed; accounts needed for: >> >>> - Noah >> >>> - Alexander (see step 1) >> >>> - Lena >> >>> - … ? >> >>> 3) updating design (include new header + tagline) >> >>> 4) notifying dev@ about the change >> >>> 5) posting last week's weekly news ;) (can do that as soon as I got >> >> access) >> >>> 6) post promotion >> >>> 7) check if categories are correct; we should also keep in mind to tag >> >> at least new posts correctly >> >> >> >> 8) Update the main website to link to the new blog. >> >> 9) eventually post on the old blog that we have a new blog :) >> >> >> >> >> >>> >> >>> Anything else? :) >> >>> >> >>> >> >>> On 24.06.2014, at 16:38, Lena Reinhard <[email protected]> wrote: >> >>> >> >>>> so, as far as I got it, next steps would be: >> >>>> 1) data migration – Jan and Alexander, could you handle that? >> >>>> 2) granting access (= creating accounts, preferrably admin accounts, >> if >> >> no one is opposed; accounts needed for: >> >>>> - Noah >> >>>> - Alexander (see step 1) >> >>>> - Lena >> >>>> - … ? >> >>>> 3) notifying dev@ about the change >> >>>> 4) posting last week's weekly news ;) (can do that as soon as I got >> >> access) >> >>>> 5) post promotion >> >>>> >> >>>> Anything else? :) >> >>>> >> >>>> On 24.06.2014, at 15:45, Noah Slater <[email protected]> wrote: >> >>>> >> >>>>> +1 on supporting Lena's choice: WordPress. >> >>>>> >> >>>>> As the other major blogger on this project, WP is also my preference. >> >>>>> >> >>>>> On 24 June 2014 13:58, Andy Wenk <[email protected]> wrote: >> >>>>>> 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 <[email protected]> wrote: >> >>>>>> >> >>>>>>> >> >>>>>>> On 24 Jun 2014, at 12:20 , Lena Reinhard <[email protected]> >> >> 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 >> >>>>> >> >>>>> >> >>>>> >> >>>>> -- >> >>>>> Noah Slater >> >>>>> https://twitter.com/nslater >> >>>> >> >>> >> >> >> >> >> > >> > >> > -- >> > Andy Wenk >> > Hamburg - Germany >> > RockIt! >> > >> > http://www.couchdb-buch.de >> > http://www.pg-praxisbuch.de >> > >> > 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 -- Noah Slater https://twitter.com/nslater
