Currently we display only a brief summary on front page

What's Byld?
Byld is the software development club of IIIT-Delhi. We’re a bunch of students who love building apps and hacks using various tools and technologies.

Also I think we should put up our vision / mission of what we want byld to be / what we try for it to be on the website. The orientation session happens only once a year and then a lot of people don't even know what programming is, and almost no one knows what dev is.

@geekSiddharth suggested another session on "what is dev, why is it cool, what role does it have in jobs, what is byld?" based on first hand interaction with a few first years.

We could also summarize all of this within 3 paragraphs and have a "about us" section on the website, that'd be good for presence.

Possible fix: add a hidden element to navigation for #belowNav

Builds are failing since past months.

Needs investigation and fix.
Probably just need to add gem install bundler:1.16.2 in travis.yml

• Add ProjectHub Information Page
• Update the list of current projects. Add backpack oracle and byld-website to it at the very least. Remove old and dead projects.
• Move projects section from homepage to a new dedicated page with available filters (or at least visual cues) to show mentor availability for the project, and show institute portals separately on the page. Ideally, projects sorted by last commit date of the projects on github (could re-order in js. Add a little randomness for fun)

I think the major change is within the container class from 3.0.0 to 3.1.x

Just noted this because the main div looks a little odd from the original website (Notice some extra spaces on either sides of the container)
(And maybe upgrade to bootstrap 4.0.0 in future, but I'd be more interested in just fixing this at the moment)

Looks like the website has been designed for viewing on Desktop. Would be great if it can be optimized for Mobile view too.

https://github.com/virresh/byldWebsite/pull/19 implements them as found on the original website.

Here are some minor improvements which we should undertake (maybe in a separate PR)

• Display hackathon winners / prizes info
• Make prizes info yml data structure use an array for first/second/third prizes. Have an ability to specify ties
• Make dateTime field accept both human-friendly date formats and the current date format as is present in old exported data
• Make navigation be present on all pages
• UI for "coming hacknight" and "coming hackathon" and "coming techtalk". Something that can handle both presence and absence of a date, and link to facebook event

Refer: #59 (comment)

Also https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/

But please refrain from github UI as much as possible, it makes making mistakes easy and provides no way to amend them
Although you can most of the times correct a mistake made from UI by pulling in the mistake and doing stuff locally

Note: Here "users" means anyone, including site maintainers

• Events - Hackathons, Hackeve and Talks
• Members list
• Projects
• Make your own member page

https://github.com/gjtorikian/html-proofer

And add information about how to do stuff in the repository for someone who doesn't know where to start

Could either use https://github.com/ekalinin/github-markdown-toc#remote-files or do it manually.

This is a one time thing, then whenever someone updates wiki they could update the ToC too

This is before it collapses to a hamburger menu (in whose icon we're using four lines instead of 3 as in the original site and everywhere else in the world - another thing to fix)

Screenshot:

Maybe it'll look better if it were aligned on the right with the IIITD logo - or if we get rid of extra nav padding which kicks in on viewport width smaller than 1200px

Namely

• 404.html (Probably needs update)
• about.md (Probably needs removal)
• members page (Needs to be added)
• blog aggregation page (Needs to be added)

(Since I have never seen the blog page of old website, I have no idea how it looks like)

So there are a lot of resources which exist on-line already. You can do a search and find them.

But the problem is that there are too many resources now. And some of them might be low quality but high ranking.

We could have a page / wiki page listing resources which personally benefited the members. Could be learning resources, exercises, online contests, etc

Hello Smera Goel, Dibya Gautam, Ria Gupta, Shekhar Shukla, Saksham Mrig, Vishwesh Kumar, and Himanshi Mathur

Welcome to Byld!

Before we begin, you are requested to complete the tasks given to you in the mail. We can use this ticket for general discussions before we add you to the group. You are also required to create a PR and add in your details in the members.md file as specified in the wiki.

We shall be using this ticket to welcome you to the club. It would also be great if you could drop a one-liner introduction here as well as in the group (when we add you 😛)

If you have any questions at all, please ask!

We can also use https://developer.github.com/webhooks/ instead of nightly builds

It's supposed to scroll to #belowNav but it isn't scrolling to it.

Also see https://github.com/virresh/byldWebsite/pull/12#issuecomment-397827604

https://github.com/IIIT-Delhi/byld-website/blame/master/site/index.md#L43

the line with tatus: is a mistake and needs to be removed

Add something nice, so that when link is expanded by crawlers they see something good
https://github.com/virresh/byldWebsite/blob/master/site/_config.yml#L19

i.e.

Link to log for latest occurrence of this

I've had to restart it once before. Leaving this in failed state so @virresh can investigate.

Would https://github.com/virresh/byldWebsite/issues/17 fix this too?

I don't want to set up a linting check / commit hook because I think it'll add friction to the process of contributing to the site

Also this is a small project so we might not really need it.

But we do want to end up just formatting everything from time to time so that it looks consistent for someone new who looks at the code.

Chances are -- if the code already isn't spaghetti then someone changing some files would also adhere to the making their changes look nice and fit in with the rest of the code too.

How could we achieve this? How about adding a few scripts which can be manually triggered to auto-format html, css, yaml, and js and then one could just run the script after it's been a long time and submit a PR

Hackathons
TechTalks
Hacknights

Goal:

Current:

To see the source code on GitHub for these files, best way I've been able to find is the blame view, because by default it looks ugly: https://github.com/IIIT-Delhi/byld-website/blob/master/site/hackathons.md

Can we change the extension of these files? Can we do something else?

The contributing guide links to these files and expects them to be easily inspectable, so that where we need this

http://byld.iiitd.edu.in/members.html

For e.g s.no 32 38 42 etc etc

The contents of homepage should appear as soon as the section is scrolled into the view,

but it's actually scripted to fade in after top of the section is at top of the screen here

Fix: fade in after 80% of the section is visible

http://byld.iiitd.edu.in/ has a few projects

These needs to be added in here: https://github.com/virresh/byldWebsite/blame/master/site/index.md#L9

Also the visual aspect is controlled from here, if you need to perform any tweaks in there:
https://github.com/virresh/byldWebsite/blob/master/site/_includes/projects.html
(Please add a hyperlink entry for the projects)

Often times when people have to take a session, they don't understand that the time commitment goes beyond the actual 2 hours of the session, preparing a good session is a much more time intensive job.

n*2 man-hours of the n participants are much more than the 15 hours a speaker will have to put in to make sure their presentation is the best it can be.

We could add a page to our website and some button which says "Want to take a session?".

The guide should be brief (5 minute read at most) giving an overview for essentials of a good session, with links for further inquiry. This structure is important because not all issues affect all speakers.

We should also make every speaker responsible for making a feedback form (or we could make it, but it's best the speaker does it because it'll be feedback for them)

Uncaught DOMException: Failed to read the 'rules' property from 'CSSStyleSheet': Cannot access rules
    at CSSStyleSheet.<anonymous> (http://byld.iiitd.edu.in/:343:25)
    at Function.each (https://code.jquery.com/jquery-1.11.3.js:384:23)
    at http://byld.iiitd.edu.in/:341:5

Possibly related to 922518a

This will make the repo plug and play (and ready to fork, since no extra configuration will be required for activating netlify on forks)

We do not want analytics from the development versions, but we definitely want them on the production version

Setting up for contributing for the first time is a bit of work. GitHub UI tries to make it a little easy, but that doesn't work (#78 (comment))

I'd like to add a gitpod configuration
to the repo so that an online IDE can be opened in a single click, with all the dependencies for the website available in a container, and terminal access for doing rebasing etc. This can later be replaced by GitHub's codespaces when that gets released.

I'm not sure how long this site will be used by the current admins, but I wanted to add gitpod to some repo to experiment with it and it'll be useful here so I think I'll add it in.

This can be done after making the site public, since we currently have data which is same as the data on current Byld site

Currently they're both in common.css but since all pages have their own .css files, we should probably do this

Currently we have a private list on trello. Ideally we'd like anyone to be able to suggest ideas, and have the ideas listed somewhere public, such as on the website.

This could be potentially clubbed with projects, i.e. on one page you have projects which are "finished and require maintenance" (most of current institute projects), you could have projects which are "under construction' and a list of "ideas"

Perhaps we'd also need a place to discuss the ideas, which could be in the issues section. If it blows up then we'd need another repo, but otherwise this repo could also work.

It's [email protected] as opposed to [email protected]

I believe byld-admin is the google group that older admins used so that each and every one of them gets a mail sent at the id?

If that's correct, I'm not sure who's on the google group and who isn't. Should we then change it to [email protected] or should we all join the google group?

cc @geekSiddharth

Most alumni have left and wouldn't be adding themselves to the website. Go through the mailing list to make sure everyone is added and also create an alumni mailing list separately to better manage the lists?

Reduce our Bus Factor

We need someone to help us design the stickers for Byld

Currently we'd like to make three kinds of stickers:

1. For everyone - These are giveaway stickers, for byld events (for both members and non-members)
2. For members - These will be stickers for byld members only
3. For winners - These stickers will be for winners only

This thread is for discussion related to images, please post one image as one message on this thread

Would possibly need custom flask or frontend-js logic that when provided with a list of feed URLs, reads all of them, arranges them in chronological order (for this to work, either the feed must specify the datetime properly, most feeds do this), and displays the blog post summaries on /blog (paginated for flask, infinite scroll for js)

If we need to keep history, then we'd have to use a backend, since feeds contain only the latest 10-30 posts.

Since this isn't a core functionality, we could just do it in user's browser after they load the blog page. It could take upto 2-10 additional seconds to load though.

For becoming a member of byld, one person would be required to do the following this:

• Make PR to add his name to the member's page.
• In comments of the PR, the person must mention why he or she should be included in byld.
  • Hackathon participation/wins
  • Open Souce contributions(small or big)
  • Skills
  • Projects
  • 🤷‍♂️

Small unobtrusive buttons on each page which take you to the .md file of that page.

Like you find on readthedocs:

Currently if you don't know about the repo, you don't know that this website is editable

Screenshot:

Expected: It should look like it does on screen width > 990px

I think this and other UI related bugs would benefit from a CSS refactor than minor fixes

https://github.com/virresh/byldWebsite/blob/master/site/_includes/navigation.html#L35

This thing is copied and edited a little to avoid placing a link there, but is a terrible thing to keep
Do something about it

See discussion on https://github.com/virresh/byldWebsite/pull/24

• Add support for
  • Github badges
  • Linkedin badge
  • Twitter "follow me" (or twitter stream, but maybe we can't allow that because we have no control over the content)
  • stackoverflow badges
  • maybe fb and G+?
• Make it look pretty (default member page UI)
• Build-time script to generate these pages

Add byld's public group link on the index page of the website. Link - https://t.me/byld_iiitd

We won't need to port the blow post viewing UI because the plans for the blog is that it'll act as a generator. It'll read the members' blogs' feeds and display them on the site