Giters

artshec / squirrel-u

A learning system powered by GitHub Pages

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

squirrel-u

This project is the home for all squirrel-u contributions.

What is squirrel-u?

squirrel-u is a starter kit for growing your own learning tree within your company.

Why squirrel-u?

Acorns feed Squirrels, can be buried (and forgotten) or planted to become Oak trees, which beget more Acorns.

Developers and teams are hungry for knowledge. Knowledge is formed around a few Acorns and grows into diverse branches of expertise through study, practice and sharing with others.

The internet provides a rich "food supply" for widely available tech topics new and old. However some technical information cannot be found via Google or stackoverflow.com:

  • product architecture,
  • internal systems,
  • domain knowledge,
  • coding practices,
  • release procedures
  • technologies as applied

As organizations grow, this unique information evolves and becomes tribal knowledge.
Tribes repeatedly share via word of mouth and email. At some tipping point, conscientious people put these bits into Powerpoint or Word documents and load into Sharepoint or Jive.
Sadly from that point these documents become hard to find and are rarely maintained.

squirrel-u is a packaged framework for helping teams transform tribal knowledge into learning trees. It is based on GitHub Pages and Markdown. It utilizes a collaborative workflow to build documentation and delivers a consolidated information view and search capability.

GitHub Pages does a beautiful job of rendering Markdown content into html and serving it from your Repository site.

Contents

This package comes with Setup, Framework and Sample Content:

  1. setup - IntelliJ setup of Ruby, local Jekyll
  2. framework - Bootstrap, lunr search, jQuery based hierarchy navigator
  3. sample content - serves as further documentation on all of the above topics.

Getting Started

  1. Fork a copy of the squirrel-u repository to your public GitHub Account: https://github.com/zippyzsquirrel/squirrel-u.git

  2. Select the gh-pages branch instead of master.

  3. Read and experiment with repository content directly in your GitHub fork.

  4. View your content at: http://zippyzsquirrel.github.io/squirrel-u/

Advanced: IDE with Local Jekyll Server

Once you've got the hang of things, you may want to create and maintain content from your IDE and serve it locally for testing. We provide a setup for IntelliJ's IDEA; feel free to adapt for your IDE (and contribute it if you are inclined to do so).

###IntelliJ

Prerequisites

  • IntelliJ (Ultimate or Community Edition)
  • IntelliJ Plugins

Setup

  1. Configure IntelliJ VCS to use GitHub (if not already done)

    • Open IntelliJ from any new or existing project
    • Open Preferences -> Version Control -> GitHub.
    • Enter url: https://github.com/
    • Specify your GitHub account name and password

  2. Windows Users: Install Git to your machine

  3. Create a new IntelliJ project from Version Control File -> New -> Project From Version Control -> GitHub

Build squirrel-u with Jekyll

  1. Run the appropriate Build Jekyll configuration ( Build Jekyll - Mac or Build Jekyll - Windows )

    • For Windows this expects that Git was installed to C:\Development\Git, if this is not correct you will need to Edit the Run Configurations to change this path.
      • If you do this the Build_Jekyll___Windows.xml will be added to your version control files as changed, just move this to another change list
        (right click and Select Move to Another Changelist) so that you do not check in changes to this file accidentally.
    • On Windows if you do not have Ruby installed and on your path it will be downloaded and the install will be started for you
      • When Prompted install Ruby to C:\Development\Ruby
      • On this same screen check the checkbox for 'Add Ruby Executables to your PATH', this is required and if not done the installation will not behave correctly in further sections.
      • Once this is completed the Ruby Devkit will be downloaded and installed, the path this gets downloaded to should default to C:\Development\Ruby\dev_kit, please verify this when prompted.
      • After the Devkit is installed you will need to close the open terminal window and restart IntelliJ
      • When IntelliJ reloads run Build Jekyll - Windows again, this will finish the Ruby setup

  2. Verify installation worked by running the appropriate Run Jekyll configuration

    • This will run a different shell script and will start the jekyll server. This can take several minutes to run the first time you run it, at the end of it you should see a message in the terminal saying the following:

done in 67.513 seconds. Auto-regeneration: enabled for 'C:/git/squirrel-u' Configuration file: C:/git/squirrel-u/_config.yml Server address: http://127.0.0.1:4000 Server running... press ctrl-c to stop. ```

  1. You can now go to http://127.0.0.1:4000 and see your squirrel-u running locally!

  2. Ensure that your origin's push remotes is setup correctly:

    

    3. 



