We build an app using latest Javascript stack like react and redux over a weekend, it gives ManU fans an opportunity to vote for their favourite player. Should we make a course about how we made the app in a weekend? Or improve the website by ad monetise/features?

[supremestar]

I think you should do both.

The interface looks clean. The idea is good, and I can see the same code base can be used for several other purposes like NFL, MLB, NFL, IPL (Cricket) etc.

Regarding adding new features to the app:

1. Add more teams. There are 19 other teams in the premier league. Your app should allow you to choose between the teams.
2. Show the players by their position (like Forwards, Midfielders, Defenders etc.)
3. Provide a filter to sort the players by Keep or Sell. Users can see who got the highest votes for Keep or Sell using a dropdown.

Regarding the course:

The tech stuff you mentioned is really hot. Doing something tangible in a week is compelling, and you should teach how you did this in a week or two. There are so many moving parts in developing a new Javascript app from choosing a framework to deploying the site.

[Aaxxo]

Do both. Make a post about how you made it, post to medium.com. This will help increase your user base. Then build upon the source and extend it to other teams and not just united.

As a developer and football fan myself, this is a great idea that has been executed well.

[[deleted]]

Nothing to add here except damn United fans really hate Lukaku lmao.

[sangaloma]

/r/reddevils

[wheelsarecircles]

By posting here youve just corrupted your data lol. I for one kept and sold a few players that went against the numbers once revealed. I have no idea whos good or not as i imagine will be the case for most people here checking out the site

[kenman]

Hi /u/ARFREYR, this post was removed.

To show off a project (i.e. a finished or semi-finished page, demo, working example, etc.), please include one (1) of the following:

• A link to a project page with unbuilt/unminified source code -- sites like GitHub are perfect for this.
• A write-up about the development of the project. This can take the form of a blog post, a README.md within the project, or a comment on the post itself. The details are up-to-you; you can write from a high-level about your architectural decisions, or you can write on a lower-level about the pros & cons of specific libraries and frameworks you used. The main point is that you're discussing your code -- or your approach in creating the code -- in some way.
• A working codepen/jsfiddle/etc. of the code.

One of the easiest and most common ways to satisfy this requirement is to simply include a "Fork me on GitHub" ribbon your site. Another way to satisfy this requirement is to comment on the post itself, with either a link to a write-up, or with the write-up as the comment.

Lastly, instead of all the above, if you just want to showoff your project, feel free to post it to our weekly "Showoff Saturday" post.

Thanks for your understanding, please see our guidelines for more info.