tomwayson
commented
6 years ago I'll bite.
I agree this is confusing. These are all web implementations of the calcite design. Keep in mind that Calcite design is also used outside of the web - i.e. in ArcGIS desktop products.
calcite web - a standalone web implementation of the calcite design (no ui framework like bootstrap is needed) calcite bootstrap - you're already using bootstrap, but you want it to look like calcite calcite maps - Um... like calcite bootstrap only it also includes a few map-centric layouts? cc @alaframboise
As to why you'd use any one or the other:
- calcite web is used for esri properties, that often times were not even using Bootstrap. It can be used by other apps that don't already have a dependency on bootstrap and have some reason to have an esri branded look and feel
- we use calcite bootstrap in Hub sites and pages, b/c we want the sites to default to looking like calcite, but also want to give our customers familiar bootstrap markdown and styles that they can use to customize the site and even override the default look and feel. Note that most of these sites are laid out like web pages and may not even have a map
- calcite maps is good when you're building a map centric application and you want to use one of a few standard layouts and have the calcite look
Why are there multiple versions of "Calcite"? One for maps, one for bootstrap and one for web? Being ESRI I kind of understand, but it would be easier to get acceptance if you would make this easier to use and narrow this down to one project or maybe a calcite version and a bootstrap version.