diff --git a/source/blog/2018-09-21-the-ember-times-issue-65.md b/source/blog/2018-09-21-the-ember-times-issue-65.md
index dca642c869..ec0596b4ae 100644
--- a/source/blog/2018-09-21-the-ember-times-issue-65.md
+++ b/source/blog/2018-09-21-the-ember-times-issue-65.md
@@ -1,7 +1,7 @@
---
title: The Ember Times - Issue No. 65
author: Chris Ng, L. Preston Sego III, Amy Lam, Ryan Mark, Jessica Jordan
-tags: Recent Posts, Newsletter, Ember.js Times, Ember Times, 2018
+tags: Newsletter, Ember.js Times, Ember Times, 2018
alias : "blog/2018/09/21-the-ember-times-issue-65.html"
responsive: true
---
diff --git a/source/blog/2018-09-28-the-ember-times-issue-66.md b/source/blog/2018-09-28-the-ember-times-issue-66.md
new file mode 100644
index 0000000000..7e4a99dc2f
--- /dev/null
+++ b/source/blog/2018-09-28-the-ember-times-issue-66.md
@@ -0,0 +1,134 @@
+---
+title: The Ember Times - Issue No. 66
+author: Bill Heaton, Chris Ng, Ryan Mark, Amy Lam, Kenneth Larsen, Jessica Jordan
+tags: Recent Posts, Newsletter, Ember.js Times, Ember Times, 2018
+alias : "blog/2018/09/28-the-ember-times-issue-66.html"
+responsive: true
+---
+
+Emberistas Ψ³ΩΨ§Ω
! πΉ
+
+Don't miss brand-new π₯ **RFCs for collocated addon tests** and **Router** served **query params** this week!
+We also have news from **Ember CLI Deprecation Workflow** and a _Lost & Found_ π΅πΎβ from the **Ember API Docs** for you,
+as well as a **Thank You note** for the most amazing **Issue Triaging** Experts! π
+
+---
+
+## [The Addon Test Is Right Where It Belongs β€οΈ](https://github.com/emberjs/rfcs/pull/378)
+
+
+Spending too much time looking for the **test files** of your **in-repo addon**? Feeling too exhausted to maintain a large test suite in which addon and host app test cases are meshed together? It doesn't have to be this way.
+
+Read more about how **collocated in-repo test files** are able to make your developer life easier in [this **shiny, new Request for Comments (RFC)**](https://github.com/emberjs/rfcs/pull/378). And as always, be sure to **leave your questions or β€οΈ emojis** right below the RFC's pull request description! β¨
+
+---
+
+## [ember-cli-deprecation-workflow 1.0.0 Release π](https://twitter.com/rwjblue/status/1045031033274605575)
+
+This week, [@rwjblue](https://github.com/rwjblue) (with help from [@mixonic](https://github.com/mixonic), [@atsao](https://github.com/atsao), and [@gaurav0](https://github.com/Gaurav0)) released [**1.0.0 of ember-cli-deprecation-workflow**](https://github.com/mixonic/ember-cli-deprecation-workflow/releases/tag/v1.0.0)!
+
+[ember-cli-deprecation-workflow](https://github.com/mixonic/ember-cli-deprecation-workflow) is an addon geared towards making Ember upgrades easier by allowing you to work through deprecations without massive console noise from Ember 1.x and 2.x deprecations.
+
+It silences the `console.log` noise or "deprecation spew" via configuration so that **only unhandled deprecations** will be **displayed in your console**. And now that the spew has settled down, you can process one deprecation at a time while ensuring that no new deprecations are introduced.
+
+Check it out on the [GitHub repo](https://github.com/mixonic/ember-cli-deprecation-workflow)!
+
+---
+
+## [And Today's Special on The Router Menu: Query Params π¨βπ³](https://github.com/emberjs/rfcs/pull/380)
+
+Ever had the need to read **query params (QPs)** off a `Controller` and pass it down to a component to change its UI state depending on the QP value?
+
+Ever had a hard time passing down QP values through layers and layers of components to do just that?
+
+It doesn't have to be this way. Read [this new RFC](https://github.com/emberjs/rfcs/pull/380) about exposing QPs as a _computed property_ on the `RouterService`. It proposes that this `Service` can then be injected into components easily which makes laborious passing of QP data obsolete.
+
+As always, **leave your comments** and appreciation [below the original proposal](https://github.com/emberjs/rfcs/pull/380) as long as it's **still under discussion**!
+
+---
+
+## [The Missing Docs Has Returned π](https://github.com/emberjs/ember.js/pull/17002)
+There has been [some documentation missing](https://github.com/emberjs/ember.js/issues/16993) from the Ember API docs from the release of 3.3 to 3.4. [@Gaurav0](https://github.com/Gaurav0) has done some great detective work π΅ and [fixed these issues](https://github.com/emberjs/ember.js/pull/17002) which means that **the missing documentation is now back.**
+
+Going forward the plan is to provide better testing for cases like this so you always have access to the documentation you need.
+
+---
+
+## [Project Structure for Single Page Apps π](https://dev.to/nullvoxpopuli/a-general-and-flexible-file-structure-that-works-for-all-projects-in-any-ecosystem-1lp9)
+
+Inspired by **Module Unification**, [@NullVoxPopuli](https://github.com/NullVoxPopuli) has
+written an article on **general project structure for single page apps.**
+In the article he explains how strucure is not specific to Ember, React, Vue, or anything else,
+but just needs to meet a set of guidelines for some common desired goals.
+
+Read it here: [_A general and flexible file structure that works for all projects in any ecosystem_](https://dev.to/nullvoxpopuli/a-general-and-flexible-file-structure-that-works-for-all-projects-in-any-ecosystem-1lp9)
+
+
+---
+
+## [Issue Triage π΅οΈ](https://paper.dropbox.com/doc/Ember.js-Issue-Triage--ANXsBgi3NQNstI7fSMQIONfOAg-Bh6AEHTj1Bt4rXq0Awg4R)
+
+
+ This week we had 5 volunteers helping π triage old issues that were inactive,
+ we closed 9 and labelled 31 of 50 from last week that need a submitter response π.
+ Those 31 may be closed in the next week or two. Together, we addressed 17 issues
+ that were inactive (and are still open π). We are beginning to establish a cadence
+ again of a team addressing issue triage π οΈ on Friday mornings.
+
+
+ Thanks for your
+
+ triage contributions
+ over the past two weeks πβ¦
+ @yininge,
+ @ryanlabouve,
+ @yohanmishkin,
+ @esbanarango,
+ @hakilebara, and
+ @pixelhandler.
+
+
+ The @emberjs/issues-team objective is to increase signal-to-noise ratio of issues
+ and π bugs so that the core team (and contributors) can take action to resolve bugs,
+ and spend less effort sorting the issues queue. Currently there are about 67 open bugs, of
+ those 25 had a reproduction (e.g. using ember-twiddle.com), and one with a pull request - total count about 270. Our aim is to get down to 150 in the next
+ couple months. If you'd like to help see the
+ #issue-triage
+ room in the community Discord chat.
+
+
+---
+
+## [Contributors' Corner](https://guides.emberjs.com/release/contributing/repositories/)
+
+This week we'd like to thank @rwjblue, @pzuraq, @chancancode, @Gaurav0, @simonihmig, @chadhietala, @bekzod, @iezer, @chrisrng, @jessica-jordan, @pixelhandler, @amyrlam, @tylerturdenpants, @acorncom, @runspired, @jrjohnson, @tmquinn, @BryanCrotaz, @mfeckie, @bmac, @Turbo87, @SparshithNR, @dcyriller, @gandalfar, @CodingItWrong, @ppcano, @hybridmuse for their contributions to Ember and related repositories! π
+
+---
+
+## [Got a Question? Ask Readers' Questions! π€](https://docs.google.com/forms/d/e/1FAIpQLScqu7Lw_9cIkRtAiXKitgkAo4xX_pV1pdCfMJgIr6Py1V-9Og/viewform)
+
+
+
+
+
Wondering about something related to Ember, Ember Data, Glimmer, or addons in the Ember ecosystem, but don't know where to ask? Readersβ Questions are just for you!
+
+
Submit your own short and sweet question under bit.ly/ask-ember-core. And donβt worry, there are no silly questions, we appreciate them all - promise! π€
+
+