Answers.Body: <p>I built <a href="http://www.progress.org" rel="noreferrer"><strong>Progress.org</strong></a> using Craft and Bootstrap—and it only took me about two months of part-time work. I’d say Craft and Bootstrap together are a match made in heaven. Here’s why:</p>
  
  <p>1) Bootstrap is an out-of-the-box template that gives you great flexibility if you want to design your website how <em>you</em> want it to look. I found other frameworks like WordPress overly constraining.</p>
  
  <p>2) Craft allows for near unlimited customizations as long as you know your front-end HTML/CSS.</p>
  
  <p>If you know your HTML/CSS, then a Bootstrap/Craft combination is ideal, in my experience.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-07T05:59:03.407Z
Answers.Text: This answer was flagged as spam, though I'm not entirely sure that it is. _Technically_ it answers the original question. But overly short answers are frowned upon... Would you mind elaborating? **How was your experience combining Craft & Bootstrap?** Good, bad? Any pointers or suggestions you might have for someone attempting this?
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-06T22:45:07.850Z
Answers.LastActivityDate: 2015-06-08T16:27:08.970Z
Answers.LastEditDate: 2015-06-08T16:27:08.970Z
Answers.UserDisplayName: Martin Adams
Answers.Body: <p>Bootstrap strictly refers to the front-end framework used as a starting point. It doesn't provide any back-end functionality so there's no clash with what Craft provides.</p>
  
  <p>EDIT: Now that you've provided more details it sounds like Craft would be a fine solution. It's not hard to take your existing code and integrate it with Craft. The learning curve that you may face based on your self-evaluation of your skillset would be tackling Twig and really understanding how twig works for templating. But we're here to help :)</p>
  
  <p>EDIT pt2: 
  This is a helpful resource: <a href="http://straightupcraft.com/twig-templating" rel="nofollow">http://straightupcraft.com/twig-templating</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-13T15:10:20.817Z
Answers.LastActivityDate: 2014-08-13T16:51:33.740Z
Answers.LastEditDate: 2014-08-13T16:51:33.740Z
Answers.UserDisplayName: Tyler Willingham
Answers.Body: <p>Can you add a little more information? I'm not sure I understand the question.</p>
  
  <p>Bootstrap is a front-end framework, it can be used in combination with Craft. Not necessarily <em>replace</em> it. So you wouldn't be "converting it".</p>
  
  <p>Now if you're referring to converting a static site that uses Bootstrap as its framework, it's going to depend on <em>the needs of the website</em> whether you want to use Craft or not. I've found that Craft works well in many scenarios but there are always exceptions.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-13T15:09:22.243Z
Answers.LastActivityDate: 2014-08-13T15:09:22.243Z
Answers.UserDisplayName: cballenar
Answers.Body: <p>I think it's actually a good idea to first build parts of the site with some static HTML/CSS and later implement the Craft code (in form of <a href="http://twig.sensiolabs.org" rel="nofollow">Twig</a>, the tempting language used by Craft).</p>
  
  <p>You would't need to convert your site for this process, because Craft template files are  normal HTML files with Twig code in-between. Yes, you probably want to refactor your code and the template files a bit, maybe make use of <a href="http://twig.sensiolabs.org/doc/tags/include.html" rel="nofollow">includes</a> and <a href="http://twig.sensiolabs.org/doc/tags/block.html" rel="nofollow">blocks</a> etc., but using a static HTML page as a starting point for your new Craft site can be really helpful.</p>
  
  <p>Oh.. and believe me, while you're learning Craft and about all the features, you'll most likely want to refactor parts of your code more than once. :D</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-13T18:18:02.393Z
Answers.Text: That's my plan. I will build static home page and some generic page templates in HTML/CSS then rebuild in Craft. My concern was Bootstrap talks about "compiled" CSS. My understanding of compiled code is that it's machine readable only. I don't know how I would integrate machine code into Craft. But, having downloaded and poked around Bootstrap, it looks like the CSS files are plain text. I still don't know what they mean by "compiled" CSS.
Answers.UserDisplayName: Henry
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-13T18:34:28.187Z
Answers.Text: They probably mean compiled from SASS or LESS files to CSS. And again, you wouldn't need to rebuild anything, you'd simply add the Twig code to your static site. :D
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-13T17:06:17.683Z
Answers.LastActivityDate: 2014-08-13T17:06:17.683Z
Answers.UserDisplayName: carlcs
Body: <p>Is there any reason you wouldn't want to do this?</p>
  
  <p>EDIT: More info</p>
  
  <p>I have a website that was built in HTML/CSS and over the years, it's been modified, added to and hacked at to the point where the code is kind of a mess. I'd like to redesign the site using a structured CMS but I want the base HTML/CSS to be well coded and optimized. That's why I'm thinking of building a site using the Bootstrap framework and then rebuilding it in Craft. I realize this seems redundant but I'm not good enough with CSS to just build it from the scratch in Craft. I'm more of the cut and paste kind.</p>
  
  <p>The reason I'm considering Craft is because I like the idea of defining fields and sections I can reuse. I built the site 90% through using ModX, it looked good but the back end and the way it presents Template Variables is not very friendly. I like Craft's approach a lot more.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-08-13T16:51:52.097Z
