getninjas / gaiden Goto Github PK

Estou realizando vários testes no BrowserStack, e percebi que na página de categorias no iOS (iPad/iPhone) o layout tem apresentado algumas quebras. Investigando o código, reparei que em alguns casos o problema é apenas a falta do vendorprefix.

Isso acontece apenas em versões anteriores ao iOS9.
De qualquer maneira, acho que seria interessante ter essa task de autoprefix, assim a gente lima de vez qualquer possibilidade de bug nesse sentido.

@eduardojmatos @MarcoBrunoBR @bsoares @eliada

As we have to support many devices and browsers, and we have a hundred of pages with multiple type and size of content, we need to test our components in diverse kind of situations.

To guarantee this, visual regression tests are extremely necessary!!

I suggest some tools to make this possible, like:

• Succss - https://github.com/B2F/Succss
• BackstopJS - https://github.com/garris/BackstopJS
• PhantomCSS - https://github.com/Huddle/PhantomCSS

Currently our Media component doesn't align its content by the top, depending on the size of the text content.

We need to describe:

• how to install the project #32 ;
• the comands and the which one is essential to run;
• our sass-lint more explicit and described;
• a Wiki with how to open a PR;
• the motivations of project;
• why "gaiden" name;
• how to integrate in common projects.

• Add a word wrap for the media-box__body element.

Today we have spaces variables and mixin generation in the same location:

https://github.com/getninjas/gaiden/blob/c7d09ba7a119323f44dc54bd30b2908407bbe0f7/src/scss/settings/_spaces.scss

We need to move out this variables to settings folder.

To see our components on live mode, we need to create a task to build to gh-pages.

• Create a task to move files to root and push to gh-pages;

I was trying to show this project to some people but some files are not being found.
I tried to fix it locally but did not succeed.

On the last 3 months, the visits from Internet Explorer 9 dropped considerably.

• Decrease browserSupport constant on ./bin/build/prod/css;
• Re-visit our no-flexbox classes on components (old Android browsers still continue accessing our site);
• Add support info on our README.

Google Lighthouse shows a report about our font-size, and +30% are too small to mobile (less than 16px). We need to talk with our designers to decide what to do in somes circumstances

Create a form and fields components are our next job in Gaiden project. So, the following items needs to be done:

• Basic structure of a form;
• legend and fieldset elements;
• field element, to wrap label and input;
• label, input, select, radio, checkbox, toggle elements;
• messages of validation (mesage, message--success, message--error, etc.);
• disable option of elements;
• general message element;
• footer with steps (that can be or not a part of form element - we can discuss about this).

We need to improve documentation about major release 11 https://github.com/getninjas/gaiden/releases/tag/v11.0.0 :)

Imagens inside thumbnail component, on mobile, is not cover all the container:

Somehow the headings demo with classes lost the styling.
Maybe a path for styling got mixed up.

It seems that on the last deploy all the image paths got mixed up.

We are polluting our terminal with unnecessary logs of documentjs. We need to remove them to see sass-lint and other important logs.

• Remove option to log all the things on dev build

Currently doing a small fix for a crossbrowser feature, I discovered that our sass-lint.yml is being ignored from the build process. Somehow, the build process uses the sass-lint.yml that comes by default in this path /home/{user}/gaiden/node_modules/sass-lint/lib/config