Answers.Body: <p><strong>Ben's answer is excellent, and should be marked as correct.</strong> This is simply some additional information to reinforce the decision to use Craft 2.</p>
  
  <p>The current version of Craft 3 is a <s><em>developer preview</em></s> <em>beta</em> (thanks Simon)... This means that there are no implicit claims of stability, and anything could change at any time. Similarly, there is no guarantee that you will be provided with a clean migration path for your data, if something were to change internally.</p>
  
  <p>As you noted, Commerce is not yet compatible with Craft 3. It's possible that Commerce won't be adapted to C3 until the official launch of C3 (tentatively slated for late 2017).</p>
  
  <p>Finally, upgrading your completed site from Craft 2 to Craft 3 should be (reasonably) painless. The facets of the site which do not directly depend on plugins should be a nearly seamless transition to C3. For the parts of your site which do depend on plugins, it will mostly be a matter of adapting those plugins to the new C3 architecture. While this will probably amount to a small-to-medium sized challenge, it will require the exact same learning curve as you'd be taking on if you were to jump into Craft 3 now. In fact, the learning curve would (theoretically) be easier if you waited, since the Craft build would be considered stable, and there may even be some documentation (and/or tutorials) available at that time.</p>
  
  <p>In summary, <strong>definitely go with Craft 2 for now</strong>.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-01T22:25:58.330Z
Answers.Text: It's now in *beta* instead of *Developer Preview* so it's getting closer.
Answers.UserDisplayName: Simon East
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-10-08T23:30:13.673Z
Answers.LastActivityDate: 2017-06-05T20:54:22.740Z
Answers.LastEditDate: 2017-06-05T20:54:22.740Z
Answers.UserDisplayName: Lindsey D
Answers.Body: <p>If you use a lot of third-party plugins, it can be more risky to start the project in Craft 2. Because you never know whether and if when an upgraded Craft 3 version of the plugin will be available.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-08T00:40:52.120Z
Answers.Text: If you intend on using a lot of third-party plugins, you'll find most of them are not even available on Craft 3 yet. ;-)
Answers.UserDisplayName: Simon East
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-10-11T17:59:36.087Z
Answers.LastActivityDate: 2016-10-11T17:59:36.087Z
Answers.UserDisplayName: MISC
Answers.Body: <p>My recommendation would be to go with Craft 2: </p>
  
  <blockquote>
    <p>A bird in the hand is worth two in the bush</p>
  </blockquote>
  
  <p>There is no doubt that Pixel &amp; Tonic has turned their focus to Craft 3, but software projects are complex and often take longer than expected and Craft 3 currently only has speculative release dates. It has also had speculative release dates in the past.</p>
  
  <p>If you've made the decision to go with Craft it's likely your additional costs based on the Craft 3 transition will either be to deal with uncertainty and moving targets while developing on Craft 3 for the next several months or to go with the stability of Craft 2 and deal with some extra costs of upgrading to Craft 3 when the transition is well documented and Craft 3 is stable.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-10-08T19:17:16.877Z
Answers.LastActivityDate: 2016-10-08T19:17:16.877Z
Answers.UserDisplayName: Ben Parizek
Body: <p>I am just about to start a new project and Craft seems the best fit as a CMS. The projects timescale is 3 months.</p>
  
  <p>I understand that a beta for Craft 3 is due out at the end of this year (2016). In view of this, should i start development on Craft 3? Or run with Craft 2 for now?</p>
  
  <p>The project will involved bespoke plugin development and use of the Commerce plugin. Is there any timeframe in place for updating the Commerce plugin to run on v3?</p>
  
Tags: <craft3>
Title: New Project: Wait for Craft 3 or start now with Craft 2?
ThreadText: # New Project: Wait for Craft 3 or start now with Craft 2?
  
  (Asked by: username_0 on 2016-10-08)
  
  I am just about to start a new project and Craft seems the best fit as a CMS. The projects timescale is 3 months.
  
  I understand that a beta for Craft 3 is due out at the end of this year (2016). In view of this, should i start development on Craft 3? Or run with Craft 2 for now?
  
  The project will involved bespoke plugin development and use of the Commerce plugin. Is there any timeframe in place for updating the Commerce plugin to run on v3?
  
  **Tags:** craft3
  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_4 on 2016-10-08. Score: 22 | Accepted answer
  
  My recommendation would be to go with Craft 2:
  
  > A bird in the hand is worth two in the bush
  
  There is no doubt that Pixel & Tonic has turned their focus to Craft 3, but software projects are complex and often take longer than expected and Craft 3 currently only has speculative release dates. It has also had speculative release dates in the past.
  
  If you've made the decision to go with Craft it's likely your additional costs based on the Craft 3 transition will either be to deal with uncertainty and moving targets while developing on Craft 3 for the next several months or to go with the stability of Craft 2 and deal with some extra costs of upgrading to Craft 3 when the transition is well documented and Craft 3 is stable.
  
  
  ---
  
  ### Answer by username_1 on 2016-10-08. Score: 9
  
  **Ben's answer is excellent, and should be marked as correct.** This is simply some additional information to reinforce the decision to use Craft 2.
  
  The current version of Craft 3 is a ~~*developer preview*~~ *beta* (thanks username_2)... This means that there are no implicit claims of stability, and anything could change at any time. Similarly, there is no guarantee that you will be provided with a clean migration path for your data, if something were to change internally.
  
  As you noted, Commerce is not yet compatible with Craft 3. It's possible that Commerce won't be adapted to C3 until the official launch of C3 (tentatively slated for late 2017).
  
  Finally, upgrading your completed site from Craft 2 to Craft 3 should be (reasonably) painless. The facets of the site which do not directly depend on plugins should be a nearly seamless transition to C3. For the parts of your site which do depend on plugins, it will mostly be a matter of adapting those plugins to the new C3 architecture. While this will probably amount to a small-to-medium sized challenge, it will require the exact same learning curve as you'd be taking on if you were to jump into Craft 3 now. In fact, the learning curve would (theoretically) be easier if you waited, since the Craft build would be considered stable, and there may even be some documentation (and/or tutorials) available at that time.
  
  In summary, **definitely go with Craft 2 for now**.
  
  > **Comments:**
  > **username_2**: It's now in *beta* instead of *Developer Preview* so it's getting closer.  
  
  ---
  
  ### Answer by username_3 on 2016-10-11. Score: 3
  
  If you use a lot of third-party plugins, it can be more risky to start the project in Craft 2. Because you never know whether and if when an upgraded Craft 3 version of the plugin will be available.
  
  > **Comments:**
  > **username_2**: If you intend on using a lot of third-party plugins, you'll find most of them are not even available on Craft 3 yet. ;-)  
  
  ---
  
  