more about process

website/src/_posts/2019-04-liftoff-30.md

@@ -21,11 +21,15 @@ Holy shit! I can't believe this is the final day of our push to get Uppy to 1.0.
 
 We also had a team call where we discussed which items we can leave behind for the launch, and which ones we'd really like to get in. To save time for working on these tasks, instead of typing, let me share a screenshot of what we agreed upon:
 
-<center><a rel="noreferrer noopener" target="_blank" href="/images/blog/30daystoliftoff/2019-04-day30-board.png"><img width="400" src="/images/blog/30daystoliftoff/2019-04-day30-board.png"></a><br /><br /></center>
+<center><a rel="noreferrer noopener" target="_blank" href="/images/blog/30daystoliftoff/2019-04-day30-board.png"><img src="/images/blog/30daystoliftoff/2019-04-day30-board.png"></a><br /><br /></center>
 
 It's gonna be a close call, especially [Ife](https://github.com/ifedapoolarewaju) has a lot on his plate still with that "[600MB issue](https://github.com/tus/tus-js-client/issues/146)" untackled, but we did get [Marius](https://github.com/Acconut) on board with the way we want to solve it, so now it's full steam ahead.
 
-Before I'm going back to the team and help out where I can, I'd like to thank you for reading along with us for these past 30 days. To be honest, at times we regretted making this commitment, but we learned a lot, and it was fun to share our development process with the world and give interested developers a better understanding of what we're trying to accomplish.
+Before I'm going back to the team and help out where I can, I'd like to thank you for reading along with us for these past 30 days. To be honest, at times we regretted making this commitment
+
+<center><br /><img src="/images/blog/30daystoliftoff/2019-04-day30-posts.png"><br /><br /></center>
+
+A post a day can steal focus. But we learned a lot (like, you need rules like: first iteration needs to be in before lunch, second one after lunch, or folks end up working overtime and the next day, next post is up already!). Luckily we had the content team to take ownership of this and keep this away from the Uppy core team as much as possible, and it sure was fun to share our development process with the world and give interested developers a better understanding of what we're trying to accomplish, and how.
 
 I hope to see you tomorrow again for our 1.0 release! Make sure to follow us on [Twitter](https://twitter.com/uppy_io) or via our [RSS feed](https://uppy.io/atom.xml) if you don't want to miss it!