active tabs not indicated properly about auviitkgp.github.io HOT 6 CLOSED

It seems that the function changeActive(number) defined in func.js is not working!

from auviitkgp.github.io.

Moved the whole website to Jekyll. This will ensure that we can continue to host everything on GitHub.

I am halfway through the process: https://github.com/icyflame/sandbox2

Site online on http://icyflame.github.io/sandbox2/

Under active development! So, in case something is broken, it's probably because I am working on it!

from auviitkgp.github.io.

I'd suggest not moving to jekyll. This is only a temporary solution for our website which is to be hosted in a PHP server. As such, jekyll specific code to be added in would prove to be a futile task and moreover become a liability while porting site onto the server.
However we do need a blog to be set up for the site and I've been planning to set one up via Jekyll hosted on GitHub. So to sum up Jekyll blog - yes, Jekyll site - no.
@ankeshanand

from auviitkgp.github.io.

Yeah! It would become a liability. But, in the current approach, since we are using Indexes instead of ID's, In case we add one tab in the navbar between Home and Sponsors, then we would have to change the index in all the files.

This can be fixed using Jekyll (Jekyll include works like PHP include_once). What do you think?

from auviitkgp.github.io.

This issue can be trivially solved by adding an id for each list item in the navbar. This would enable referring to each of them by name, and the generic jQuery call for .navbar>li would select all of them. This approach would have none of the scaling problems you mentioned.
Hauling in a framework for a bug-fix is over-kill, don't you think?

from auviitkgp.github.io.

Yeah! It probably is! But I wanted to try out how a normal non-blog website would be built with Jekyll! :P

—
Siddharth Kannan,
First year, Undergraduate student,
Indian Institute of Technology,
Kharagpur, West Bengal,
India.

Sent from Mailbox on Android.

Powered by Gmail.

On Thu, Sep 25, 2014 at 10:34 PM, Nevin Valsaraj [email protected]
wrote:

This issue can be trivially solved by adding an id for each list item in the navbar. This would enable referring to each of them by name, and the generic jQuery call for .navbar>li would select all of them. This approach would have none of the scaling problems you mentioned.

Hauling in a framework for a bug-fix is over-kill, don't you think? 😛

Reply to this email directly or view it on GitHub:
#7 (comment)

from auviitkgp.github.io.