Skip to content

Updated styles and layout to be compatible with twitter-bootstrap 4 #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: wicked_1_0
Choose a base branch
from

Conversation

armezit
Copy link

@armezit armezit commented Dec 10, 2018

No description provided.

@DonMartin76
Copy link
Member

I have not forgotten this, it's very high up on the prio list, but I have some things I would like to talk to you about first regarding how to customize (e.g. by incorporating the scss step in the Kickstarter or something similar, leveraging the _variables.scss file from Bootstrap).

@armezit
Copy link
Author

armezit commented Jan 5, 2019

@DonMartin76 It would be nice to have sass support to let customizing bootstrap variables . Do you have any idea? I'll take a look at kickstarter and portal-env projects to find out possible approaches.

@DonMartin76
Copy link
Member

My idea would have been to have a variables file, or simply just use the variables file from Bootstrap, and use the Kickstarter to generate the CSS files. Alternatively, this step could be done startup of the portal API, but for the sake of simplicity, I think the kickstarter can do.

Input (in the static configuration) would be the variables file. Output, also in the static configuration, would be the generated CSS file(s).

I do not quite know what I am talking about, but it sounds to me it could be a feasible approach.

What do you think?

@armezit
Copy link
Author

armezit commented Jan 8, 2019

It makes sense. I would implement it in just a couple of days or maybe even sooner.

@DonMartin76
Copy link
Member

This will probably not make it into the 1.0 release, but I see it as a 1.1. There are still a couple of open questions we need to assess before we can really take it into the roadmap.

Over the next couple of days, I will be dropping the wicked_1_0 and merge everything to next; can you rebase your PR to that branch after it has happened (i.e. not yet)? That would be great.

I will open an issue for this to make it more public what we are talking about.

@armezit
Copy link
Author

armezit commented Jan 8, 2019

Sure. I'll rebase it whenever the next branch is ready.
Also, I'll add support for compiling sass files in portal-kickstarter and it would be ready for more review when you open an issue.

@DonMartin76
Copy link
Member

Branch next is up to date.

DonMartin76 and others added 2 commits January 17, 2019 16:13
-Wire to portal.com instead of portal.local, otherwise Google locally won't work
@armezit armezit force-pushed the twitter-bootstrap-4 branch from 376ac8e to d23466b Compare January 25, 2019 09:42
@armezit
Copy link
Author

armezit commented Jan 25, 2019

@DonMartin76 sorry for late response.
I rebased the PR to the next branch.
As I'm not much familiar with the way github deals with rebases, let me know that is it required to create a new PR ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants