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.

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

[FEATURE]: Information on Embedathon homepage. #41

Closed
anirudhprabhakaran3 opened this issue Nov 8, 2023 · 9 comments
Closed

[FEATURE]: Information on Embedathon homepage. #41

anirudhprabhakaran3 opened this issue Nov 8, 2023 · 9 comments
Labels
enhancement New feature or request Module:Embedathon All issues related to Embedathon Module

Comments

@anirudhprabhakaran3
Copy link
Member

What is the feature you would like to see?

Add the following text to the embedathon homepage.

Those who are taking IEEE/Renewing membership can add CAS membership for 2024 for FREE. Please encourage more students to get the benefit.

Please note its only applicable to those who have never been CAS Member before.
https://cas.ieeebangalore.org/guide-to-join-ieee-cas/

cas_membership

How important do you think this feature is?

Medium

Contact Details (optional)

No response

Anything else?

No response

@anirudhprabhakaran3 anirudhprabhakaran3 added enhancement New feature or request Module:Embedathon All issues related to Embedathon Module labels Nov 8, 2023
@anirudhprabhakaran3 anirudhprabhakaran3 added this to the Embedathon 2024 milestone Nov 8, 2023
@nishant-nayak
Copy link
Member

@anirudhprabhakaran3 shouldn't this be a part of the Embedathon-Website repo?

@anirudhprabhakaran3
Copy link
Member Author

Migrating that project here right?

@nishant-nayak
Copy link
Member

@anirudhprabhakaran3 migrate once the public facing pages of Corpus are ready and the Embedathon Website for 2023 is fully ready. Until then, I'd recommend developing the Embedathon Website as a separate project.

I don't want Embedathon folks waiting on us to finish migrating the public pages before they can get their registrations and all underway.

@anirudhprabhakaran3
Copy link
Member Author

yeah so I'm getting vignaraj and a couple of juniors to start migrating the static pages from now itself, so that by the time we need to get this live we'll have all the content ready. that's fine right?

@nishant-nayak
Copy link
Member

That's fine. If all goes well, we can have Embedathon as part of this project itself. To be safer, I would still recommend developing the Embedathon Website separately, maybe creating provisions for easy integration with Corpus.

@anirudhprabhakaran3
Copy link
Member Author

I think we can do it, since even if we don't get all static pages done by then, we'll have to get a new container for Embedathon and a domain. If that's the case, we can just disable some urls and deploy just the embedathon app right? That's why developing it in that different repo seems a bit redundant, imo.

Also will be running behind the others to get static work asap. should not be that difficult tbh.

@nishant-nayak
Copy link
Member

Alright. Get whoever is working on Embedathon to migrate the Embedathon app into this repo and make a new PR for it.

I'll also be working on migrating static pages. If there is anyone else working on new pages, make sure they have an issue assigned to them for the page. #37 and #38 are good starting points.

@anirudhprabhakaran3
Copy link
Member Author

I only will start working on the Embedathon app for now. Will ask Vignaraj if he wants to join or if he'll be part of the migration force too.

Also, scaffolding Embedathon from scratch is a good idea? What do you think? (from scratch I mean copy pasting relevant pieces of code from the old repo, not just copy pasting entire files and all)

@nishant-nayak
Copy link
Member

Taking this discussion onto Discord.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Module:Embedathon All issues related to Embedathon Module
Projects
None yet
Development

No branches or pull requests

2 participants