Permalink
Commits on Feb 9, 2017
  1. Fix a typo in the guides

    chasenlehara committed on GitHub Feb 9, 2017
Commits on Feb 8, 2017
  1. Merge pull request #3004 from canjs/version-migration-guide

    Version the install commands in the Migration guide
    chasenlehara committed on GitHub Feb 8, 2017
  2. Version the install commands in the Migration guide

    If you run `npm install canjs --save` in a 2.3 project, it’ll just install the latest version of 2.3, not CanJS 3.
    chasenlehara committed on GitHub Feb 8, 2017
Commits on Jan 10, 2017
  1. Add info about the StealJS plugins configuration required for steal-s…

    …tache to the Migration Guide
    
    Fixes #2938
    chasenlehara committed Jan 10, 2017
Commits on Dec 21, 2016
  1. Make the Migration Guide code examples more consistent by using tabs …

    …instead of spaces
    chasenlehara committed Dec 21, 2016
  2. Use a specific snapshot for all of our JS Bins

    Some of the links to JS Bin were for the latest version of the code, not a snapshot, so if the code changed, other users would see those changes.
    chasenlehara committed Dec 21, 2016
  3. Outline changes that can be made before moving to CanJS 3

    Fixes #2460
    chasenlehara committed Dec 21, 2016
Commits on Dec 20, 2016
  1. Add a description to the Migration Guide

    chasenlehara committed Dec 20, 2016
  2. Improve the Migration Guide’s structure

    Fixes #2920
    chasenlehara committed Dec 20, 2016
Commits on Dec 19, 2016
  1. Fix a broken link on the Mission page

    Fixes #2906
    chasenlehara committed Dec 19, 2016
  2. Replace v3.canjs.com with just canjs.com

    Fixes #2859
    chasenlehara committed Dec 19, 2016
  3. Add a mapping between 2.3 paths and the new modules

    First step to incorporating all of the info from https://gist.github.com/ccummings/cf3122a67619fc0eabd1501480c009ba
    chasenlehara committed Dec 19, 2016
Commits on Dec 18, 2016
  1. Merge branch 'master' into docs-updates

    chasenlehara committed Dec 18, 2016
Commits on Dec 15, 2016
  1. Fix the command for installing all of can-core

    We weren’t including `can-stache-bindings` in the list of modules to install to get all of can-core.
    
    Related to http://forums.donejs.com/t/clicking-element-doesnt-fire-click-event/509
    chasenlehara committed Dec 15, 2016
Commits on Dec 13, 2016
  1. Fix some issues in the Chat guide

    Related to #2867
    chasenlehara committed Dec 13, 2016
  2. Fix some issues in the TodoMVC guide

    The biggest change in this commit is not using the generic API names in the descriptions that appear before the code changes.
    
    Here’s an example of a sentence that appeared previously:
    
    > Use `{{#each expression}}` to loop through every todo.
    
    With this commit, the following is displayed:
    
    > Use `{{#each todos}}` to loop through every todo.
    
    The code still links to the API docs and it makes it easier for readers to connect the sample code with the description.
    
    Related to #2867
    chasenlehara committed Dec 13, 2016
  3. Clean up the ATM guide

    Fixes #2894
    chasenlehara committed Dec 13, 2016
Commits on Dec 12, 2016
  1. Fix various documentation issues

    Related to #2867
    chasenlehara committed Dec 12, 2016
Commits on Dec 6, 2016
  1. Minor consistency, punctuation, spelling, & grammar fixes/improvements

    chasenlehara committed Dec 6, 2016
Commits on Dec 3, 2016
  1. Make the JS Bin embed URLs protocol relative

    Fixes #2832
    chasenlehara committed Dec 3, 2016
  2. Add instructions for requiring stache templates for Browserify users

    An npm package called `stringify` is used to `require()` the template files.
    
    Fixes #2843
    chasenlehara committed Dec 3, 2016
  3. Add webpack instructions to the “Setting up CanJS” guide

    Fixes #2841
    chasenlehara committed Dec 3, 2016
Commits on Nov 30, 2016
  1. Second draft of the Technical Highlight’s Models section

    Related to #2496
    chasenlehara committed Nov 30, 2016