# Manifest file for the template this file is included with: Route66_ProBlue_2dot3_v001
#
# List of all CDN and fixed files in subdirectories to be used, such as:
#       Template specific overrides in a CSS file (must be in subdirectory for template)
#       CDN content for javascript & CSS frameworks like: Bootstrap, Materialize, Font-Awesome, etc.
#
# Add any variables or widget overrides you need
#
# To copy this template, you must edit this file and change all instances of
# 'Route66_ProBlue_2dot3_v001' to the new name, which is also used as the template directory name.
#
# Variables staring with $mgr_ are used only in the manager sections.
#
# Any upgrades to the same tmplate need to have a different version number. For example, if
# the version is 001, then the next version would be 002 and the name would change from
# Route66_sample_Green_2dot3_v001 to Route66_sample_Green_2dot3_v002 in all the hash keys below (the names with no spaces).
#
#######################################################################
#
# REQUIRED FILES LIST
#
#
# store_header.tpl
# store_footer.tpl
# store_checkout_header.tpl
# store_checkout_footer.tpl
# index.html (blank or with error message and optional forwarding to store home page)
#
#
# template_widgets.inc
# Contains HTML widgets and other HTML code that are generally dependent on CSS framework tags.
# You can override any other default widgets or HTML with your own code and CSS tags.
# If disabled, the defaults are used if they exist.  See documentation for those widgets that are required in this file.
# If overriding a default widget or variable (those that start with a dollar sign), make sure to copy widget variables names, tokens, and code styling to ensure proper operation.
# Last line of file must be: 1;
# REQUIRED. File must be at same location as headers & footers and named: template_widgets.inc
# See the agora_html_widgets.pl file for other widgets you may override within template_widgets.inc.
#
#
# template.css
# Contains any additional CSS your design/template needs OR CSS frame work overrides you wish to provide.
# Leave completely blank if not needed.
# Optional. Named template.css and located in same directory as the headers/footers.
#
#
# template.js
# Contains any additional javascript code your design/template needs.
# Leave completely blank if not needed.
# Optional. Named template.js and located in same directory as the headers/footers.
#
#
# template_homezone.inc
# Widgets that are available for the home page (and other static pages) via the use of widget tokens defined for each widget.
#
#
# eng_us-mgr_lang.inc (for all iso languages supported by your template: eng_uk, etc)
# Language specific items for the manager for the template & template managers.
# Include a manager language file for all iso languages supported by your template: eng_us, eng_uk, etc.
#

################################################################################
#######   Template ID & Directory Name used in Template Manager   #######
################################################################################

$mgr_template_id = 'Route66_ProBlue_2dot3_v001'; # should also be name of template directory
$mgr_template_version{'Route66_ProBlue_2dot3_v001'} = '06.6.00.000';

# CSS frameworks, some for future expansion.
# Chooses which framework centric directory to use for many templates.
# boot3 = bootstrap 3.x legacy
# boot4 = bootstrap 4.x, boot5 = bootstrap 5.x, boot6 = bootstrap 6.x
# mat1 = materialize 1.x, mat2 = materialize 2.x, mat3 = materialize 3.x
$mgr_template_framework = 'boot3';


################################################################################
#######   Template Widget Zones   #######
################################################################################

# separate each zone with a pipe (|) character
# Zone1:
# Zone2:
# Zone3: Left Column - Top
# Zone4: Left Column - Mid to Bottom
# Zone5: Main Content (Horizontal) - Top
# Zone6:
# Zone7: Right Column - Top
# Zone8:
# Zone9:

$mgr_template_zones_used = 'Zone3|Zone4|Zone7';


################################################################################
#####    Widget Information for Store Manager     #####
################################################################################

# Any new, that are not pre-existing widgets, outlined in your template_widgets.inc file
# must have the following information supplied as a single string, separated by a pipe (|) character:

# 1. key name for each widget listed/defined within your template
# 2. Default Title to be Displayed (user can change these later)
# 3. The widget template name to be used. Can be one of ours our one you define.
# 4. The subroutine (aka function) that is called to fill the contents of the widget template
#     This is optional but many widgets need a subroutine to execute if a generic widget template is used.

# The widget string should look like this (and enclosed in single quotes):
#       'keyName|widgetDisplayTitle|widgetTemplateName|subroutineNameIfAny'

# Multiple widget strings must be separated with commas (,) between the quote marks for each string.
# ( place comma between the quote mark for the end of one string, and the quote mark for
# the beginning of the next widget string.)

# Notes:
# You can override any existing widget in your template_widgets.inc file without
# needing to add anything to this list.

