-
Notifications
You must be signed in to change notification settings - Fork 3
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
Issue 13 fix guides page #19
Issue 13 fix guides page #19
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are you putting underscores at the front of guides? The html and markdown have no _ at the start
The only reason is to keep thing consistent in the _includes folder. |
@barton2526 was it a question or suggestion to change? could you please be more specific? |
I'm not familiar enough with the original rationale to say. Perhaps @RoboticMind knows |
Underscores tell Jeykll to not try to build that file or folder directly.
https://jekyllrb.com/docs/structure/ Technically the files in the _include directory don't need to have and _ in front of them because the folder is already ignored. The files were like that before I started working with the gridcoin.us site and I've just kept it consistent with that. I would have no issue changing it to not have underscores in that folder as long as you change all the |
@RoboticMind I think it would be better to have separate issue for that as this is not related to this one. Plus it would be easier to test. wdyt? |
any other issues with this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With some of the more detailed guides being removed, the guides there look like they might need some changes
</li> | ||
</ul> | ||
</li> | ||
<li>Send a beacon.</li> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs a whole step like it had in the more detailed guides. Sending a beacon involves multiple steps
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This step will require screenshots and a lot of text. This simplified stepper probably not a very good fit for it. It will look very cluttered. I think it deserves a separate page. What if we will have here a link instead to the individual page here instead?
I can refer to the .us website page temporarily (https://gridcoin.us/guides/earn-grc.htm) and have a ticket to craft the page later as a part of .world website. wdyt?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would work for now
</h3> | ||
</header> | ||
<div class="step-body"> | ||
<h4 class="h5">Check Your Projects</h4> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might want to mention the GDPR requirements some projects have somewhere in here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, good point. Also I think the GDPR should be mentioned on whitelist page also. Perhaps it worth to create an to extend the whitelist page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I created the issue with a requirements to extend whitelist page with GDPR requirements.
Updates at this section is a part of that task.
Co-authored-by: RoboticMind <[email protected]>
…n-World-Site into issue-13-fix-guides-page
@RoboticMind please have another look at this PR. |
And I think it is worth to deploy it despite the fact that some parts are missing. Those issues could be addressed as another PR. I believe this improvements worth to have deployed, it should be better anyway. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I read over it again and noticed a few other issues with the wording/outdated information
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Can you squash some of these commits? Will merge after that
That option would result in one commit. I think Robotic meant to reduce 22 to a more manageable number, but still keep them modular (ie >1) |
I understand, so I tried before your message doing this in a regular way (rebase ~10, the mark as squash) but seems like because this branch is already on a remote I can not rewrite the history. |
You need to squash locally and then force push to |
Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_solo_crunching.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_boinc_introduction.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_solo_crunching.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_solo_crunching.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_pool_crunching.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_solo_crunching.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_solo_crunching.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_staking_only.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_solo_crunching.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_pool_crunching.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_solo_crunching.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_boinc_introduction.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_solo_crunching.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_solo_crunching.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_pool_crunching.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_solo_crunching.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_solo_crunching.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_staking_only.htm Co-authored-by: RoboticMind <[email protected]> Update _includes/_guides/_solo_crunching.htm Co-authored-by: RoboticMind <[email protected]>
8bf7cce
to
d03b300
Compare
@barton2526 thank you, --force did a trick! |
@RoboticMind can we have it merged now? |
Merged |
Fixes #13
Note: We need to improve the content of the guides. Since the solo crunching guide looks OK, the other two are definitely need some attention. While working on this issue I almost didn't touch the content itself as I can not consider myself as a tech writer (furthermore I ain't no native speaker) so I just removed non-related text from there. The guides on the original .us website for pool and staking-only aren't detailed enough and a little bit rather confusing, so perhaps some work needs to be done there as well to my opinion.
Hence I suggest to not rely on the content of this PR but rather have additional issues to adjust content.