WPservice DEVELOPMENT STUDIO PRESENTS
LONG-TERM GROWTH
We always design our websites with your future success in mind, carefully planning and optimizing all content to ensure maximum visibility and long-term profitability

How to Install and Configure Bootstrap HTML Template on WordPress Site

After creating a responsive landing page, when getting ready to install WordPress template material, users need to access the FTP to the root of their domain. Assuming that the WordPress structure itself is alreadyserv installed, navigate to the wp-content section from the root directory of the site FTP. In order to do this its assumed that users have a basic command of the method by which this directory system functions. Being able to work with FTP functions and commands is sort of necessary to get this set up.

 Uploading and Customizing the Code

Once the wp-content section is accessed, users will need to:

  •  Navigate to the themes section
  •  Create a new folder called wpbootstrap
  •  Paste the bootstrap folder inside of it
  •  Create a new file inside called index.php
  •  Copy in a static HTML page
  •  Creat a new file in the folder called style.css
  •  Add in the standard theme comment, since the WordPress installation will draw information from what’s written there
  •  Upload an image that will appear in the WordPress admin area that matches around 300×225 pixels named screenshot.png

Once these steps are finished, administrators are finally able to start actually building the theme. Click activate under the WP Bootstrap theme to make it live. Now the HTML needs to be worked on. It might be best to install something like the Test Drive plug in if this is being installed on a live site, so that errant users don’t go exploring and find a nonfunctioning site. Working on a private domain shouldn’t matter, though, if users are already blocked out from it. While accessing the site shouldn’t cause any trouble, it might look awkward to those not associated with the project.

Take the HTML that would often be included at the top of each page and copy it into the header.php file so that it acts as the theme for everything. Individuals who know how to install WordPress template material can add the basic row and column definitions between the:

 <?php get_header(); ?>
 and
 <?php get_footer(); ?>

Find the links everywhere to the CSS files in the header and change them over to:

 <!-- Le styles -->
<link href="<?php bloginfo('stylesheet_url');?>" rel="stylesheet">

Then add the following to the style.css sheet:

 @import url('bootstrap/css/bootstrap.css');
@import url('bootstrap/css/bootstrap-responsive.css');
body {
     padding-top: 60px;
     padding-bottom: 40px;
}

Naturally there are countless customizations that could take place here; these are only examples of what could potentially be done. Those trying to work with some advanced material, like the wordpress mailchimp plugin, might have trouble if they don’t have a hook that allows developers to add CSS or Javascript to the site. Mailchimp and plenty of others balk, so its best to do this. As a result the header.php file needs:

 <?php wp_enqueue_script("jquery"); ?>
    <?php wp_head(); ?>
  </head>
  <body>

It might be best to add support for some HTML5 elements as well with the

 <script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>

line.

 Working on Custom Installations

Consumers working with these kinds of installations have literally hundreds of options when it comes to customizing WordPress HTML code when making Bootstrap themes. They can probably do pretty much anything when it comes down to it. Users who are concerned that they might have too many options for them can certainly choose from a vast variety of pre built functions. These WordPress services are helpful because they’re already put together and look professional. Color and font tags can always be changed, but make sure to do so from the highest-level header file possible. This will help to ensure that the WordPress site looks nice and uniform across every single page. There’s no reason to do this on each individual site when working with a site-wide HTML installation like this, after all.

Comments are closed.