Create a Login Feature backend storing the data

[Smritigit1202]

Create a Login Feature backend storing the data-

Name
Enrollment
Email Id
Phone No
Participant / Volunteer / Coordinator

Coordinator - can create events and post the events pics, once concluded.

Preferred Tech Stack-
any SQL Database and Django

[codeblech]

login needs to be thought out extensively. we would not want to the login to be required just to view posts. also, we need to be aware of what features actually depend on login.

then, we need to decide if everyone can login, or only coordinators can login.

in either case, we need a workflow to manage appointment of coordinators, and their capabilities on the platform.

still, we would need a quick and easy workflow to switch the posts on automatic mode again, where instagram posts are scraped and directly uploaded. this is for times when the coordinator is or cannot be active. some more decisions need to be made here. Do the coordinators decide when the site is on "auto-pilot" and when only manual posts are made? What if the coordinator just becomes inactive without starting the automatic posts?

With any feature implementation, there would be many design decisions. I would like those decisions to be made with care and discussion.

In case of any feature that would require manual input from people, be it us maintainers or hub coordinators, I want those features to be only implemented after discussions with the parties involved. For example, what if no coordinators want this hassle of posting here?

Then again, it comes down how friction-less of an experience can we provide to anyone who does manual work for this magazine.

With all that yap, I want to say...whatever feature you're implementing please think it through. I am not trying to stop you from learning any of this stuff. I'd be happy to help you with any of this otherwise. I just don't want this magazine to be a load of unusable feature dumps.

[Smritigit1202]

Thank you for your thoughtful feedback.
I agree that we need to carefully consider login requirements and coordinator roles.
So, can we simply implement the login feature right now, and then develop the additional requirements as the website grows..? What say?🤔

[codeblech]

i think the implementation of login would be coupled with what that login would enable the user to do, like... does loggin in allow user to upload/modifying/delete posts?

how do you plan to implement it?

[Smritigit1202]

What we can do is add a feature to boost posts within our app’s data. People who are interested in an event can click an icon, and then we can display those posts on the of all users homepage as "most liked" or "most interested in."

Liking Instagram posts through our app won’t be possible, but this way we can still highlight popular posts based on user interest.

[codeblech]

or we can scrape likes data directly from instagram. sounds good