Comments.Text: Updated my answer based on your update
Comments.UserDisplayName: Tyler Willingham
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-10T00:23:29.307Z
Comments.Text: Hi Henry! Could you consider accepting whichever answer was most helpful?
Comments.UserDisplayName: Matt Stein
Tags: <frontend><craft-features>
Title: Has anyone converted a Bootstrap based website to Craft?
ThreadText: # Has anyone converted a Bootstrap based website to Craft?
  
  (Asked by: username_0 on 2014-08-13)
  
  Is there any reason you wouldn't want to do this?
  
  EDIT: More info
  
  I have a website that was built in HTML/CSS and over the years, it's been modified, added to and hacked at to the point where the code is kind of a mess. I'd like to redesign the site using a structured CMS but I want the base HTML/CSS to be well coded and optimized. That's why I'm thinking of building a site using the Bootstrap framework and then rebuilding it in Craft. I realize this seems redundant but I'm not good enough with CSS to just build it from the scratch in Craft. I'm more of the cut and paste kind.
  
  The reason I'm considering Craft is because I like the idea of defining fields and sections I can reuse. I built the site 90% through using ModX, it looked good but the back end and the way it presents Template Variables is not very friendly. I like Craft's approach a lot more.
  
  **Tags:** frontend, craft-features
  
  > **Comments:**
  > **username_1**: Updated my answer based on your update  
  > **username_2**: Hi username_0! Could you consider accepting whichever answer was most helpful?  
  
  ---
  
  ## 4 answers
  
  ### Answer by username_3 on 2015-06-06. Score: 5
  
  I built [**Progress.org**](http://www.progress.org) using Craft and Bootstrap—and it only took me about two months of part-time work. I’d say Craft and Bootstrap together are a match made in heaven. Here’s why:
  
  1) Bootstrap is an out-of-the-box template that gives you great flexibility if you want to design your website how *you* want it to look. I found other frameworks like WordPress overly constraining.
  
  2) Craft allows for near unlimited customizations as long as you know your front-end HTML/CSS.
  
  If you know your HTML/CSS, then a Bootstrap/Craft combination is ideal, in my experience.
  
  > **Comments:**
  > **username_4**: This answer was flagged as spam, though I'm not entirely sure that it is. _Technically_ it answers the original question. But overly short answers are frowned upon... Would you mind elaborating? **How was your experience combining Craft & Bootstrap?** Good, bad? Any pointers or suggestions you might have for someone attempting this?  
  
  ---
  
  ### Answer by username_1 on 2014-08-13. Score: 2
  
  Bootstrap strictly refers to the front-end framework used as a starting point. It doesn't provide any back-end functionality so there's no clash with what Craft provides.
  
  EDIT: Now that you've provided more details it sounds like Craft would be a fine solution. It's not hard to take your existing code and integrate it with Craft. The learning curve that you may face based on your self-evaluation of your skillset would be tackling Twig and really understanding how twig works for templating. But we're here to help :)
  
  EDIT pt2:
  This is a helpful resource: <http://straightupcraft.com/twig-templating>
  
  
  ---
  
  ### Answer by username_5 on 2014-08-13. Score: 1
  
  Can you add a little more information? I'm not sure I understand the question.
  
  Bootstrap is a front-end framework, it can be used in combination with Craft. Not necessarily *replace* it. So you wouldn't be "converting it".
  
  Now if you're referring to converting a static site that uses Bootstrap as its framework, it's going to depend on *the needs of the website* whether you want to use Craft or not. I've found that Craft works well in many scenarios but there are always exceptions.
  
  
  ---
  
  ### Answer by username_6 on 2014-08-13. Score: 1
  
  I think it's actually a good idea to first build parts of the site with some static HTML/CSS and later implement the Craft code (in form of [Twig](http://twig.sensiolabs.org), the tempting language used by Craft).
  
  You would't need to convert your site for this process, because Craft template files are normal HTML files with Twig code in-between. Yes, you probably want to refactor your code and the template files a bit, maybe make use of [includes](http://twig.sensiolabs.org/doc/tags/include.html) and [blocks](http://twig.sensiolabs.org/doc/tags/block.html) etc., but using a static HTML page as a starting point for your new Craft site can be really helpful.
  
  Oh.. and believe me, while you're learning Craft and about all the features, you'll most likely want to refactor parts of your code more than once. :D
  
  > **Comments:**
  > **username_0**: That's my plan. I will build static home page and some generic page templates in HTML/CSS then rebuild in Craft. My concern was Bootstrap talks about "compiled" CSS. My understanding of compiled code is that it's machine readable only. I don't know how I would integrate machine code into Craft. But, having downloaded and poked around Bootstrap, it looks like the CSS files are plain text. I still don't know what they mean by "compiled" CSS.  
  > **username_6**: They probably mean compiled from SASS or LESS files to CSS. And again, you wouldn't need to rebuild anything, you'd simply add the Twig code to your static site. :D  
  
  ---
  
  