├── 2017 ├── June │ └── OPEN-pfdw-1w.html ├── March │ ├── pfdw-2w.html │ └── pfdw-3w.html └── May │ ├── pfdw-1w.html │ └── pfdw-2w.html ├── .gitignore ├── AREA.md └── README.md /.gitignore: -------------------------------------------------------------------------------- 1 | *.DS_Store 2 | .AppleDouble 3 | .LSOverride 4 | 5 | # Icon must end with two \r 6 | Icon 7 | 8 | 9 | # Thumbnails 10 | ._* 11 | 12 | # Files that might appear in the root of a volume 13 | .DocumentRevisions-V100 14 | .fseventsd 15 | .Spotlight-V100 16 | .TemporaryItems 17 | .Trashes 18 | .VolumeIcon.icns 19 | .com.apple.timemachine.donotpresent 20 | 21 | # Directories potentially created on remote AFP share 22 | .AppleDB 23 | .AppleDesktop 24 | Network Trash Folder 25 | Temporary Items 26 | .apdisk 27 | -------------------------------------------------------------------------------- /2017/June/OPEN-pfdw-1w.html: -------------------------------------------------------------------------------- 1 | 2 | THE PLAINFLOW DIGESTED WEEK - April 3rd 3 | 4 | 16 | 17 | 18 | 19 | 20 | 157 | 163 | 164 | 165 |
166 | 167 | 168 | 445 | 446 |
169 |
170 | 171 | 172 | 173 | 174 | 175 | 185 | 186 |
176 | 177 | 178 | 179 | 182 | 183 |
180 | View in your Medium 181 |
184 |
187 | 188 | 189 | 198 | 199 |
190 | 191 | 192 | 195 | 196 |
193 | 194 |
197 |
200 | 201 | 202 | 203 | 204 | 205 | 403 | 404 |
206 | 207 | 208 | 209 | 210 | 211 | 212 | 213 | 214 | 215 | 216 | 217 | 218 | 219 | 220 | 221 | 222 | 223 | 228 | 229 | 230 | 231 | 232 | 233 | 234 | 235 | 236 | 237 | 238 | 239 | 240 | 241 | 242 | 243 | 244 | 245 | 246 | 247 | 248 | 249 | 250 | 251 | 252 | 253 | 254 | 255 | 256 | 262 | 263 | 264 | 270 | 271 | 272 | 278 | 279 | 280 | 286 | 287 | 288 | 289 | 290 | 291 | 292 | 293 | 294 | 295 | 296 | 297 | 298 | 299 | 300 | 301 | 302 | 303 | 304 | 305 | 306 | 307 | 308 | 309 | 310 | 315 | 316 | 317 | 318 | 319 | 320 | 321 | 322 | 323 | 324 | 325 | 326 | 327 | 328 | 329 | 330 | 331 | 332 | 333 | 334 | 335 | 336 | 337 | 338 | 339 | 344 | 345 | 346 | 350 | 351 | 352 | 356 | 357 | 358 | 362 | 363 | 364 | 365 | 366 | 367 | 368 | 369 | 370 | 371 | 372 | 373 | 374 | 375 | 376 | 377 | 378 | 379 | 380 | 381 | 382 | 383 | 384 | 387 | 388 | 389 | 392 | 393 | 394 | 397 | 398 | 399 | 400 | 401 |
The PlainFlow Digested Week
224 |
225 |

226 |
227 |
On Email
x Pull Request approved 🎉
257 |
258 |

1. The Mozilla Foundation recently announced to serve as the legal/fiscal home for the Thunderbird project, but Thunderbird will migrate off Mozilla Corporation infrastructure, separating the operational aspects of the project. 259 |

260 |
261 |
265 |
266 |

267 |

268 |
269 |
273 |
274 |

275 |

276 |
277 |
281 |
282 |

283 |

284 |
285 |
On Data and Analytics
x Pull Request approved 🎉
311 |

312 | 313 |

314 |
On Tech Marketing
x Pull Request approved ✨
340 |

341 | 342 |

343 |
347 |

348 |

349 |
353 |

354 |

355 |
359 |

360 |

361 |
What suprised us this week..
By the PlainFlow Team 🙌
385 |

386 |
390 |

391 |
395 |

