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

Add link to Code With Andrea website (Flutter tutorials) #709

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bizz84
Copy link
Contributor

@bizz84 bizz84 commented Jun 28, 2020

Description

CodeWithAndrea.com contains a growing collection of over 50 free videos, articles and tips about Flutter app development.


Checklist

@Solido
Copy link
Owner

Solido commented Jul 10, 2020

@renancaraujo @rodydavis @orestesgaolin @jogboms

First time we need to deal with such a case:

Free content is used to drive traffic that eventually transform to a sell on this page
https://codewithandrea.com/courses/

Putting this on top of the list is like redirecting traffic for business but there's some interesting content too.

What's your idea ?
Should we create an explicit section ?

@rodydavis
Copy link
Contributor

Probably just include a tag like paid or free trial!

@bizz84
Copy link
Contributor Author

bizz84 commented Jul 11, 2020

To clarify, I regularly post free Flutter tutorials (articles and videos).

At the end of my pages there are cards where students can view my paid courses if they wish to do so.

Alternatively, I could open a PR to include a link to my YouTube channel.

This includes all my free videos. People can indirectly find my website from there, but the paid content is much less prominent.

Would that be more suitable?

@rodydavis
Copy link
Contributor

I think it is fine free YouTube channel could be added, but we could also add a paid content section too! 🤔

@bizz84
Copy link
Contributor Author

bizz84 commented Jul 11, 2020

The name "paid content" kind of implies that all the content is paid. Many instructors have websites with a mix of free and paid content - not sure what would be the best way to categorize this.

I'll open a separate PR for my YouTube channel.

@jogboms
Copy link
Collaborator

jogboms commented Jul 12, 2020

I quite agree with @rodydavis on the tagging. It contains amazing free content. Maybe a tag indicating possible paid content.

@bizz84
Copy link
Contributor Author

bizz84 commented Jul 22, 2020

Related: I've now opened a separate PR for my YouTube channel:

#722

@rodydavis @Solido re. website, how would you like to move forward?

Thanks :)

@renancaraujo
Copy link
Collaborator

IMO we should move forward with https://codewithandrea.com/articles/ (since that section is supposed to be for blogs and the channel has been included via #722) regardless of the 'courses' link. It only would be considered a "paid product" only if the articles were under a paywall or some kind of free trial.

Bottom line: It should go, IMO.

@rodydavis
Copy link
Contributor

LGTM

@bizz84 bizz84 force-pushed the add-code-with-andrea-website branch from 9298ff2 to afeec28 Compare July 22, 2020 16:14
@bizz84 bizz84 force-pushed the add-code-with-andrea-website branch from afeec28 to 24cd557 Compare July 22, 2020 16:14
@bizz84
Copy link
Contributor Author

bizz84 commented Jul 22, 2020

@renancaraujo That sounds like a good idea. I rebased and amended my PR to point to the articles page.

Copy link
Collaborator

@renancaraujo renancaraujo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@bizz84
Copy link
Contributor Author

bizz84 commented Aug 21, 2020

@rodydavis @renancaraujo @jogboms @Solido I'm not sure if anyone has noticed, but content from merged PRs doesn't seem to appear in the main README (Example: #722). Perhaps some build pipeline is no longer working?

Also would be nice to merge this PR. 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants