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 clarification to differentiate between the blog URL and the RSS(feed URL) during sign-up #3763

Merged
merged 1 commit into from
Nov 25, 2022

Conversation

cychu42
Copy link
Contributor

@cychu42 cychu42 commented Nov 16, 2022

Issue This PR Addresses

USAGE: #3646
This PR addresses one of the issues raised in the issue.

Type of Change

  • Bugfix: Change which fixes an issue
  • New Feature: Change which adds functionality
  • Documentation Update: Change which improves documentation
  • UI: Change which improves UI

Description

image
The issue was that some users experience confusion between a blog URL (blog's root HTML) and select the RSS (blog's feed XML) during sign-up. This PR adds 2 sentences to the prompt to clarify the difference, in src\web\app\src\components\SignUp\Forms\BlogFeeds.tsx.

Steps to test the PR

Test this by going through the sign-up process to view the Blog Feeds page.
During testing, you can use test account user1 with password user1pass.
You can enter any Github account name to get through the page before this page.

Checklist

  • Quality: This PR builds and passes our npm test and works locally
  • Tests: This PR includes thorough tests or an explanation of why it does not
  • Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not (if applicable)
  • Documentation: This PR includes updated/added documentation to user exposed functionality or configuration variables are added/changed or an explanation of why it does not(if applicable)

@gitpod-io
Copy link

gitpod-io bot commented Nov 16, 2022

@NeilAn99
Copy link
Contributor

I think it might be nice to provide an example of a blog URL, so users who don't know what HTML and XML are know what to provide.

@cychu42
Copy link
Contributor Author

cychu42 commented Nov 16, 2022

Maybe, but there are many different sites, so I'm not sure it's practical to list them all or useful to list only one.

@NeilAn99
Copy link
Contributor

I think maybe one example would be fine, I think most people use dev.to. But just a simple example, something like:

Blog URL: https://dev.to/user
vs
Blog feed URL: https://dev.to/feed/user

@TueeNguyen
Copy link
Contributor

Agree with @NeilAn99, let's add examples of blog url and feed url in 2 separate lines

@cychu42
Copy link
Contributor Author

cychu42 commented Nov 17, 2022

OK, how about this?
image

Copy link

@batunpc batunpc left a comment

Choose a reason for hiding this comment

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

@cychu42 Your implementation looks good!
I have left some initial review that we could address

src/web/app/src/components/SignUp/Forms/RSSFeeds.tsx Outdated Show resolved Hide resolved
@@ -8,6 +8,8 @@ const ChannelFeeds = () => {
<RSSFeeds
title="YouTube and Twitch"
prompt="OPTIONAL: Enter your YouTube and/or Twitch channel"
promptExample1=""
promptExample2=""
Copy link

@batunpc batunpc Nov 17, 2022

Choose a reason for hiding this comment

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

Making the prop optional and assigning a default value like empty list, will ensure that nothing will break and would not have to make changes here.

src/web/app/src/components/SignUp/Forms/RSSFeeds.tsx Outdated Show resolved Hide resolved
@cychu42
Copy link
Contributor Author

cychu42 commented Nov 18, 2022

@batunpc Good ideas! I made some changes accordingly.
The only thing I didn't do is assigning a default value, because it doesn't look like the existing code does it for other variables of type RSSFeedsFormProps , but I did make the promptExamples array optional and make sure nothing would render if there's no value assigned.
For instance, the next page renders using the same type without any example.
image

@cychu42 cychu42 requested a review from batunpc November 18, 2022 19:19
batunpc
batunpc previously approved these changes Nov 18, 2022
Copy link

@batunpc batunpc left a comment

Choose a reason for hiding this comment

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

Thank you @cychu42 , great job 👍

@cychu42
Copy link
Contributor Author

cychu42 commented Nov 19, 2022

Thank you all for the reviews. I just rebased and squashed the commits, after the approval.
I guess I'm now waiting for a reviewer with write access to allow merge to happen.

@cychu42 cychu42 requested a review from batunpc November 19, 2022 01:22
batunpc
batunpc previously approved these changes Nov 19, 2022
@manekenpix
Copy link
Member

manekenpix commented Nov 19, 2022

Last minute suggestion:

The text looks a bit bloated and hard to read, what about something more simple? maybe a basic but clear indication of what valid and non valid blog URLs are:

image

It doesn't have to be exactly this ^, but maybe something a bit cleaner would be better for users? It could also include links to blog URL vs feed URL explanations or definitions, or Blog vs Post (some people think a post is a blog).

I'm also ok if the team decides that the changes proposed in this PR are the way to go.

@cychu42
Copy link
Contributor Author

cychu42 commented Nov 23, 2022

What if we use some shorter text instead:

Enter your blog root URL (HTML) and select the blog's RSS feed URL (XML) you want to use in Telescope, such as:
Blog root URL: https://dev.to/user
RSS feed URL: https://dev.to/feed/user

The 2 examples can be smaller texts like you suggested.

@manekenpix
Copy link
Member

manekenpix commented Nov 23, 2022

What if we use some shorter text instead:

Enter your blog root URL (HTML) and select the blog's RSS feed URL (XML) you want to use in Telescope, such as:
Blog root URL: https://dev.to/user
RSS feed URL: https://dev.to/feed/user

The 2 examples can be smaller texts like you suggested.

@cychu42 Yeah, I think that'd work.

* Turn examples into an array
* Fix Eslint error
* Shorten the prompt and resize URLs
@cychu42
Copy link
Contributor Author

cychu42 commented Nov 25, 2022

OK. I updated it. It now looks like this:
image

For the prompt examples, I used the same font size as the formControlLabel class (the RSS URL(s) that shows after validation), which is smaller than the prompt.

Copy link
Member

@manekenpix manekenpix left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@manekenpix manekenpix merged commit e58aa60 into Seneca-CDOT:master Nov 25, 2022
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.

6 participants