# Your Widget Title will only be used if it is the first time using the widget.

################################################################################

# Enter your widget strings inside the ():

@mgr_template_new_column_widgets = ();

@mgr_template_new_horizontal_widgets = ();


################################################################################
#######   HTML Header META tags for this template   #######
################################################################################
#
# Should include character set (charset), viewport, and any other meta items required for your template.
#
$mgr_template_html_header_metatag_charset{'Route66_ProBlue_2dot3_v001'} = q|<meta charset="utf-8">|;

$mgr_template_html_header_metatags{'Route66_ProBlue_2dot3_v001'} = q|
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
|;


################################################################################
#######   Javascript Files To Include   #######
################################################################################
#
# NOTE: some browser security tools block remote scripts not located on your site under the same domain name, even from known CDNs. If this becomes a problem, the files need to b moved to a local location (relative to the store and on the same domain name or site).
#
# These JS files are added to the store footer files just before the closing /body> tag.
# Add all files you need to load, one per line between the pipes: q| and the ending |;
# If a CDN URL enter in https URL (secure mode). Also make sure the manager language files correlate to the file locations.
# If a local JS file included with the template (in same directory as this template), enter '[[LocalFile]]' in the URL followed by a forward slash and the file name.  The system will build the local link for you (do not list the template.js file, it is added after these files automatically by the system, if enabled).
# [[LocalFile]] example: <script src="stylesheet" href="[[LocalFile]]/jquery-9.3.1.slim.min.js"></script>
# If a site JS file included with the cart is needed, enter '[[AssetFile]]' in the URL followed by a forward slash, followed by any subdirectory name and another forward slash (if in a sub-directory), and then end with the file name.  The system will build the link for you.
# [[LocalFile]] example: <script src="stylesheet" href="[[AssetFile]]/jquery/jquery-9.3.1.slim.min.js"></script>
# Normally jQuery is loaded first (if required), so list in the order that the JS files are needed.
# These files are loaded before anything required by AgorCart as well as before the template.js file, if enabled/loaded.
#
# Note: By default, Chrome will reject CDN or remotely hosted javasript that is not on the same domain name (CSS is still okay), so some features will not work properly if you are calling remote JS files.
#
$mgr_template_js_file_group{'Route66_ProBlue_2dot3_v001'} = q|
<!-- jQuery core JS -->
<script src="[[AssetFile]]/jquery/jquery-1.12.4.min.js"></script>
<!-- Bootstrap core JS -->
<script src="[[AssetFile]]/bootstrap/bootstrap-3.3.7.min.js"></script>

<!-- IE10 viewport hack for Surface/desktop Windows 8 bug -->
<script src="[[AssetFile]]/ie10-viewport-bug-workaround.js"></script>
<script src="[[AssetFile]]/offcanvas.js"></script>
|;


# For Reference only - Not Used below....
#<script src="https://code.jquery.com/jquery-3.3.1.slim.min.js" integrity="sha384-q8i/X+965DzO0rT7abK41JStQIAqVgRVzpbzo5smXKp4YfRvH+8abtTE1Pi6jizo" crossorigin="anonymous"></script>
#<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.3/umd/popper.min.js" integrity="sha384-ZMP7rVo3mIykV+2+9J3UJ46jBk0WLaUAdn689aCwoqbBJiSnjAK/l8WvCWPIPm49" crossorigin="anonymous"></script>
#<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.4/popper.min.js" integrity="sha256-buCJtv5E9D2vlgk/iJYywBD8xf1M3lL7mzKJn3Oqa1A=" crossorigin="anonymous"></script>
#<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.5/popper.min.js" integrity="undefined" crossorigin="anonymous"></script>
#<script src="https://stackpath.bootstrapcdn.com/bootstrap/4.1.2/js/bootstrap.min.js" integrity="sha384-o+RDsa0aLu++PJvFqy8fFScvbHFLtbvScb8AjopnFD+iEQ7wo/CG0xlczd+2O/em" crossorigin="anonymous"></script>
# <script src="https://code.jquery.com/jquery-2.2.4.min.js" integrity="sha256-BbhdlvQf/xTY9gja0Dq3HiwQF8LaCRTXxZKRutelT44=" crossorigin="anonymous"></script>


