yeah I guess I was picturing Atlanta thinking it was Santa Clara

(the exhibit hall I mean)

working on a release notes post for all the releases from last week, @brosner can you review what i've said about DUA? http://blog.pinaxproject.com/post/iugftOUd/ at some point

and yes, that is just a working title

looks great to to me. way better than what I did on github releases 😉

The blog post looks great! Good job @paltman! simple smile Let me know when it’s ready to be published.

did a bunch of work tonight on switching starter projects over to gulp, here is the draft of a blog post to serve as an announcement once I cut releases of the starter projects: http://blog.pinaxproject.com/post/wHQIfamu/

Great work! simple smile

did we want to dress up my first screencast any before uploading to our youtube channel? Or should i do another take where I narrative as i go instead of doing it as a second track afterwards?

or should I record a few more

before we decide to publish any of htem

in case we can establish a certain pattern

@paltman: I think it would be good if we had a couple more in store before we publish the first one so we could publish one each week for example instead of publishing one and then having a huge break between the next one. I’d like to have some consistency if possible.

i need to get a blog post out covering pinax-cohorts and pinax-theme-bootstrap

a screencast as well

yep

@katherinemichel sorry it's been so long since we've spoken. as i was catching up on conversations in various channels it occurred to me one thing that could be really cool for the community is a weekly blog post that provides a Pinax Status. It could be any releases that happened that week, notable commits, issues closed, and summaries of noteworthy conversations in different channels. doesn't have to be comprehensive (that'd be way to stressful) just highlights. also, could be a good place for you to document your thoughts/plans/tasks that you are working on in Pinax as you continue making this community awesome. One idea for doing this practically would be to start a draft post on Sunday night or Monday with a outline of things you would like to say are done (for the things you want to accomplish taht week) and then add to it and edit it as you go through out the week so come Friday, it's not much editing to do before publish. Just an idea. Thoughts?

I've been off on my own working on the tutorial. Plus, I had a few major mishaps happen in the last couple of months, so was less sociable than normal. I think it sounds like a good idea.

I've also still got a blog post I started after the last release that I'd like to publish in some form sometime. Maybe can edit a bit and add some things from 18.04 and publish.

i think even updates on how tutorial is going and your ideas for it would be interesting to hear about

sounds good

I've gotten past some of the easier to understand things and been grappling with the harder parts. I think I will get there, but takes a bit of time to understand.

No just understand, but how to explain what is important for users to know.

I know you’d mentioned taking notes on DUA when I suggested that recent question that is becoming a FAQ

I have screenshots of a number of things that have been suggested for docs and/or FAQs.

definitely capturing what people have been asking is a good way to drive documentation improvements

FAQs are nice to start with because you can just add to them incrementally as questions come up

without a lot of planning or structure

That's true