pshishodia-kgp / goc-website Goto Github PK

We'll have a list of companies in the backend. And the user can only select a company name among those. This is mainly to avoid duplicate and spam.

A global chat where we could send instant messages, they may or may not disappear afters24 hours (say) depending on our implementation.

This can be used suppose during GOC classes to notify all users or have some random discussions.

Selecting a tag should render blogs containing that tag only.
Note: Option to not select any tag
Further: Option to select multiple tags

Assuming we have a bunch of blogs, we need to list them out per request. Things to take care of

1. on a request ot "/blogs", all the existing blogs will be listed pagewise (with each page having a fixed number of blogs)
2. on a request of "/blogs?tags=...", the blogs with the particular tags as the argument have to be listed pagewise
3. A proper schema to store the existing blogs along with their tags (a json file?)

Note that it should have the following structure.

Problem Statement
Sample Test Case
Explanation
Constraints
Expected Solution
Tags

You're supposed to create two webpages, one at '/problems' that shows the list of all the problems (probably in a table with tags maybe?) and another webpage at '/problems/problem_id = 34' (say), that shows the complete problem with index 34 with all the details.

Handle Upvotes / Downvotes for blogs and comments.

Fill main page with

1. recent blogs (only titles)
2. Most active users
3. Most rated users (on codeforces)
4. Recent submissions on codeforces?

For now, probably just store link to cf's profile picture (can extract it during login). Also,need to update this in comments.

We need a mechanism for submitting blogs. Assume you receive a post request at "/submitBlog". We need a handler function that handles the post request. It should

1. verify the presence of all necessary data and metadata
2. insert it into the database properly while managing the accompanying tags as well
3. Reutrn success/failure status (the type of error, if it fails)

1. All the company names get automatically added as tags.
2. Interview Experiences only button on forum to only see interview posts.

Allow user to format the text, say italicize it, and add latex.

Every comment should have a (minus) icon beside it, clicking on it collapses the comment including all it's descendants. (similar to reddit. ) The icon should toggle to (plus) +, clicking on which now makes all those comments reappear.

login form should have fields

username/email: 
password: 

Sign up form should have fields:

gmail: 
username (cf): 
password: 
confirm password: 

The registration will be confirmed only user changes it email on code forces, with the same email as in here, and make it public, just for a while.

1. Signup Form shows error even when you open it.
2. InterviewBlog doesn't let you add new company (say shortlisting) until you have filled all the fields (even interview_content), which is really a pain in the ass.

Forum will have normal posts that might ask for debugging or anything else.

Merge interview blogs and Forum's post into one, that is the user can create a general post, and choose if it's an interview blog or not, we'll indicate this by some other field maybe. This would also reduce the amount of code that we'll have to write twice by a lot.

Right now, all text-areas are extendable and auto-adjust to the height they want because of a script in base.j2. Add support to add min-height to that script so that each text-area can have different minimum height to begin with.

Currently implemented as one-many (Each blog can have multiple tags)
Should be many-many (Tags can be shared commonly by multiple blogs as well)

Users should be notified about replies to their comments or blogs.

For now, only the basic skeleton for the website has been implemented. From a viewer's perspective, though it serves the purpose, it loses points in the aesthetics. Hence, improving these webpages is necessary. The required details one has to keep in mind

1. decide upon a proper theme for the entire website that will be used for all webpages
2. without making the webpage heavy, an aesthetically attractive design for webpages built over the basic skeleton present
3. any feature that might be needed but is currently not present (just the frontend part)

While creating an interveiw Post, there's no way to add tags now. Create a search-bar where you could type through the handles and search the one you want, or create whole another tag if there doesn't exists any with that name.

a rectangular box is defined in main.css. Wrap the login and signup forms using that class. The problem here is that, you do not want the box to take the whole width but only as much as the form needs.

Allow to save blog as draft.

Create the prototype for how a blog would look like.

1. Allow the user to have 'add to desktop/add shortcut(in mobile)' option.
2. It should also give notifications in mobile's notification tab, like facebook/whatsapp.

Maintain parent comments id and also comment's depth so as to break showing nested comments by an offset after fixed depth.

Post has a column for when the post was created.
Time elapsed between creation and display should be rendered in this format : x days ago
If it is less than a day ago, then either show "less than a day ago" OR convert to hours "x hours ago"
Following this manner, for posts created less than an hour ago, display "few minutes ago"

The comment box for any comment other than parent comment isn't of full width.

@tsaraf20 I'll add the improvements here. Please comment so that I can assign this issue to you.

We need to design a proper frontpage for the website using HTML and CSS. A suitable theme can be employed keeping in mind the aim of the website is to helpful students hence their CP awareness and skills, and prepare for interviews as well. Things necessary (but not restricted to) :-

1. The Name (Grimoire of Code)
2. A searchbar
3. Display of some popular blogs (just the frontend)

Other features could be added as well.

Shall we allow all four possibilities among edit/delete post/comment?

You'll need to create model for Problems, and in the current Blog Schema, you'll have to create a relationship with multiple problem objects, and modify the queries accordingly.