Since we need, almost all the time, links without underline, maybe we should add a special class to specify which links we wants underline when hovered and let all the links be text-decoration: none.

Because I already had to modify too many links to remove the underline.

Faltou aplicar nas fontes do formulário de login: "Já tem cadastro? É só entrar"

e faltou aplicar na fonte do cadastro: "Ou crie sua conta:"

I don't recommend to adopt the last two sizes of drop down buttons. Do you see how it can be useful?

I just added

.social table.share-this a {
cursor: pointer;
}

because the share process is not a link, but a js.

Is class container used to contain all the pages content?

If yes, I suggest to add a margin-top 65px;

Robi,

when the event title has more width than 120px, as defined in the prometheus, the event title break in two lines. Today I put the ... automatically by adding this css:

white-space: nowrap;
overflow: hidden;
text-overflow: ellipsis;
width: 120px;

This is my suggestions about how to do it. I didn't added it because you said you wants to follow the modifications, but I am not able to move foward without it. When you can update it?

Thank you,

Our top bar is displaying some empty spaces between some dividers.

I recommend to remove all this padding inside the box. I don't recommend to use the triangle connecting the box with the dropdow, maybe we can do just like Google does (see example below).

Loading plugin to show a visual response for users

There is no style defined to buy tix for events with sales.

I recommend to adopt only one kind of top bar, my vote if for no divisions top bar.

Is that really useful to have buttons inside the top bar? Can't we just recommend to do not use buttons in top bar?

Vamos aumentar a fonte do "É de graça", abaixo do botão de criar conta.

Are we keeping the same old width predefinitions for boxes (span1, span2 etc), or we are adopting new ones?

@i-Robi can we review the icons in our icon folder. We are missing these icons:

https://skitch.com/lgavinho/87dfb/event-page-3.008.png

Maybe we should review the event page to discover all the icons are missing.

We should add a slider component as used to define tickets price in event form. The actual has a bug:the user cannot goes to 0 or 100 values because of a problem selecting the max right and max left.

Robi,

what about modify everything in sprites? we have tom much icons at the home page to load them as individual images. Do you agree with that? If yes, let's add it as a sprite to all prometheus.

It will help us to organize and manage all the images inside the img folder.

Thank you,

@i-Robi I suggest to put the code above from line 261 to 35:

.container {
width: 960px;
margin: 0 auto;
}

.container:before,
.container:after {
display: table;
content: "";
}

.container:after {
clear: both;
}

.center {
margin: 0 auto;
}

Let's add a date picker component.

Is it possible to customize the silders? For example, remove the bottom pagination, hide the timers and page numbers in top left etc.

We should remove .center margin top and bottom, because it changes other css predefinitions. This class should be:

.center {
margin-left: auto;
margin-right: auto;
}

@i-Robi we should specify for

p:last-child {
margin-bottom: 0;
}

instead of

p:last-child {
margin: 0;
}

Because it remove all the other margins in my other last paragraph tags.

The moves are too fast. In mobile model we should allow it to take 100% width.

If we put the pages right on the background, it can be a little bit hard to see. It is hard to see the ">>" in the sides.

Some Pagination good practices from "Smashing Magazine"

Good Practices Of Pagination Design
(7 Aspects according to Faruk Ates)

• Provide large clickable areas
• Don’t use underlines
• Identify the current page
• Space out page links
• Provide Previous and Next links
• Use First and Last links (where applicable)
• Put First and Last links on the outside

I like our actual pagination model, but the only problem is that it does not allow me to jump pages. See Google Example too.

Our project has css and image folders at the same level. So, for the images access, is recommended to add a ../ to go up one level and reference correctly.

It requires to put prometheus.css file inside a folder css.

Ex.:

body {
background: url('img/bg-pattern.png');
font-family: 'Lato', 'Helvetica Neue', Helvetica, Arial, sans-serif;
font-weight: 300;
font-size: 16px;
}

should be

body {
background: url('../img/bg-pattern.png');
font-family: 'Lato', 'Helvetica Neue', Helvetica, Arial, sans-serif;
font-weight: 300;
font-size: 16px;
}

Let's add the 16px icon set and adjust prometheus to work with it.

@i-Robi I can ask Juliana to help us with it. But you can do it if you think it goes faster.