396 |
402 |
405 | 406 | 407 | 409 | 410 |
408 |
411 | 412 | 413 | 414 | 421 | 422 |
415 | Contribute on GitHub for the next newsletter 420 |
423 | 424 | 425 | 426 | 427 | 428 | 438 | 439 | 440 | 441 | 442 |
429 |
430 | 431 | 432 | 434 | 435 |
This is an Open Source Weekly Digest curated by the PlainFlow team. To unsubscribe click here
PlainFlow Inc, 340 Lemn Ave, Walnut, CA 91789, US
© 2017 PlainFlow, Inc. 433 |
436 |
437 |
443 |
444 |
447 |
448 | 449 | -------------------------------------------------------------------------------- /2017/March/pfdw-2w.html: -------------------------------------------------------------------------------- 1 | 2 | THE PLAINFLOW DIGESTED WEEK - March 20th 3 | 4 | 18 | 19 | 20 | 21 | 22 | 159 | 165 | 166 | 167 |
168 | 169 | 170 | 460 | 461 |
171 |
172 | 173 | 174 | 175 | 176 | 177 | 187 | 188 |
178 | 179 | 180 | 181 | 184 | 185 |
182 | View in your browser 183 |
186 |
189 | 190 | 191 | 200 | 201 |
192 | 193 | 194 | 197 | 198 |
195 | 196 |
199 |
202 | 203 | 204 | 205 | 206 | 207 | 418 | 419 |
208 | 209 | 210 | 211 | 212 | 213 | 214 | 215 | 216 | 217 | 218 | 219 | 220 | 221 | 222 | 223 | 224 | 225 | 233 | 234 | 235 | 236 | 237 | 238 | 239 | 240 | 241 | 242 | 243 | 244 | 245 | 246 | 247 | 248 | 249 | 250 | 251 | 252 | 253 | 254 | 255 | 256 | 257 | 258 | 259 | 260 | 261 | 268 | 269 | 270 | 277 | 278 | 279 | 286 | 287 | 288 | 295 | 296 | 297 | 298 | 299 | 300 | 301 | 302 | 303 | 304 | 305 | 306 | 307 | 308 | 309 | 310 | 311 | 312 | 313 | 314 | 315 | 316 | 317 | 318 | 319 | 326 | 327 | 328 | 329 | 330 | 331 | 332 | 333 | 334 | 335 | 336 | 337 | 338 | 339 | 340 | 341 | 342 | 343 | 344 | 345 | 346 | 347 | 348 | 349 | 350 | 357 | 358 | 359 | 363 | 364 | 365 | 369 | 370 | 371 | 375 | 376 | 377 | 378 | 379 | 380 | 381 | 382 | 383 | 384 | 385 | 386 | 387 | 388 | 389 | 390 | 391 | 392 | 393 | 394 | 395 | 396 | 397 | 400 | 401 | 402 | 406 | 407 | 408 | 412 | 413 | 414 | 415 | 416 |
The PlainFlow Digested Week
226 |
227 |

