I tried to start over by exiting Mac Terminal. Reopened, changed to my project directory, then typed in foundation watch and am now getting a new error message:
Jays-Mac-Pro:cdndelivery jay$ foundation watch
 
> foundation-sites-template@1.0.0 start /Users/jay/Dropbox/Websites/cdndelivery
> gulp
 
module.js:549
    throw err;
   
 
Error: Cannot find module 'gulp-cli'
    at Function.Module._resolveFilename (module.js:547:15)
    at Function.Module._load (module.js:474:25)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/Users/jay/Dropbox/Websites/cdndelivery/node_modules/.bin/gulp:3:1)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
Error: foundation-sites-template@1.0.0 start: gulp
Exit status 1
    at EventEmitter.<anonymous> (/usr/local/lib/node_modules/foundation-cli/node_modules/npm/lib/utils/lifecycle.js:217:16)
    at emitTwo (events.js:126:13)
    at EventEmitter.emit (events.js:214:7)
    at ChildProcess.<anonymous> (/usr/local/lib/node_modules/foundation-cli/node_modules/npm/lib/utils/spawn.js:24:14)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:925:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
 
Jays-Mac-Pro:cdndelivery jay$ 
 
I get the same error message if I try npm start.
 
I've made several attempts to get this working and hope to get to work soon on my new project. Can I hire someone to do a screenshare over the phone with me and get the latest version of Foundation with Sass installed correctly on my Mac? I'm using macOS 10.14.5 and Coda 2.7.3 as my code editor.

Thank you Val.

@charles see the fix that @rafi posted. It has a js file you add to all pages that use tabs. Works fine. Back browse reverses you through each tab selected then to previous page.

@Knight - sounds like you've got some experience and are doing some great things with v6. Would you consider creating some video training or hosting a webinar to teach others how to use these advanced tools and techniques? I for one would be interested and even open to making a reasonable donation for access to some video training. 

Can someone from Zurb share their thoughts on this conversation? Some of us made significant investments into large projects where we chose the Foundation framework. So far, my experience with version 6 has been very challenging at best. I appreciate that 6 has some new features and is faster and lighter but we can't throw away our investments in V5 and recode- especially when we have to figure it out on our own and are getting little help on the issues we are running into in v6.
Could there not be an option for v6 that is backward compatible to v5? What will future upgrades look like? Will we have to redo a v6 project to use v7 when that happens? When will v5 be retired forcing users to get to at least v6? These are real business issues that need to be considered for those who have large or complex mission-critical income producing projects.
I evaluated Twitter Bootstrap and Foundation 5 when looking for a responsive framework and chose Foundation 5. It is a great framework and I like some of the features of v6. I am finding it very hard though to get support for v6 and am concerned about making further investments into this framework due to recent support issues and potentially upgrade issues if we are to expect this in future releases. 
There is probably a lot I don't know or understand but that is kind of the point. Documentation and support go a long ways to help us make informed decisions. What say you Zurb?

This appears to be a bug from Foundation 6.0.3 (resolved in current release) which Yetti seems to be currently installing (at least as of 5/30/16) rather than the current Foundation 6.3.x version.

This appears to be a bug from Foundation 6.0.3 (resolved in current release) which Yetti seems to be currently installing (at least as of 5/30/16) rather than the current Foundation 6.3.x version.

I updated the Foundation code to a more current version, which has resolved several bugs, however I was not able to do that through Yetti. I used the "Download Everything" option from the Foundation 6 page:
http://foundation.zurb.com/sites/download.html/
The css and js folders are structured differently so had to change the paths for loading the appropriate resources into each page <head> and the js before the </body>.
However, I've lost the ability to use Sass which is very important to this project. I am not able to use the command line tools to install or update a Foundation 6 project configured with Sass due to the numerous error messages I get on the command line that I do not understand. My understanding is that Yetti was created to remove the complexity of that for those of us who need an easier solution to configure Sass for Foundation.
 

I was not able to use Yetti to get to a more recent version of Foundation; however, I was able to update to the current version using the basic css and js without the Sass. This did resolve the Sticky problem. I hope to be able to use Sass so have opened a different Forum request to see if Yetti can install a current version of the code instead of 6.0.3. Thank you Brett for catching the version issue.

Understood. Just hard for some small businesses owners that make our living off of sales (not billable IT work) and don't have enough cash for a large IT rewrite. Look forward to working with F6 on new projects though. Thanks for the input Knight.