Missing CSS and JS files? about calcite-bootstrap HOT 6 OPEN

Ping @FelFly

from calcite-bootstrap.

@bsvensson Yes. We did remove them because this project is no longer running a full instance of Bootstrap and I needed the gh-pages branch to write updated documentation (which I should have sometime this week.) Full story here: #294.

If you have a copy of the javascript files and want to make a PR to add them to the assets folders of the docs like we did for umacgillivray with the CSS files, we can probably add that as a holdover for the old version of this project.

But moving forward, I'm trying to make this into an actual theme that you use on top of the vanilla Bootstrap code - that way folks can have Calcite Bootstrap or customer themes applied and without running two sets of Bootstrap files.

from calcite-bootstrap.

from calcite-bootstrap.

@ajturner Yes. I have all this written in the calcite-bootstrap-theme repo. I just need to move it over here.

As for a merged version - I don't know what you mean. If you mean that we should have a set of Bootstrap files in this project, I was specifically told by three people in two teams that was the incorrect way to handle a theme and I should remedy it with this version. With this version, there are three paths to running this theme:

1. Run Calcite Bootstrap as strictly Bootstrap variables
2. Run Calcite Bootstrap as Bootstrap variables + expansion variables/CSS to achieve stricter Calcite Web "look" and to have support for card components
3. Run either one of the patterns above, but in the event of a shared theme or customer theme, use that instead

from calcite-bootstrap.

It seems to me that the consuming app's build process should produce a single css file that is bootstrap + calcite bootstrap + any other css the app needs.

from calcite-bootstrap.

from calcite-bootstrap.