Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Prototype Frontpage Implementation. #67

Closed
wants to merge 13 commits into from
Closed

Prototype Frontpage Implementation. #67

wants to merge 13 commits into from

Conversation

bravegnu
Copy link
Member

No description provided.

bravegnu added 12 commits March 10, 2015 23:30
@bravegnu
Prototype implementation for the frontpage.
f718254 
The idea is to develop HTML page outside the Pelican framework, so
that we have greater control over layout of the page. We would also
like the frontpage to act as index / TOC to the rest of pages in the
site.
@bravegnu
Fix volunteer link.
fccb20f
@bravegnu
Max. width set to 1200px, and scroll-over effect killed.
c8c84f0 
The width of the contents is restricted to a max. of 1200px, so that
we don't have worry about the layout beyond this width. But with this
change, the scroll-over will only partially cover the splash, so we
kill the scroll-over effect as well.
@bravegnu
Move the footer out of the container.
32cb3c0 
The container is restricted to 1200px width, but we would like the
footer to span the entire browser window width. So we move the footer
out of the container.
@bravegnu
Removed unused style.
0391f42
@bravegnu
Put the album images in a grid.
02937be 
The album images are put in a grid, and made responsive so that they
scale as required, instead of getting wrapped.
@bravegnu
Drop the twitter hashtag embed.
9d5311d 
The twitter hashtag embed is out of place, since we just want people
to Join and Follow Us on Twitter. So a tweet listing is sufficient
here.
@bravegnu
Fixup workshop photos.
2d16a8e 
The existing workshop photo is not large enough to take up the space
provided by the grid. So instead we use two photo, make them
responsive and put them in their own grid.
@bravegnu
Fixup grid for Project section.
43fa27f 
The grid size was incorrectly specified for large displays. That has
been fixed. Moreover for medium sized displays, the grid size is now
set to 1, to avoid wrapping of the code.
@bravegnu
Reduce frame width for "Recent Topics" embed.
d5b9dbc 
The frame width is reduce to fit within the grid for large displays.
@bravegnu
Typo and spacing fixes.
486f00e
@bravegnu
Fixup overlap of "Volunteer Sign-up" button.
22f706f 
The Volunteer Sign-up button overflows the grid in medium displays,
fix that up, by setting the grid columns to 1 in medium displays. Also
on large display we give sufficient space for the button.
@bravegnu bravegnu mentioned this pull request Mar 13, 2015
Open
@bravegnu
Copy link
Member Author

Guys, your comments on this ...

@shrayasr
Copy link
Member

Sorry for the lateness. Been really busy this week at office.

This is way more "scalable" than what we currently have but I think it becomes a little too bland. There is just way too much text going on in the page. We should find the right balance IMO between using text and not using it. I really like PyCh.in and we could learn from them. They have a good balance going on with dashes of colour.

Please note, in no way am I criticizing what you have done. This is a great effort and should be done. The only sad part is none of us are designers and I don't know if we have any one on the team that is who can help us out with this.

Let me also give this a try and we can probably borrow thoughts from our work and decide on a final version?

@bravegnu
Copy link
Member Author

OK. I will try to explain why we started doing this, and why ended up doing this.

  • First, we wanted a page that can hold links to all other pages in the website. That was what I proposed in Landing page outside pelican #47 The current pelican theme only provides a sidebar with few links that has proved to be insufficient in many instances, as noted by @shrayasr in the same issue.
  • Since we started re-doing the front page, we decided to borrow some cues from other sites, like Pych, PyCon India, etc. But our intentions might be much different from theirs.
  • I do agree that this prototype needs improvement in the design department. But if you think this would serve as meaningful starting point, then I would prefer getting this committed, and then improving upon it. The page will remain hidden, till the time it is satisfactory. At which point we will turn the home.html to index.html and go public.

@shrayasr
Copy link
Member

First, we wanted a page that can hold links to all other pages in the website. That was what I proposed in #47 The current pelican theme only provides a sidebar with few links that has proved to be insufficient in many instances, as noted by @shrayasr in the same issue.

👍

Since we started re-doing the front page, we decided to borrow some cues from other sites, like Pych, PyCon India, etc. But our intentions might be much different from theirs.

Fair enough. But what I meant was the direction that we need to take eventually.

I do agree that this prototype needs improvement in the design department. But if you think this would serve as meaningful starting point, then I would prefer getting this committed, and then improving upon it. The page will remain hidden, till the time it is satisfactory. At which point we will turn the home.html to index.html and go public.

Yes I noticed that it is in home.html and that it wont replace index.html. If it anyway doesn't come up on the site then why do we really need to commit it in? We can just keep this as a WIP place and work on it, right? Like you mentioned lets use this as a starting point and work on it here. I don't see the necessity to merge it in if it isn't going live anyway ATM. Right?

@igauravsehrawat
Copy link
Contributor

how about we look for new theme the same way we looked for logo ?

@shrayasr
Copy link
Member

how about we look for new theme the same way we looked for logo ?

-1 from me on this. It'll become too much of an elaborate process then.

@bravegnu bravegnu closed this Mar 25, 2015
@shrayasr
Copy link
Member

@bravegnu Why is this closed? Lets continue our frontpage discussion here. ok?

@bravegnu
Copy link
Member Author

Can we discuss in the issue #47 instead?

@shrayasr
Copy link
Member

Ah, sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@bravegnu @shrayasr @igauravsehrawat