10 Matching Annotations
  1. Sep 2019
    1. 4Life Innovations web developers have the expertise and experience to advise you on the best CMS development services that should be integrated into your new or existing website.  Contact us today!

      4Life Innovations web developers have the expertise and experience to advise you on the best CMS development services that should be integrated into your new or existing website. Contact us today!

  2. Mar 2019
  3. Feb 2019
    1. If you would like to comment on this story or anything else you have seen on BBC Culture, head over to our Facebook page or message us on Twitter.

      So sad to see that they've abrogated their responsibility for comments on their site to Twitter and Facebook

  4. Dec 2018
    1. And while content analytics tools (e.g., Chartbeat, Parsely, Content Insights) and feedback platforms (e.g., Hearken, GroundSource) have thankfully helped close the gap, the core content management experience remains, for most of us, little improved when it comes to including the audience in the process.
  5. Nov 2017
    1. an environment unlike anything they will encounter outside of school

      Hm? Aren’t they likely to encounter Content Management Systems, Enterprise Resource Planning, Customer Relationship Management, Intranets, etc.? Granted, these aren’t precisely the same think as LMS. But there’s quite a bit of continuity between Drupal, Oracle, Moodle, Sharepoint, and Salesforce.

  6. Jun 2015
    1. ability to deploy in a variety of learning environments due to the diversity of implementation approaches that schools utilize .

      Again, LTI is key here. We want to be able to integrate/interoperate with lots of L/CMSs.

  7. Jan 2014
    1. We use @Caolan's excellent Async library. Our code is not 5 level deep nested callbacks. We currently have about 45,000 lines of Javascript in our main repository. In this code base, we have used the async library as our only flow control library. Our current use of the library in our code base: async.waterfall: 74 async.forEach: 55 async.forEachSeries: 21 async.series: 8 async.parallel: 4 async.queue: 3 I highly suggest, that if you are unsure about Node.js and are going to do an experiment project, make sure you use Async, Step, or one of the other flow control modules for your experiment. It will help you better understand how most larger Node.js applications are built.

      Considerations for building on Node.js

    2. We decided to make a spreadsheet of the possible environments we would consider using for our next generation product. The inputs were: Community Velocity Correctness (aka, static typing-like things) Debuggability/Tooling Downtime/Compile Time Libraries (Standard/External) Testability Team Experience Performance Production We setup the spreadsheet so we could change the weight of each category. This let us play with our feelings, what if we only cared about developer velocity? What if we only cared about testability?

      Good considerations for selecting a platform.