Timeline for Should Habitat be used as a starter kit?
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2020 at 9:47 | history | edited | CommunityBot |
Commonmark migration
|
|
| Nov 21, 2018 at 0:37 | comment | added | jammykam | My point exactly, highly opinionated. | |
| Nov 20, 2018 at 23:21 | comment | added | Dylan Young |
So if one single example of a feature is okay, what is the difference if there are multiple examples of a feature, such is the case with Habitat? I would say the sample page is bloat, because if you are planning to start building out a site, you will ultimately need to delete that page. Same if you are trying to build out a Component for the marketplace using the starter kit, if it contains a Hero example module. I do agree it's a matter of opinion. Which it's good there are lots of options available, so depending on your opinion, there is probably an option available.
|
|
| Nov 20, 2018 at 21:37 | comment | added | jammykam | But now you're getting into opinionated semantics of what constitutes a "starter kit" and what you consider "bloat". A single example of a feature, personally I would not consider that bloat, like saying a default example of Sitecore contains bloat due to the sample homepage. And the rest seem to be what the author considers best practice. | |
| Nov 20, 2018 at 2:24 | vote | accept | Michael West | ||
| Nov 16, 2018 at 23:49 | comment | added | Dylan Young | I kind of disagree that Helixbase is a starter kit. It contains "example" modules as mentioned in it's documentation. Been working on an Open Source Project: github.com/sitecoremaster/Helix-Starter-Kit that I consider more of a "Starter Kit", because you can initialize a base Sitecore Solution which contains only 3 projects (Serialization, ORM and DI) and nothing more. It also provides developer efficiencies to extend it. No extra bloat, which is by design. | |
| Nov 16, 2018 at 2:55 | comment | added | Chris Auer | So you are saying there is a chance? | |
| Nov 16, 2018 at 1:27 | comment | added | Ken McAndrew | I'd say definitely mine the Foundation layer, and/or use something that's not as "feature-rich" as Habitat like github.com/muso31/Helixbase, which is more designed as a "starter kit" that's mainly Foundation with some examples on the Project/Feature level. | |
| Nov 16, 2018 at 0:57 | history | edited | Pete Navarra | CC BY-SA 4.0 |
added 162 characters in body
|
| Nov 16, 2018 at 0:49 | history | edited | Pete Navarra | CC BY-SA 4.0 |
deleted 13 characters in body; added 1 character in body
|
| Nov 16, 2018 at 0:41 | history | edited | Pete Navarra | CC BY-SA 4.0 |
added 141 characters in body; added 1 character in body
|
| Nov 16, 2018 at 0:36 | history | edited | Pete Navarra | CC BY-SA 4.0 |
added 129 characters in body
|
| Nov 16, 2018 at 0:35 | comment | added | Dylan Young | Or what seems to be more common out there, that vendors that use it as a "StarterKit", never do the comparative analysis, and then your solution comes with alot of unnecessary bloat that has unknown consequences. | |
| Nov 16, 2018 at 0:25 | history | answered | Pete Navarra | CC BY-SA 4.0 |