################################################################################
#######   CSS Files To Include   #######
################################################################################
#
# These CSS files are added to the store header files in the header section before the opening body HTML tag.
# Add all files you need to load, one per line between the pipes: q| and the ending |;
# If a CDN URL, enter in https URL (secure mode). Also make sure the manager language files correlate to the file locations.
# If a local CSS framework file included with the template, enter '[[LocalFile]]' in the URL followed by a forward slash and the file name.  The system will build the local link for you (do not list the template.css file, it is added after these files automatically by the system).
# [[LocalFile]] example: <link rel="stylesheet" href="[[LocalFile]]/bootstrap.min.css">
# If a site CSS file included with the cart is needed, enter '[[AssetFile]]' in the URL followed by a forward slash, followed by any subdirectory name and another forward slash (if in a sub-directory), and then end with the file name.  The system will build the link for you.
# [[AssetFile]] example: <script src="stylesheet" href="[[AssetFile]]/bootstrap/bootstrap.min.css"></script>
# These files are loaded before anything required by AgorCart as well as before the template.css file, if enabled/loaded.

$mgr_css_framework_and_font_files{'Route66_ProBlue_2dot3_v001'} = q|
<!-- Bootstrap 3.3.x CSS -->
<link rel="stylesheet" href="[[AssetFile]]/bootstrap/bootstrap-3.3.7.min.css">
<!-- CSS version of FontAwesome -->
<link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.5.0/css/all.css" integrity="sha384-B4dIYHKNBt8Bc12p+WXckhzcICo0wtJAoU8YZTY5qE0Id1GSseTk6S+L3BlXeVIU" crossorigin="anonymous">
|;

# not Used
# <link rel="stylesheet" type="text/css" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css" media="all">
# <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css" integrity="sha384-BVYiiSIFeK1dGmJRAkycuHAHRg32OmUcww7on3RYdg4Va+PmSTsz/K68vbdEjh4u" crossorigin="anonymous">

################################################################################
##### FontAwesome Notes
# AgoraCart currently uses FontAwesome CSS version by default for icons.
# If you do not use FontAwesome JS or CSS versions, make sure you create your own versions of widgets that use your preferred font framework or a different version of FontAwesome, or your own custom CSS styling for all cart HTML Widgets and/or tags using your preferred font framework/styling.
#####
################################################################################


################################################################################
#######   Social Media Icons   #######
################################################################################
#
# For Font Framework or Custom HTML Widgets for Icons:

$mgr_social_media_icons_supported{'Route66_ProBlue_2dot3_v001'} = 'yes';

# Social Media Icon Templates for the header or other areas.
# Each one is enabled/disabled individually by store admin in the manager screens.
$mgr_social_facebook{'Route66_ProBlue_2dot3_v001'} = q|
<li><a href="[[SocialMediaFacebook]]" target="_blank"><span class="fa-layers fa-fw testshadow">
    <i class="fab fa-facebook-f"></i>
    </span></a></li>
|;

$mgr_social_twitter{'Route66_ProBlue_2dot3_v001'} = q|
<li><a href="[[SocialMediaTwitter]]" target="_blank"><span class="fa-fw testshadow">
  <i class="fab fa-twitter"></i>
    </span></a></li>
|;

$mgr_social_linkedin{'Route66_ProBlue_2dot3_v001'} = q|
<li><a href="[[SocialMediaLinkedIn]]" target="_blank"><span class="fa-fw testshadow">
    <i class="fab fa-linkedin-in"></i>
    </span></a></li>
|;

$mgr_social_instagram{'Route66_ProBlue_2dot3_v001'} = q|
<li><a href="[[SocialMediaInstagram]]" target="_blank"><span class="fa-fw testshadow">
    <i class="fab fa-instagram"></i>
    </span></a></li>
|;

$mgr_social_gab{'Route66_ProBlue_2dot3_v001'} = q|
<li><a href="[[SocialMediaGab]]" target="_blank"><span class="fa-fw testshadow">
    <i class="far fa-sm">Gab</i>
    </span></a></li>
|;

$mgr_social_youtube{'Route66_ProBlue_2dot3_v001'} = q|
<li><a href="[[SocialMediaYoutube]]" target="_blank"><span class="fa-fw testshadow">
    <i class="fab fa-youtube"></i>
    </span></a></li>
|;


# Thumbnail image URL location for the template:
# Displayed in the template selection screen (store manager side).
# Can be in template directory (local to cart) or stored on your website or a publicly accessible file sharing location like dropbox, etc.
# Must be HTTPS (secure SSL / TLS accessible). Approved template images are hosted at the AgoraCart.com site.
# Must be no wider than 270 pixels. Best practice: 270x144 size.
$mgr_template_thumbnail_URL{'Route66_ProBlue_2dot3_v001'} = 'https://agoracart.com/template_thumbnails/Route66_ProBlue_2dot3_v001.png';


1;
