DashCore is a Bootstrap 5.x HTML Template ready to showcase your SaaS, Startup, Software or any tech solution. The download includes the complete source files including HTML, CSS, and JavaScript as well as SCSS stylesheets for easy customization.
If you have any questions that are beyond the scope of this help file, please feel free to email us via our user page contact form, or write direct to support@5studios.net, please include your purchase code in order for us to verify you. Thank you so much !!!
The template is organized in the following way:
This template is based on HTML5 boilerplate structure and the latest version of Twitter Bootstrap framework (4.0 Beta). Please visit http://www.getbootstrap.com if you want to learn more about Bootstrap and it components.
The general HTML structure appears in the following format:
<nav class="navbar navbar-expand-md navigation sidebar-left">
<section class="container">
<!-- MENU ITEMS -->
</section>
</nav>
<main>
<header class="heading">
<div class="container">
<!-- HEADING CONTENT -->
</div>
</header>
<section class="section">
<div class="container">
<!-- ALL SECTIONS CONTENT -->
</div>
</section>
<footer>
<div class="container">
<!-- FOOTER CONTENT -->
</div>
</footer>
</main>
This template uses SCSS for stylesheets. For more information about SCSS, visit http://sass-lang.com/guide.
Template SCSS files are located in the /SCSS directory. Vendor CSS files are located in the /html/css directory.
We need to compile SCSS files to CSS to make them usable. All compiled files are located in the /css folder.
All SCSS files are separated by component types for easy customization.
The main file for the theme is dashcore.scss file which has references to all .scss files that compose the theme.
Those files use Bootstrap variables and mixins in order to compile to CSS.
You can modify those files to include additional style or remove any unwanted reference, one use case could be to leave the variation of a section you like and remove references to the others.
Do not remove references to Bootstrap and FontAwesome components as it will not compile.
// User predefined variables, will overwrite any predefined variable
@import "user/variables";
// For compatibility and sharing of styles with another themes of ours
@import "shared/import";
// Importing of any local variable|function|mixins that should be globally accessed
@import "dashcore/import";
// Bootstrap core styles
@import "bootstrap/scss/bootstrap";
// The local theme
@import "shared/styles";
@import "dashcore/styles";
@import "dashcore/shop";
// User custom styles
@import "user/styles";
It's recommended, if you plan to add additional styles other than ours, that you place all of your code in the user/ directory, this is avoid overwritten your styles in future theme updates.
This template uses several JS files. Those files are loaded at the bottom of the page to increase the site speed and rendering.
We have included minified version of those files split in the following way, this way you can opt to include those minified version as you consider.
We use some PHP scripts to process the submission of the forms on the template
Every form in the HTML has an action attribute with the path relative to the PHP file which will process it
<form id="form-contact" action="srv/contact.php" data-response-message-animation="slide-in-up">
...
</form>
By default we left it this way, you can move the files to another location or rename them as you like, if you do that don't forget to update the action attribute to reflect your changes. Please refer to the
forms section for additional details on the file structure and PHP code
We use MailChimp API 3.0 to connect to the service, our implementation only include
Adding a member to a list,
for this sake we create a class in /srv/integration/MailChimp.php file.
We implement this class to make the subscription process in subscribe.php. There you must provide API_KEY and LIST_ID
with your own. We assume you know how to get those values.
define("LIST_ID", "[YOUR LIST ID]");
define("API_KEY", "[YOUR API KEY]");
This is the only change needed to make the script to work.
We explain how easy is to customize the template through HTML, SCSS or JS changes to suit your needs.
We use Google Poppins and Caveat fonts by default.
To change the embedded font, open the HTML page you want and locate the head section and change the font as you wish. Make sure to change the font names in CSS files as well.
<link href="https://fonts.googleapis.com/css?family=Poppins:100,300,400,500,700,900" rel="stylesheet">
<link href="https://fonts.googleapis.com/css?family=Caveat" rel="stylesheet">
Once you have changed the font, look for $font-family-base and $font-family-handwritten variables in /SCSS/shared/import/_bootstrap-overwrite.scss and /SCSS/shared/import/_variables.scss files respectively, make your adjustments properly.
// _bootstrap-overwrite.scss
$font-family-base: "Poppins", sans-serif !default;
// _variables.scss
$font-family-handwritten: "Caveat", cursive, $font-family-base !default;
This template is ready to use any colors scheme, for wich we use SCSS to create colors pallete and process the CSS dynamically and show your colors right away.
You change your colors scheme in /SCSS/shared/import/_palette.scss.
We use 6 main colors for each scheme which can be completely customized to fit your needs.
To include your own colors just change variables to your values and compile.
$color-primary: $color-1 !default;
$color-secondary: $gray-700 !default;
$color-success: $color-3 !default;
$color-info: $color-2 !default;
$color-warning: $color-6-light-2x !default;
$color-danger: $color-auxiliary-light-4x !default;
$color-light: $color-5-light-5x !default;
$color-dark: $gray-900 !default;
$color-gray-light: $gray-400 !default;
$color-gray: $gray-600 !default;
$color-gray-dark: $gray-800 !default;
In addition to the image cover background, each section may include an overlay. There are so many colors of overlays as defined in the colors scheme, all named by its index (.overlay-1, .overlay-2, .overlay-3 and so on).
You can choose the level of opacity 10 to 90 by using the alpha-? css class.
Make sure you have included .overlay class.
<div class="overlay overlay-4 alpha-9">
<!-- CONTENT HERE -->
</div>
DashCore comes with fully functional form submission. Every form has an action attribute, this is the script which will process the form in server side. We have set up those scripts in srv folder.
<form action="srv/subscribe.php" class="form form-subscribe" method="post" data-response-message-animation="slide-in-left">
<input type="text" name="Contact[fullName]"/>
...
</form>
<div class="response-message">
<h4 class="bold"><i class="icon font-md inline fa-envelope-o"></i>One last step!!!</h4>
<small>To complete the subscription process, please click the link in the email we just sent you.</small>
</div>
The name of the inputs should be in array format, for example: Contact[fullName], this way is easier to read on the server, and bind the values into the corresponding model.
The value inside the squared brackets is the name of the attribute in your model, it is case sensitive.
Each script has references to the core libraries we have developed.
// srv/suscribe.php
include('./integration/MailChimp.php');
include('./models/SubscribeModel.php');
// srv/models/SubscribeModel.php
namespace models;
include __DIR__ . '/../components/Model.php';
use components\Model;
All of these references are located relatively to the scripts. You can change the location of the files or rename them, by doing this you must update the files to reflect your changes.
Note how each file has include statements, and how the path is relative to its container, this way PHP knows where to find those references.
Advice response-message-animation="slide-in-left" in the form tag.
This attribute indicates the notification message animation should be when a response is available. If the attribute is present you must provide an element with response-message css class next to the form.
When the response is available the message will replace the form with the animation you indicated. At this time only slide-in-left animation is available, but you can create your owns. __forms.scss is where you may want to create the animations for your forms
As long as we improve and extend the template, some topics may need extra explanation in order for you to fully customize them.
We use the button pointed out bellow as a reference to relocate the page header mockups when the page is viewed on mobile devices.
Perspective mockups for desktop
Perspective mockups for mobile devices
There are several considerations you must attend when customizing this variation
If you would want to remove the .learn-more button, you will need to add another element, preferable within the same section and/or position as the button was.
This is because this element is used as a reference for relocating the mockups.
Code snippet to reposition the perspective-mockups
The code snippets above shows how the .learn-more button is used as a reference to reposition the mockups, so if removed the code will break on line 52
If you change the default css class for this button, please be sure to change it on the javascript as well thus the element can be found and avoid any error or misbehavior.
The following resources were used to create this template. We are much obligated to their developers.
Any Images or logos used in previews are not included in this item or final purchase and you need to contact authors to get permission in case you want to use them in your commercial or non-commercial projects.
For some of them we are allowed to make reference, in case you wanted to use them in your design
The SVG icons you saw in the preview were taken from https://flaticon.com, those icons free to download with attribution, we used the ones in the following links.