Closed CassidyB closed 9 years ago
@CassidyB we will be making breaking changes in between major versions, so if we did this the production site could become deeply broken all of the sudden without you knowing about it...
@paulcpederson fantastic point, so which version should we tie ourselves to? Also if you build a new feature into the site and than update the JSON with this new item but we do not have the CSS or JS to make it work, would that not be an issue as well?
@CassidyB yeah, that's a good question. Since the doc is pulled automatically from the most recent json I guess it makes sense to have a latest folder. If we make breaking changes the markup from us will be fine, but other areas of the patterns site might break. Not sure the best way to handle that, but I think having a latest folder is probably a good idea so at least the web stuff is always in sync.
@CassidyB another way to get around this would be to just import content from a specific version's json into the project and then you can tie the content and design to a particular version.
@paulcpederson So the solution to this issue is that you will move all the JS/CSS/IMG/referenced files to the latest folder and we will point all of our code to the latest folder.
ok, there is now a latest folder which has all the same stuff as the versioned folder. Closing.
In order to keep us on the latest version of the JS/CSS/IMG files we created a folder on the S3 called calcite-web/latest/. When a new version is pushed to the s3 can you please push a copy of the JS/CSS/IMG folders that are inside of your latest release folder into the calcite-web/latest/ folder as well? This way our site is always up-to-date and we do not have to change our URLs.