Soft launch meta issue

[tmeasday]

Both re-read each every article

• Typos / formatting
• Check links work
• Ensure references include links (e.g. “next section”)
• Take Screenshots
• Check code snippets (ensure work w/ 1.2)
• Make a list of non-trivial incomplete parts

  Todos app code

• [x] Fix #33 #34 #36 for code style guide
• [x] Using simpleschema#validate in validateNewUser doesn't work with useraccounts:flow routing because of inspecting error details. Add special case for validation error https://github.com/meteor-useraccounts/flow-routing/pull/23 https://github.com/meteor/guide/issues/163 [note: not actually an issue in Todos since we don't need to do this when using useraccounts]
• [x] Backtrack to ordered arguments for publications
• [x] meteor/todos#57 - simple schema and audit-argument-checks https://github.com/aldeed/meteor-simple-schema/pull/518
• [x] Need to resolve denorm code issue: https://github.com/meteor/todos/pull/60
• [x] Confirm that audit-argument-checks even works with keyword args...
• [x] meteor/todos#56 - fix re-rendering and triple-function
• [x] Update parts of the code that need i18n with comments referring to the GitHub issue

  Content

• [ ] Add section to methods about HTTP API - Should we have something about HTTP API/server side routes? - fix simple:rest to allow attaching options to existing method
• [x] Update code snippets with field reactivity: https://github.com/meteor/guide/issues/173
• [x] Address all comments from @splendido review https://github.com/meteor/guide/pull/154
• [x] Denormalizer content got lost between methods and collections (waiting on resolution of PR, https://github.com/meteor/todos/pull/60)
• [x] Backtrack to ordered arguments for publications
• [x] Finalize article order
• [x] Confirm that postCSS content is up to date meteor/guide#157
• [x] Build tool package loading reword meteor/guide#151
• [x] Fix security section meteor/guide#148
• [x] Method call lifecycle improvement meteor/guide#147
• [x] Deal with i18n situation Figure out tap:i18n section in UX guide
• [x] Bulk updates Recommend bulk updates in migrations, rather than iterating over all items and running a new update query
• [x] Add SEO / prerender.io - dfischer:prerenderio
• [x] Remove references to cursor-utils: Build a cursor-utils package that allows "slicing" cursors
• [x] Example of waiting on specific data meteor/guide#159
• [x] Add some text about how to do CD w/ circle (both for apps on Galaxy/mother and packages)
• [x] Update data loading article to filter fields in all publications
• [x] Update security article to show example of Lists.publicFields

  Website

• [x] Figure out how to factor images into separate directory
• [x] Deal with Blaze chapter rendering problems
• [x] Order articles "Welcome!" probably shouldn't be the 6th article in the sidebar
• [x] Fix or remove search??? - disabled by Sashko
• [x] Fix mobile code snippets meteor/guide#125

  Stretch

• [x] Investigate markdown rendering on Atmosphere... https://atmospherejs.com/alanning/roles is particularly bad - the entire document is one huge broken link.

[stubailo]

Proofreading progress, Sashko

• [x] Welcome!
• [x] Collections and Schemas
• [x] Publications and Data Loading
• [x] Methods
• [x] URLs and Routing
• [x] Users and Accounts
• [x] User Interfaces
• [x] Blaze
• [x] Security
• [x] Deployment and Monitoring
• [x] Build system

Proofreading progress, Tom

• [x] Welcome!
• [x] Collections and Schemas
• [x] Publications and Data Loading
• [x] Methods
• [x] URLs and Routing
• [x] Users and Accounts
• [x] User Interfaces
• [x] Blaze
• [x] Security
• [x] Deployment and Monitoring
• [x] Build system

[stubailo]

Collections notes:

• "synchronous fibers-based API" might be super confusing :+1:
• "(see the methods article for a discussion of patterns to do this)" we need to write the denorm section :+1:
• The article mentions denorming userId onto todos, but we don't do this anymore. Perhaps we should come up with a different example? :+1:
• Need to link from hooks to the new denorm section in methods :+1:
• Removed: "(by default apps are considered at migrations "zero")" we should probably have a paragraph about migration versions and where they are stored somewhere.
  • I'm not sure, this feels like a technical detail that's best left for the migrations docs :question:

Real new content:

• Switch to using meteor shell instead of env vars if you're running locally, even with --production :+1:
• "For this reason, the migrations package allows you to specify a down() function and set MIGRATION=x to migrate back to version x." we didn't use env vars to control migrations before this point - it's probably worth it to have an example of migrating down from meteor shell. :+1:
• Is it a good idea to back up your database before a complex migration? I feel like that's what I would do, but maybe it's not feasible? :+1:
• It could potentially be a big problem that the collections go through collection2, since the schema could be different than when you wrote the migration initially :+1:

[stubailo]

Data loading notes:

• It sure would be nice to have some kind of diagram or video about publications :arrow_down:
• We might not need it immediately, but it might be good to have a section about subscription life cycle just like we have for methods. I don't even know all of the things that happen when you subscribe (live queries being initialized, when the ready state happens, merge box, etc) :+1:
• In the place where we recommend loading data inside templates, it's important to mention that you should stop subscriptions when you're not using them, and the easiest way to do that is to tie the subscription life cycle to the template that is using the data. When the user navigates away from that view, the subscription is stopped and the data unloaded, saving valuable server resources! :+1:

Stopped at "fetching data"

[tmeasday]

Method nodes:

• The code snippet defining the method here http://guide.meteor.com/methods.html#advanced-boilerplate doesn't actually ever define the method :white_check_mark:
• Form example is kind of weird:
  • Array of error messages but code doesn't call push or anything :white_check_mark:
  • Dotted template names :white_check_mark:

[tmeasday]

Accounts notes:

• needs a SS of accounts UI :white_check_mark:
• throwing errors from validateNewUser :white_check_mark:

[sashko: addressed. the validateNewUser thing might not actually be relevant since useraccounts does validation for you, so you don't need to use it if you're using useraccounts.]

[tmeasday]

Blaze notes:

• need to complete example http://guide.meteor.com/blaze.html#composition :+1:

[tmeasday]

Security notes:

• XXX: about explaining validated method http://guide.meteor.com/security.html#validated-method :white_check_mark:
• XXX: about sikka http://guide.meteor.com/security.html#rate-limiting :white_check_mark: (removed, we can always add it later)
• Text about "passing in a filter" seems weirdly the same as "passing in fields": http://guide.meteor.com/security.html#publication-options :white_check_mark: :arrow_down: (added more explanation, let's talk about this one)
• Security checklist :arrow_down: should we finish this? For some reason I feel like this should wait until later.

[tmeasday]

Deployment notes:

• Use a screenshot that actually shows deployment w/ multiple containers :+1:

[tmeasday]

Build system notes:

• XXX Note about bower :white_check_mark: Removed for now, we can add it later if we need to
• NPM 1.2 ? :white_check_mark: added meteorhacks:npm for now
• XXX: callbacks from NPM (content is in unmerged package article) :white_check_mark: moved
• XXX: Typescript :white_check_mark: removed, we can add it later
• XXX: angular templates :white_check_mark: added short content, linked to tutorial

[stubailo]

Routing notes:

• What should the appBody template be called? listsShowPage? listsShow? forceLoggedIn? :arrow_down:
• Should we rename our routes? :arrow_down:
• listShowPage code sample needs to be rewritten :+1:
• Link to "template as block helper" section in Blaze article :+1:
• Server-side routing should also link to Restivus, which is in many ways a more complete/customizable solution compared to simple:rest. :+1:
• Server side routing should link to the right part of methods
  • There is no right part right now..? :question:

[stubailo]

UI Notes:

• The first paragraph starts with "Regardless of the rendering library that you are using", I think it would be better to start off mentioning Blaze, React, and Angular. In the future we should perhaps link to resources to learning each, and maybe even talking about how to pick one. :+1:
• "styleguide" or "style guide"? It feels really weird seeing that as one word. :+1:
• The smart component section just shows the HTML of the listsShowPage, which is not the interesting part. We should include an analysis of the data loading, which is in the JS code. :+1:
• Could use some comments in both of the the long code snippets in the "pagination controller pattern" section :+1:
• Galaxy screenshot has meet-eeyore in the URL :arrow_down:

[stubailo]

Blaze notes:

• About using data context in template helpers, we say: "This can be hard to reason about, so it’s often a good idea to instead pass the required data into the helper as an argument." - in that case, why do we do it in Todos and in the first example? Perhaps we should change the code. :+1:
• Example for passing keyword arguments in the template inclusion section uses a code snippet which no longer exists in the example app :+1:
• Propose renaming "helpers in tags" to something like "attribute helpers" :+1:
• XXX: we are violating our own rule here and reading into the sub-component :+1:
• I'm not a big fan of the name "utility library" - this seems to encourage just having a big "utils.js" file that has all of your complex stuff :+1:

[stubailo]

Deployment notes

• Modulus section says "see below" for setting up a custom database, but I can't find anything about that in the article :+1:
• I feel like we could make Galaxy more prominent - right now it looks like just one of 5 options, we should make it look like the most obvious choice, because it is :+1:

[stubailo]

Build tool notes

• Temporarily removed note about Bower, should put it back later
• Made a note that NPM will be seamless in 1.3, mentioned meteorhacks:npm for now
• Removed typescript for now, pending Meteor 1.3 and talking to Uri
• Moved the NPM callback content into this article

[stubailo]

Data loading notes:

• First code snippet: "In this particular example, the subscription is initialized when the app starts and never stopped" this code sample actually doesn't have a subscription. Perhaps we should add one. :+1:
• We don't have a CSS style for "notes" (technically, block quotes...) we should consider adding it soon but it's not a blocker :arrow_down:
• "subscribing to data" section has no code snippet :+1:
• I think we should rename "Organizing subscriptions" to "subscribe in UI components" :+1:
• Reorganized headings, Tom should look over it :+1:

[stubailo]

Method notes:

• Added a note about future forms article

[stubailo]

Notes from call with Tom:

• Sashko should re-read the denormalization section/migration section to see if the “real new content” has been added
• Tom will add a section about subscription life cycle - merge box and whatnot - and get it checked with someone else, probably Glasser :+1:
• Also, something about stopping subscriptions :+1:
• Let’s think about which diagrams we need for the final release
• Use a callback in the composition example :+1:
• Add a point about whitelisting keys on filters passed from the client
• Finish up the security checklist, and figure out what to do about the things that aren’t mentioned anywhere else
• Fix deployment screenshots, black out URL :+1:
• Tom should read over new block of content about NPM and callbacks :+1:
• New template names: :+1:
  • Lists_show_page
  • Lists_show
  • App_forceLoggedIn
  • App_body
• Route names :+1:
  • Lists.show
  • App.home
• Some subscription names in routing article are not correct - lists/public :+1:
• Rename styleguide to style guide :+1:
• Make explicit recommendation to avoid data context in helpers :+1:
• Sashko to write block quote CSS

Plan

• Soft launch week of Jan 4?
• Tom to write initial stab at blog post
• Get Tim to tell Sashko how to finish article

[tmeasday]

Build system

add something about cosmos:browserify for now?

[stubailo]

Tasks for Sashko, to discuss during meeting with Zol 1/4/16:

• [ ] Methods and HTTP API, link to it from server side routing
• [x] https://github.com/meteor/todos/issues/64
• [ ] Launch Atmosphere markdown fix :question:
• [x] Edit blog post
• [x] Add something about cosmos:browserify to NPM section? Move out of React guide?
• [x] Update Guide landing page
• [x] Move contributing content to README
• [x] Update Todos app README
• [x] Finish security checklist
• [x] Investigate fix for Atmosphere markdown (Zol?)
• [x] Fix naming to match code style guide in Todos app
• [x] Update code snippets in Guide with field reactivity from Todos app
• [x] Remove modulus, move free hosting up, talk to Ryan
• [x] Go over all of tom's changes since Sashko went on Vacation
• [x] Re-read denormalization and migrations sections
• [x] Talk about whitelisting filter keys passed from client
• [x] Write block quote/side note CSS
• [x] What to do about code style article :question:
• [x] Edit subscription lifecycle section

[stubailo]

Launched! Blog post going out tomorrow morning.