git remote set-url --push origin https://yourUserName@github.com/yourUserName/squirrel-u.git
```


Visual Studio


Prerequisites



Setup


    

  1. 

    Configure Visual Studio Source Control to use GitHub  (if not already done)
    

      

    • Open Visual Studio from any new or existing project
      • 

    • Open Tools -> Options -> Source Control -> Plug-in Selection
      • 

    • Select Microsoft Git Provider
      • 

    • In Team Explorer Home, select Settings -> Git Settings
      • 

    • Enter your user name, email address, and default repository location
      • 

    

    2. 

  2. 

    Windows Users:  Install Git to your machine
    

    3. 

  3. 

    Clone the forked repository to a local repository by doing the following
    

      

    1. Click the Connect to Team Projects icon on the Team Explorer pane 
      2. 

    2. Expand the Clone drop down under Local Git Repositories
      3. 

    3. Fill in the URL for the forked repository.
      4. 

    4. Fill in the directory where you want the local repository placed. THIS DIRECTORY SHOULD NOT EXIST YET
      5. 

    5. Click Clone to create the local directory and clone the repository.
      6. 

    

    4. 

  4. 

    Create a new Visual Studio project from Existing Code
File -> New -> Project From Existing Code
    

      

    • Select any project type you want, this does not effect the outcome, Click next.
      • 

    • Specify the project details as follows:

        

      • Where are the files?: Navigate to the location of the local repository
        • 

      • Name: Name the project as you see fit.
        • 

      • Output Type: Class Library
        • 

      

      • 

    • Click Finish
      • 

    

    5. 



Build squirrel-u with Jekyll


    

  1. 

    Open a command window and navigate to the local squirrel-u repository.
    

    2. 

  2. 

    Enter the command C:\Development\Git\git-bash.exe solutiondir/setup/scripts/runJekyllGrunt.sh, where <solutiondir> is the directory where your squirrel-u fork resides.
    

      

    • For Windows this expects that Git was installed to C:\Development\Git, if
this is not correct you will need to Edit the Run Configurations to change
this path.

        

      • If you do this the Build_Jekyll___Windows.xml will be added to your
version control files as changed, just move this to another change list
        
(right click and Select Move to Another Changelist) so that you do not
check in changes to this file accidentally.
        • 

      

      • 

    • On Windows if you do not have Ruby installed and on your path it will be
downloaded and the install will be started for you

        

      • When Prompted install Ruby to C:\Development\Ruby
        • 

      • On this same screen check the checkbox for 'Add Ruby Executables to
your PATH', this is required and if not done the installation
will not behave correctly in further sections.
        • 

      • Once this is completed the Ruby Devkit will be downloaded and
installed, the path this gets downloaded to should default to
C:\Development\Ruby\dev_kit, please verify this when prompted.
        • 

      • After the Devkit is installed you will need to close the open
terminal window and restart IntelliJ
        • 

      • When IntelliJ reloads run Build Jekyll - Windows again, this will
finish the Ruby setup
        • 

      

      • 

    

    3. 

  3. 

    This can take several minutes to run the first time you run it, at the
end of it you should see a message in the terminal saying the following:
    

    done in 67.513 seconds.
Auto-regeneration: enabled for 'C:/git/squirrel-u'
Configuration file: C:/git/squirrel-u/_config.yml
Server address: http://127.0.0.1:4000
Server running... press ctrl-c to stop.

    

    4. 

  4. 

    You can now go to http://127.0.0.1:4000 and see your squirrel-u running locally!
    

    5. 

  5. 

    Ensure that your origin's push remotes is setup correctly:
    

    

    6. 



git remote set-url --push origin https://yourUserName@github.com/yourUserName/squirrel-u.git
```


Running squirel-u on IIS instead of GitHub Pages


    

  1. Install Node.js and Grunt.js on the IIS server where you want to serve the squirrel-u website.
    2. 

  2. Install Jekyll on the IIS server where you want to serve the squirrel-u website by following the directions here.
    3. 

  3. Set up a static website on your IIS server by following the directions on TechNet.
    4. 

  4. Configure an automated, or manual, deployment process that will publish the squirrel-u files to a directory of your choice on you IIS server.
    5. 

  5. Edit the Gruntfile.js file in your squirrel-u solution so that the text "_site", in the shell:jekyllBuild task is replaced with the path to the root directory of the static website you set up.
    6. 

  6. Create a windows task that runs on startup to run the command "path-to-squirrel-u-files/grunt squirrelWatch" where <path-to-squirrel-u-files> is the directory of the location where the squirrel-u files are published to your IIS server in step 2.
    7. 

  7. Now any changes that are published to the website's folder on the IIS server will trigger a Jekyll build that pushes all the updated HTML files from the build to the root directory of your static website. After the build completes, navigating to the website via a browser will display the updated site.
    8. 



Contributors


A big thanks to the following folks who've helped shape the ideas and content that went into this repository:


    

  • Jim Fox
    • 

  • Melissa Mosser
    • 

  • Maria Jeannet
    • 

  • Dan Ben
    • 

  • Isaac Higgins
    • 

  • Michael Lively
    • 



Contributing


If you like this repository and would like to help make it even better, feel free to create an issue
or submit a pull request with changes.


About
A learning system powered by GitHub Pages
License:Apache License 2.0
Languages
Language:CSS 49.9%Language:HTML 22.3%Language:JavaScript 17.1%Language:Shell 5.9%Language:Ruby 3.5%Language:GCC Machine Description 0.7%Language:Batchfile 0.5%