I have been told that it is best to create a responsive site from scratch and not using a bootstrap framework such as the twitter one. However the membership script that I am running uses the twitter bootstrap version 3 framework, so I am wondering if there will be any kind of conflict? Or it won’t matter
Can you explain your question a little more clearly, @byronwells? I’m having trouble working out what you mean.
If you are using CSS from more than one source, there is always the risk of conflict, if both are targeting the same classes. But without more information, it’s hard to picture your exact scenario.
I am clearing asking to know if there will be any sort of conflict between codes, bearing in mind my membership script uses Twitter Bootstrap version 3 code to display things and so on… However I have heard from several people that using this type of framework is not a very good idea…
So I am wondering if because the script is coded/running/displaying that framework, I have to still write in that format or not??
That really depends.
Most (all?) frameworks have “conventions” that need to be adhered to in order to get the most benefit from using them.
For example, the folder sub-folder structure might need to be a certain way, certain folders and files might need to have certain names, certain HTML tags might need to be used in certain ways, id and class attributes might need to have certain values. etc.
As long as the conventions are followed, everything should work great.
However, problems begin to arise as soon as deviation from the conventions begins.
For example, a “slider” is added but the HTML it uses is affected by the frameworks CSS rules for those HTML tags.
There are times when using a framework might be a good idea. For example, if I were creating a site that relied heavily on a “grid layout” I might use a “grid” framework that made designing the site easier.
IMHO there are several things to consider when deciding on whether or not to use any given framework.
- how well do you “know” the framework
- how much of it will you actually use
- how much will it get in the way of site customization
- how much time do you have to spend on troubleshooting any conflicts that may arise
I can’t speak for others, but I imagine a reason they said using a framework is not a good idea is because when using one, one needs to have both a very good understanding of the basics, and a very good understanding of the framework.
That, and by the time someone becomes advanced enough in design, there is less need to use a framework that may add unnecessary “bloat” to get the desired results.
It’s often different if you are not the only one working on the project or if you have a tight deadline to meet.
But for a solo designer putting together a one-time site design it is often easier to not use a framework.
Well my membership script use twitter bootstrap version 3…
<nav class="navbar navbar-default mainnav navbar-fixed-top"> <div class="no-side-pad container"> <!-- Brand and toggle get grouped for better mobile display --> <a class="navbar-brand mainnav-logo" href="index.php?page=home"> <img src="http://www.codingforums.com/images/logo-default.gif" class="logo" alt="Logo" width="100%"> </a> <button type="button" class="mainnav-toggle navbar-toggle collapsed " data-toggle="collapse" data-target="#bs-example-navbar-collapse-1"><span class="sr-only">Toggle navigation</span> <span class="icon-bar"></span> <span class="icon-bar"></span> <span class="icon-bar"></span> </button> <!-- Collect the nav links, forms, and other content for toggling --> <!-- Navigation Drop Down Menu Code --> <div class="collapse navbar-collapse navbar-right no-side-pad top-collapse" id="bs-example-navbar-collapse-1"> <ul id="main-menu" class="sm sm-clean top-menu"> <li><a href="index.php?page=contact">Contact Us</a></li><li><a href="index.php?page=faq">FAQ</a></li><li><a href="index.php?page=home">Home</a></li><li><a href="index.php?page=join">Join</a></li><li><a href="index.php?page=login">Login</a></li><li><a href="index.php?page=test">Test</a></li> <!-- This is the header navigation, so this can be re-used in your custom design --> </ul> </div> <div class="clear-both"></div> <!-- END Drop Down Menu Code --> <!-- /.navbar-collapse --> <!-- /.container-fluid --> </div> </nav> <div class="main-container"><!-- start main container --> <div class="container"><!-- start container --> [[ PAGE LAYOUT/STYLING CAN GO HERE ]] </div><!-- end main container --> <div style="clear:both"></div> <footer> <nav class="navbar bottom-nav"> <!-- Brand and toggle get grouped for better mobile display --> <div class="container no-side-pad bottomnav-container"> <div class="navbar-brand bottomnav-logo"><img src="templates/responsive/images/logo-default.gif" class="bottomLogo" alt="Logo" width="100%"></div> <div class="navbar-right bottom-collapse"> <ul class="sm sm-clean bottom-menu" id="footer-menu"> <li><a href="index.php?page=affiliates">Affiliates</a></li> <li><a href="index.php?page=privacy">Privacy</a></li> <li><a href="index.php?page=links">Recommended Links</a></li> <li><a href="index.php?page=affiliatelink">Your Affiliate Link</a></li> </ul> </div> <div class="clear-both"></div> </div> </nav> <div class="main-container1" style="background-color:#300;"> <div class="copyright" style="text-align:center; background-color:#000; color:#FFF;">Copyright 2016 <a href="http://www.unlockingblueprints.com">Unlocking Blueprints</a> - All Rights Reserved</div> </div> </footer>
Do I still need to use it??
Do you need to?
IMHO if you like it and everything is more or less working, you might as well keep it now that you have it.
If you aren’t happy with it, then you could either try to bang things into shape or scrap it and start anew.
Which would be more trouble I can’t say.
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.