Please include support for Bootstrap 4. Right now, Oscar appears to support Bootstrap 3. Please include support for Bootstrap 4
All PR are welcome, if you begin it i will help you.
Thank you. I am very new to programming but I am willing to help. Can you please tell me what I would need to do to include Bootstrap 4?
@ctailo It will be quite a big change due to the amount of templates and static files that would need updating (all the while taking care of design responsiveness on all screen sizes with the changes). But, in summary, you will have to update the relevant static files (less, js, css, images, fonts) for bootstrap with latest stable release from v4, then update all the templates that use bootstrap classes from v3, to v4 classes (or the corresponding changes if that class is deprecated or something entirely new would be better to use).
Although, I'd like to suggest, if you are going to make those changes, it is worth to look at other UI / CSS libraries and see if we can have better alternatives, since the amount of effort needed would be roughly equal.
@ashishnitinpatil Maybe, tabler?
How about Bulma ?
Please lets stick with bootstrap 4
Please lets stick with bootstrap 4
I agree with you. I think that bootstrap 4 is the easiest one to work with. I do not know of other frameworks. I am fairly new to programming, so I am not sure that I can commit to doing this by myself. However, if other people want to work on this, I can submit pull requests if I am able to contribute in some way.
This is going to be a big undertaking. I will help towards this but I'm unsure just how much of my spare time I can contribute. I guess the place to start is creating a branch that we can all push changes to.
feature/bootstrap-4.0
This is going to be a big undertaking. I will help towards this but I'm unsure just how much of my spare time I can contribute. I guess the place to start is creating a branch that we can all push changes to.
feature/bootstrap-4.0
Ok. How could this project be managed. Should we list out all of the things that should be done to make this change. As I said before, I am new to programming, so I am not familiar with everything that would be needed to do this.
@ctailo I've not made any changes to this project before so I have no idea of the procedure for new features in this repo.
You are correct in stating that we would need to first plan out what will need changing in a list, the list can then be ordered in order of completion. Someone from the core developer side would then need to review each pull request and merge into a new feature branch.
We need a core developer to "own" this feature, we can then do the work regarding listing out and then starting.
@SalahAdDin Do you have any comments to add regarding how we can get this done?
I think at first we can replace current static files by new version, and after that we can solve any compatibility problem, or we can replace step by step in each module in order to control it in a better way, of course, we must create a new branch for that and a new branch over that branch for each module.
I'll start a list here and update it as and when we think of more.
Requirements:
Hi, I have created a starting template for upgrading to bootstrap4 - feature/bootstrap4-addition-only
I have not removed previous bootstrap3 files because I think it'll be easy in development to refer to what the site looked like, before making relevant changes with bootstrap4 upgrade.
Once we finish with the upgrade, we can proceed with following TODOs which are basically for removal of bootstrap3 related files / changes.
gulp less task (gulpfile.js/*)Since I don't have push permission to official repo, kindly create a branch based on my feature branch to start off this upgrade.
Any updates on this yet?
Me and @samitnuk took over and continued to work on the Bootstrap 4 migration.
There's enough of work to do, but catalogue already looks like this:

A few days ago try to update my django-oscar project to MDBootstrap, where I found the problems in the shopping basket, where to click to remove or add to buy later. No matter what you need, you can count on me.
Basket summary page:

if you click on "Buy Later" or in "Remove", it works? Because with me don't work, i do not know why css would change the functionality of the page, but it simply did not work the links.
What is the progress here? Can I already test the code somewhere? I couldn't find any branch regarding this topic
See PR #3005.
if you click on "Buy Later" or in "Remove", it works? Because with me don't work, i do not know why css would change the functionality of the page, but it simply did not work the links.
Most of the binding should work, although we're about to finish with visual part and start testing functionality.
Couple screenshots from the updated dashboard.



Looks good. The big job is done, waiting for Oscar version 2.1 that might include Bootstrap 4. Last update was made 31 of may and for now the branch is out-of-date with the base branch...
How is Bootstrap 4 integration? I really need it for the last project I'm working on.
Has it already been reviewed by the authors? The work looks great
do we need any help here to keep this moving?
do we need any help here to keep this moving?
@daniel-butler see discussion on https://github.com/django-oscar/django-oscar/pull/3302
Most helpful comment
Couple screenshots from the updated dashboard.