Hey 👋 .
228 | Welcome to the first (1# - 20th March) PlainFlow Digested Week. 229 |
Read this post in our Blog if you'd like to know more about this project. 230 |

231 |
232 |
On Email Marketing
4 Pull Request approved 🎉
262 |
263 |

264 | 1. Pail Airy talked about Email Typography in "Knowing Your Type"
265 |

266 |
267 |
271 |
272 |

273 | 2. Wilbert Heinen made this github wrap-up of articles about email accessibility
274 |

275 |
276 |
280 |
281 |

282 | 3. Litmus published the 2017 State of Email Report
283 |

284 |
285 |
289 |
290 |

291 | 4. Kristian Robinson described in this blogpost his email tribute to Alien.
292 |

293 |
294 |
On Marketing Automation
1 Pull Request approved 🎉
320 |

321 | 1. Myk Pono just published 322 | What is Next in the Sales Enablement Industry? 323 |
324 |

325 |
On Tech Marketing
4 Pull Request approved ✨
351 |

352 | 1. Rich Barton Co-Founder at Zillow Group Great talked about the future of modern marketing teams in The New Age of Marketing 353 | 354 |
355 |

356 |
360 |

2. On Hacker News: What is your startup's marketing stack?
361 |

362 |
366 |

3. On Growth Hackers: What is your current Marketing technology stack?
367 |

368 |
372 |

4. Amit from Clearbit talked about de-anonymizing web traffic data and conversion rates.
373 |

374 |
What suprised us this week..
By the PlainFlow Team 🙌
398 |

1. The Google Blog announced this week that you can now send and receive money in the Android Gmail app

399 |
403 |

2. The Google Blog also announced Gmail Add-ons, now developers can write an integration once and deploy it anywhere. 404 |

405 |
409 |

3. 410 | Nathan Barry explaines in this post how he bootstrapped an Email Marketing Business.

411 |
417 |
420 | 421 | 422 | 424 | 425 |
423 |
426 | 427 | 428 | 429 | 436 | 437 |
430 | Contribute on GitHub for the next newsletter 435 |
438 | 439 | 440 | 441 | 442 | 443 | 453 | 454 | 455 | 456 | 457 |
444 |
445 | 446 | 447 | 449 | 450 |
This is an Open Source Weekly Digest curated by the PlainFlow team. To unsubscribe click here
PlainFlow Inc, 340 Lemn Ave, Walnut, CA 91789, US
© 2017 PlainFlow, Inc. 448 |
451 |
452 |
458 |
459 |
462 |
463 | 464 | -------------------------------------------------------------------------------- /2017/March/pfdw-3w.html: -------------------------------------------------------------------------------- 1 | 2 | THE PLAINFLOW DIGESTED WEEK - March 27th 3 | 4 | 18 | 19 | 20 | 21 | 22 | 159 | 165 | 166 | 167 |
168 | 169 | 170 | 459 | 460 |
171 |
172 | 173 | 174 | 175 | 176 | 177 | 187 | 188 |
178 | 179 | 180 | 181 | 184 | 185 |
182 | View in your browser 183 |
186 |
189 | 190 | 191 | 200 | 201 |
192 | 193 | 194 | 197 | 198 |
195 | 196 |
199 |
202 | 203 | 204 | 205 | 206 | 207 | 417 | 418 |
208 | 209 | 210 | 211 | 212 | 213 | 214 | 215 | 216 | 217 | 218 | 219 | 220 | 221 | 222 | 223 | 224 | 225 | 230 | 231 | 232 | 233 | 234 | 235 | 236 | 237 | 238 | 239 | 240 | 241 | 242 | 243 | 244 | 245 | 246 | 247 | 248 | 249 | 250 | 251 | 252 | 253 | 254 | 255 | 256 | 257 | 258 | 263 | 264 | 265 | 270 | 271 | 272 | 277 | 278 | 279 | 284 | 285 | 286 | 291 | 292 | 293 | 294 | 295 | 296 | 297 | 298 | 299 | 300 | 301 | 302 | 303 | 304 | 305 | 306 | 307 | 308 | 309 | 310 | 311 | 312 | 313 | 314 | 315 | 316 | 319 | 320 | 321 | 325 | 326 | 330 | 331 | 332 | 333 | 334 | 335 | 336 | 337 | 338 | 339 | 340 | 341 | 342 | 343 | 344 | 345 | 346 | 347 | 348 | 349 | 350 | 351 | 352 | 353 | 354 | 359 | 360 | 361 | 364 | 365 | 366 | 370 | 371 | 372 | 376 | 377 | 378 | 379 | 380 | 381 | 382 | 383 | 384 | 385 | 386 | 387 | 388 | 389 | 390 | 391 | 392 | 393 | 394 | 395 | 396 | 397 | 398 | 401 | 402 | 403 | 406 | 407 | 408 | 411 | 412 | 413 | 414 | 415 |
The PlainFlow Digested Week
226 |
227 |

Hey 👋 .
Over the past few weeks of the PlainFlow Digested Week we’ve talked about email marketing and marketing technology in general. This week we’re double clicking into one particular aspect: implication of Artificial Intelligence on Marketing.

228 |
229 |
On Email Marketing
5 Pull Request approved 🎉
259 |
260 |

1. We've found a Sketch plugin called Slinky that allows you to export Sketch artboards as ready–to–send HTML e-mail templates

261 |
262 |
266 |
267 |

3. Table tr td sent a terrific email that works as an email builder

268 |
269 |
273 |
274 |

3. Albert Wegner partner at Union Square Ventures (USV) shared a few things that he has learned about email

275 |
276 |
280 |
281 |

4. If you're seeing weird rendering in the Outlook app on iOS/Android, Courtney Fantinato wrote a blogpost about her recent findings

282 |
283 |
287 |
288 |

5. This week I've discovered this collection of amazing email campaigns by Jason Rodrigues

289 |
290 |
On Analytics
3 Pull Request approved 🎉
317 |

1. Jessica Best wrote 6 Steps to Putting Data to Work in Email

318 |
322 |

2. Mickey Alon wrote The Next Big Thing in Digital Customer Acquisition 323 |

324 |
327 |

3. The Clearbit team just published a new series called "Data Driven Sales" 328 |

329 |
On Tech Marketing
x Pull Request approved ✨
355 |

1. Jonathan Taylor explains why every digital marketer needs to learn how to deploy marketing technology. 356 | 357 |

358 |
362 |

2. Huw Walters published How to be Data-Driven: 5 Things Your Startup Should Start Doing"

363 |
367 |

368 |

369 |
373 |

374 |

375 |
What suprised us this week..
By the PlainFlow Team 🙌
399 |

1. Segment just announced the Open Fellowship 2017 (Applications close May 8th 2017)

400 |
404 |

2. Only a few hours ago Tomasz Tunguz published Creating Tension In Your Startup's Marketing Positioning.

405 |
409 |

410 |
416 |
419 | 420 | 421 | 423 | 424 |
422 |
425 | 426 | 427 | 428 | 435 | 436 |
429 | Contribute on GitHub for the next newsletter 434 |
437 | 438 | 439 | 440 | 441 | 442 | 452 | 453 | 454 | 455 | 456 |
443 |
444 | 445 | 446 | 448 | 449 |
This is an Open Source Weekly Digest curated by the PlainFlow team. To unsubscribe click here
PlainFlow Inc, 340 Lemn Ave, Walnut, CA 91789, US
© 2017 PlainFlow, Inc. 447 |
450 |
451 |
457 |
458 |
461 |
462 | 463 | -------------------------------------------------------------------------------- /2017/May/pfdw-1w.html: -------------------------------------------------------------------------------- 1 | 2 | THE PLAINFLOW DIGESTED WEEK - April 3rd 3 | 4 | 16 | 17 | 18 | 19 | 20 | 157 | 163 | 169 | 170 |
171 | 172 | 173 | 477 | 478 |
174 |
175 | 176 | 177 | 178 | 179 | 180 | 190 | 191 |
181 | 182 | 183 | 184 | 187 | 188 |
185 | View this Email on Medium 186 |
189 |
192 | 193 | 194 | 203 | 204 |
195 | 196 | 197 | 200 | 201 |
198 | 199 |
202 |
205 | 206 | 207 | 208 | 209 | 210 | 448 | 449 |
211 | 212 | 213 | 214 | 215 | 216 | 217 | 218 | 219 | 220 | 221 | 222 | 223 | 224 | 225 | 226 | 227 | 228 | 236 | 237 | 238 | 239 | 240 | 241 | 242 | 243 | 244 | 245 | 246 | 247 | 248 | 249 | 250 | 251 | 252 | 253 | 254 | 255 | 256 | 257 | 258 | 259 | 260 | 261 | 262 | 263 | 264 | 265 | 266 | 267 | 268 | 272 | 273 | 274 | 275 | 276 | 277 | 280 | 281 | 282 | 283 | 284 | 287 | 288 | 289 | 295 | 296 | 297 | 303 | 304 | 305 | 311 | 312 | 313 | 314 | 315 | 316 | 317 | 318 | 319 | 320 | 321 | 322 | 323 | 324 | 325 | 326 | 327 | 328 | 329 | 330 | 331 | 332 | 333 | 334 | 335 | 339 | 340 | 341 | 342 | 343 | 344 | 349 | 350 | 351 | 352 | 353 | 354 | 358 | 359 | 360 | 361 | 362 | 363 | 364 | 365 | 366 | 367 | 368 | 369 | 370 | 371 | 372 | 373 | 374 | 375 | 376 | 377 | 378 | 379 | 382 | 383 | 384 | 389 | 390 | 391 | 396 | 397 | 398 | 399 | 400 | 401 | 402 | 403 | 404 | 405 | 406 | 407 | 408 | 409 | 410 | 411 | 412 | 413 | 414 | 415 | 416 | 417 | 418 | 419 | 423 | 424 | 425 | 428 | 429 | 430 | 431 | 436 | 437 | 442 | 443 | 444 | 445 | 446 |
The PlainFlow Digested Week
229 |
230 |

Hey 👋 .
231 | Welcome to the first PlainFlow Digested Week of May. 232 |
Last week I’ve personally started sharing in the PlainFlow blog my own thoughts on the Marketing and Analytics industries.
I initially wrote a piece called 233 | The Modern SaaS Stack and the Unexploited Amount of Data and later on I published a post titled AI implications on Marketing and Analytics. You will read an excerpt of these two posts down below in this email.
Got ideas/suggesttions? Don't be shy -- get in touch with me @leonardofed on twitter.

234 |
235 |
On Email Marketing
3 Pull Request approved 🎉
269 |

1. Sjoerd van Rijen, Product Designer at WeTransfer explained 270 | how and why they redesigned all their emails.

271 |
278 |

2. Litmus published the 2017 State of Email Workflows. The paper is 45 pages long, but if you’re into email marketing you shouldn’t miss a single word.

279 |
285 |

3. Mailchimp interviewed Camille Palu and Miah Roberts from tabletrtd. Their Own Code: The Weird, Wonderful World of Table Tr Td

286 |
290 |
291 |

292 |

293 |
294 |
298 |
299 |

300 |

301 |
302 |
306 |
307 |

308 |

309 |
310 |
On Data and Analytics
3 Pull Request approved 🎉
336 |

1. We’re about to see a shift between the want-phase and the need-phase for Artificial Intelligence. In “AI implications on Marketing and Analytics”, I explained why and how Analytics and Marketing SaaS products will use Artificial Intelligence. 337 |

338 |
345 |

2. Avinash Kaushik from Google Developers published another truly wonderful piece: Artificial Intelligence: Implications On Marketing, Analytics, And You 346 | 347 |

348 |
355 |

3. Chris Stucchio sparked my curiosity with a very interesting analysis on 356 | Uber’s customer acquisition trough.

357 |
On Tech Marketing
3 Pull Request approved ✨
380 |

1. I published on the PlainFlow Blog: The Modern SaaS Stack and the Unexploited Amount of Data. We uncovered how most of the startups adjust their product/marketing strategies based on new technologies and how they measure (or don’t measure) the impact of those technologies on their customers’ experiences.

381 |
385 |

2. Garry Lee explained in a very interesting piece why Customer Data Platforms (CDP) will be the next evolution of your marketing automation 386 | 387 |

388 |
392 |

3. Microsoft published their Marketing Stack and Scott Brinker promptly wrote Microsoft shares their marketing stack in the Stackies, and it’s awesome 393 | 394 |

395 |
What suprised us this week..
By the PlainFlow Team 🙌
420 |

1. Claire Suellentrop launched on Product Hunt her new book: Websites that Convert: The fundamentals of writing compelling website. The book is very well-written and it’s plenty of actionable insights. Very recommended. 421 |

422 |
426 |

2. Ask HN: How did you acquire your first 100 users?

427 |
432 |

3. DHH, co-founder of Basecamp and creator of Ruby on Rails explained 433 | in this podcast 434 | his main principles in marketing.

435 |
438 |

4. Ask HN: 439 | Should I create a clone of a popular SaaS with rock-bottom pricing? 440 |

441 |
447 |
450 | 451 | 452 | 454 | 455 |
453 |
456 | 457 | 458 | 459 | 466 | 467 |
460 | Contribute on GitHub for the next newsletter 465 |
468 | 469 | 470 | 471 | 472 | 473 | 474 |
475 |
476 |
479 |
480 | 481 | 482 | -------------------------------------------------------------------------------- /2017/May/pfdw-2w.html: -------------------------------------------------------------------------------- 1 | 2 | THE PLAINFLOW DIGESTED WEEK - April 3rd 3 | 4 | 16 | 17 | 18 | 19 | 20 | 157 | 163 | 169 | 170 |
171 | 172 | 173 | 469 | 470 |
174 |
175 | 176 | 177 | 178 | 179 | 180 | 190 | 191 |
181 | 182 | 183 | 184 | 187 | 188 |
185 | View this Email on Medium 186 |
189 |
192 | 193 | 194 | 203 | 204 |
195 | 196 | 197 | 200 | 201 |
198 | 199 |
202 |
205 | 206 | 207 | 208 | 209 | 210 | 440 | 441 |
211 | 212 | 213 | 214 | 215 | 216 | 217 | 218 | 219 | 220 | 221 | 222 | 223 | 224 | 225 | 226 | 227 | 228 | 236 | 237 | 238 | 239 | 240 | 241 | 242 | 243 | 244 | 245 | 246 | 247 | 248 | 249 | 250 | 251 | 252 | 253 | 255 | 256 | 257 | 258 | 259 | 260 | 261 | 262 | 263 | 264 | 265 | 266 | 267 | 268 | 269 | 273 | 274 | 275 | 276 | 277 | 278 | 281 | 282 | 283 | 284 | 285 | 289 | 290 | 291 | 297 | 298 | 299 | 306 | 307 | 308 | 314 | 315 | 316 | 317 | 318 | 319 | 320 | 321 | 322 | 323 | 324 | 325 | 326 | 327 | 328 | 329 | 330 | 331 | 332 | 333 | 334 | 335 | 336 | 337 | 338 | 341 | 342 | 343 | 344 | 345 | 346 | 349 | 350 | 351 | 352 | 353 | 354 | 358 | 359 | 360 | 361 | 362 | 363 | 364 | 365 | 366 | 367 | 368 | 369 | 370 | 371 | 372 | 373 | 374 | 375 | 376 | 377 | 378 | 379 | 383 | 384 | 385 | 389 | 390 | 391 | 395 | 396 | 397 | 398 | 399 | 400 | 401 | 402 | 403 | 404 | 405 | 406 | 407 | 408 | 409 | 410 | 411 | 412 | 413 | 414 | 415 | 416 | 417 | 418 | 422 | 423 | 424 | 428 | 429 | 430 | 434 | 435 | 436 | 437 | 438 |
The PlainFlow Digested Week
229 |
230 |

Hey 👋 .
This week we've got more than 10 spot-on articles.
231 | **But** before we get started we wanted to tell you that the release day it's getting every day closer. The private beta for PlainFlow is expected to be announced for this summer. A few of you were already contacted for a sneak preview before the launch of the private beta. 232 | 233 |

Want to have a sneak preview of the product? Don't be shy -- get in touch with me @leonardofed on twitter or just hit reply to this email. 👈

234 |
235 |
On Email & Product Marketing 254 |
4 Pull Request approved 🎉
270 |

1. Karel Ledru-Mathé from Visible wrote You do not need email confirmation in your sign up flow and explained how & why reduced a 4 step process to 1. 271 |

272 |
279 |

2. Scott Belsky wrote about a brilliant post prospecting a future Notification layer API that would flip the model, incentivizing app developers to push only the most actionable, well-timed, and value-add notifications in pursuit of premium attention for their products.

280 |
286 |

3. Nichole Elizabeth DeMeré wrote an golden piece about the interactions between brand and customer over the course of the entire relationship in the 8 Innovative Ways to Use CX Metrics to Create Unbeatable Customer Experience ft. Wootric 287 |

288 |
292 |
293 |

294 |

295 |
296 |
300 |
301 |

4. One of my favorite post of the month is: Drip campaigns — How we do them differently at Highrise by Nathan Kontny. He explained in layman terms the fatigue that marketing automation is having right now. 302 | 303 |

304 |
305 |
309 |
310 |

311 |

312 |
313 |
On Data and Analytics
3 Pull Request approved 🎉
339 |

1. The ConversionXL Blog asked me to write something for them. I said yes. It took me 3full hours to write Customer Data Platforms: The Next Big Shift in SaaS Marketing Stacks.

340 |
347 |

2. Our previous post The Modern SaaS Stack and the Unexploited Amount of Data was featured on Y Combinator’s HN and the thread ended up being very interesting.

348 |
355 |

3. Bill Franklin deconstructed the Google Analytics tracking script in this 10min read post. 356 |

357 |
On Tech Marketing
3 Pull Request approved ✨
380 |

1. The marketing technology landscape is big, broad, and deep. So many different kinds of solutions fall under that umbrella, and they don’t always fit into nice, neat categories. Scott Brinker proposed a model for organizing the chaos of marketing technology: The 6 C’s Model. 381 |

382 |
386 |

2. I repeated many and many times how the standard GA’s attribution models were so broken. Last week at Google’s Marketing Next the company announced the beta for Google Attribution, a free tool for examining the role that different marketing strategies play in customer purchasing decisions. 387 |

388 |
392 |

3. Lana K. Moore will soon start a new blog on Marketing Technology — looks promising. It will be launched by June 2017. The site is still under construction. 393 |

394 |
What suprised us this week..
By the PlainFlow Team 🙌
419 |

1. I got a very curious email asking me how we create the charts in our articles. I took the chance to publish How We Write at PlainFlow and explain how looks like our entire writing workflow. 420 |

421 |
425 |

1. Really Good Emails featured The PlainFlow Digested Week email newsletter, you can get to the source code on Github. 426 |

427 |
431 |

3. I usually don’t feature products here, but Roadmap by Brittany Fuller blew me away. One of the best product to capture feedback and communicate your progress to users. 432 |

433 |
439 |
442 | 443 | 444 | 446 | 447 |
445 |
448 | 449 | 450 | 451 | 458 | 459 |
452 | Read this email on Medium 457 |
460 | 461 | 462 | 463 | 464 | 465 | 466 |
467 |
468 |
471 |
472 | 473 | -------------------------------------------------------------------------------- /AREA.md: -------------------------------------------------------------------------------- 1 | # The PlainFlow Digested Week - Content Area 2 | 3 | --- 4 | The PlainFlow Digested Week is a crowdsource email newsletter that goes to all the PlainFlow subscribers. 5 | 6 | You can contribute to this project by submitting useful links in this public 7 | Github repo. 8 | 9 | Every Monday morning **9 am PST** we will review and approve all your pull requests aiming to send the email to your inbox by **10 am PST**. 10 | 11 | We will mention all the featured authors on twitter with the @plainflow account before sending the email out. 12 | 13 | Here's a detailed article in our Blog. 14 | 15 | --- 16 | 17 | This describes the structure of the PlainFlow Digested Week. 18 | If you want us to cover a new topic, open a pull request addig a title and a short description. 19 | 20 | ### Email Structure 📚 21 | 22 | We divided the Email template into 5 different main areas: 23 | 24 | 1. Headline 25 | 2. On Email Marketing 26 | 3. On Marketing Automation 27 | 4. On Tech Marketing 28 | 5. What surprised us 29 | 6. Here goes your new Area 30 | 31 | ##### [Headline](#head) 32 | 33 | In the headline, we'll tell you a brief summary of the content below. How people contributed to the Email and how many PRs we've got. 34 | We'll also tell you what's email number and a quick link to get access to another newsletter we've published. 35 | 36 | 37 | ##### [On Email Marketing](email) 📧 38 | 39 | This whole section is about Email Marketing. 40 | If you work in this industry you'll probably already read a few great blogs out there: 41 | 42 | - Litmus Blog 43 | - Really Good Emails 44 | - TABLE TR TD 45 | - HTeuMeuLeu Medium Blog 46 | 47 | 48 | What can you submit here? 49 | 50 | 1. tech articles about email development 51 | 2. email tutorials 52 | 3. onboarding emails, product emails, retention emails, promotion emails, whatever-category-emails 53 | 4. podcast or video? sure, those are welcome too as long as they are about emails 54 | 55 | 56 | ##### [On Marketing Automation](#automation) ⚡ 57 | 58 | Marketing Automation is one of the topics that we love most. 59 | Simple smart ways of building complex things. 60 | 61 | What can you submit here? 62 | 63 | 1. marketing automation examples 64 | 2. automation scenarios 65 | 3. marketing integrations 66 | 4. product, marketing, sales automation 67 | 5. tutorials 68 | 69 | ##### [On Tech Marketing](#martech) 💻 70 | 71 | No matter if work in Product, Marketing, or in Sales, nowadays you need to understand how technologies work together and how you can get this most out of those. 72 | 73 | We want this whole section dedicated to Marketing Technology. 74 | 75 | What can you submit here? 76 | 77 | 1. real-world scenarios of Marketing Technology 78 | 2. how different SaaS marketing tools work together 79 | 3. APIs and marketing integrations 80 | 81 | ##### [What surprised us this week](#wow) 82 | 83 | If you've got something interesting that you want to show here but it's not suitable for all the categories above, this is your go-to section. 84 | 85 | As long as you respect the Content & Style Guidelines written above, you can post here (almost) your want. 86 | 87 | ##### [Here goes your new Area](#new-area) 88 | 89 | Here goes the description of your new proposal. 90 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # The PlainFlow Digested Week 2 | 3 | The PlainFlow Digested Week is a crowdsource email newsletter that goes to all the PlainFlow subscribers. 4 | 5 | You can contribute to this project by submitting useful links in this public 6 | Github repo. 7 | 8 | Every Monday morning **9 am PST** we will review and approve all your pull requests aiming to send the email to your inbox by **10 am PST**. 9 | 10 | We will mention all the featured authors on twitter with the @plainflow account before sending the email out. 11 | 12 | Here's a detailed article in our Blog. 13 | 14 | --- 15 | 16 | ### Content Guidelines 📚 17 | 18 | In order to keep the bar as high as possible, we will add your posts only if they meet these 4 principles: 19 | 20 | ###### Content 📑 21 | 22 | The great Alfred Hitchcock once said: _to make a great film you need three things - the script, the script and the script._ 23 | 24 | The script is to movies as the content is to newsletters. 25 | 26 | We're asking you to submit only what **you** think is so genuinely interesting that's worth other people's time. 27 | Always avoid catchy titles or more-searched-terms kind of articles. 28 | 29 | ###### Bias 📢 30 | We're starting this open project because we love great content and because we want to make that available to you, not because we want you to read specific blogs or authors. 31 | 32 | It's important for us that you submit articles in a fair way without obvious bias or added commentary. 33 | 34 | ###### Transparency 🔬 35 | 36 | We won't sell anything in this newsletter. It's not our goal and should not be your goal either. We need your full transparency. 37 | 38 | ###### Freshness 🗞 39 | 40 | In a world that is constantly changing being up to date is quite relevant. 41 | 42 | We're not Google and we're not as strict as the PageRank algorithm, but fresh content is something we value. 43 | 44 | ### Email Structure 📚 45 | 46 | We divided the Email template into 5 different main areas: 47 | 48 | 1. Headline 49 | 2. On Email Marketing 50 | 3. On Marketing Automation 51 | 4. On Tech Marketing 52 | 5. What surprised us 53 | 54 | ##### [Headline](#head) 55 | 56 | In the headline, we'll tell you a brief summary of the content below. How people contributed to the Email and how many PRs we've got. 57 | We'll also tell you what's email number and a quick link to get access to another newsletter we've published. 58 | 59 | 60 | ##### [On Email Marketing](email) 📧 61 | 62 | This whole section is about Email Marketing. 63 | If you work in this industry you'll probably already read a few great blogs out there: 64 | 65 | - Litmus Blog 66 | - Really Good Emails 67 | - TABLE TR TD 68 | - HTeuMeuLeu Medium Blog 69 | 70 | 71 | What can you submit here? 72 | 73 | 1. tech articles about email development 74 | 2. email tutorials 75 | 3. onboarding emails, product emails, retention emails, promotion emails, whatever-category-emails 76 | 4. podcast or video? sure, those are welcome too as long as they are about emails 77 | 78 | 79 | ##### [On Marketing Automation](#automation) ⚡ 80 | 81 | Marketing Automation is one of the topics that we love most. 82 | Simple smart ways of building complex things. 83 | 84 | What can you submit here? 85 | 86 | 1. marketing automation examples 87 | 2. automation scenarios 88 | 3. marketing integrations 89 | 4. product, marketing, sales automation 90 | 5. tutorials 91 | 92 | ##### [On Tech Marketing](#martech) 💻 93 | 94 | No matter if work in Product, Marketing, or in Sales, nowadays you need to understand how technologies work together and how you can get this most out of those. 95 | 96 | We want this whole section dedicated to Marketing Technology. 97 | 98 | What can you submit here? 99 | 100 | 1. real-world scenarios of Marketing Technology 101 | 2. how different SaaS marketing tools work together 102 | 3. APIs and marketing integrations 103 | 104 | ##### [What surprised us this week](#wow) 105 | 106 | If you've got something interesting that you want to show here but it's not suitable for all the categories above, this is your go-to section. 107 | 108 | As long as you respect the Content & Style Guidelines written above, you can post here (almost) your want. 109 | 110 | 111 | ### Our workflow 📚 112 | 113 | We will be reviewing and approving the pull requests each day from Tuesday till Monday morning. 114 | 115 | 116 | Every Monday morning **8:30 am PST** we will make sure we had reviewed and approved all your pull requests. We'll send the email to your inbox by **10 am PST**. 117 | 118 | This is how a traditional Monday morning will look like for us. 119 | 120 | 121 | 122 | 123 | ### 'How do I submit a new link?' 📚 124 | 125 | You can contribute to the PlainFLow Digested Week by submitting a pull request. 126 | 127 | > what is a pull request? read on here 128 | 129 | If you're new to GitHub, don't panic. You don't necessarily need to open your terminal to submit a pull request. 130 | 131 | Here's a 5-step tutorial to submit a new article: 132 | 133 | 1. Find the current _Month_ directory by clicking here 134 | 2. Open the **OPEN**-pfwd-$w.html 135 | 3. Click _"Edit this file"_ 136 | 4. Edit the HTML of the page and add your links 137 | 5. Select the _"Create a new branch for this commit and start a pull request"_ and submit your edits. 138 | 139 | >To learn more about Pull Request feel free to check this out: https://help.github.com/articles/about-pull-requests 140 | 141 | ### Style Guidelines when submitting a new Pull Request 📚 142 | 143 | This is the structure we suggest you submit links. 144 | 145 | 146 |
147 | - rank your resource at the beginning based on the other links position 148 | - mention the author (link to his twitter profile) and give credits 149 | - brief of the description of the resource 150 | - resource link 151 |
152 | 153 | **So this is how a final pull request will look like.** 154 | 155 | 156 | 157 |
158 | And This is how will look like the **code**: 159 | 160 | 161 |
162 | 163 | 164 | ### How can you help us! 165 | 166 | You can subscribe to the PlainFlow Digested Week here: http://www.plainflow.com/ 167 | 168 | Now have fun! 169 | --------------------------------------------------------------------------------