pull down to refresh
@bitcoinplebdev
625,760 sats stacked
stacking since: #50813longest cowboy streak: 11 verified stacker.news contributor
588 sats \ 1 reply \ @bitcoinplebdev OP 31 Mar \ parent \ on: PlebDevs Release - Complete UI / Layout Refactor devs
Fixed! @BlokchainB
You can manually mark lesson as completed now in the more options dropdown
Once all lessons in a course are completed the course is marked as complete.
Let me know if you have any more issues with this!
Course Tracking improvements are being worked on right now, sorry about that! Will also have a manual checkbox soon to mark lessons as completed manually so you can check off the course yourself
If you go to the course you should see lessons marked as completed (or not) (if you complete the missing one's you'll get your badge issued)
Amazing thank you so much for the thorough feedback!
I agree with you in general about the JavaScript portion. This is a big jump and ideally I would like to do this in more baby steps (probably 3-4 individual lessons). I am planning on updating / improving the starter course soon (this was the first version and I actually filmed it in a single weekend lol) so a lot of little improvements I want to add!
I'm generally not a fan of quiz's (and it's a lot to build into the platform) but a few people have suggested it so far so I'll consider how it could be done easily.
Coding exercises are something that is a little more realistic and doable. There are repo "submissions" built into the platform so I could lean into this more (requiring submission for most lessons) but also embedding a codepen directly into a lesson is possible as well.
The lesson tracking can be a bit fickle still... In general it should trigger a lesson as completed after 80% of the video has been watched but this doesn't always trigger correctly. I think I will add a manual checkbox to allow you to mark it as completed if the auto lesson tracking doesn't work. I know progress is important and I want to make it encouraging and seamless on the platform! Still a ways to go.
Things will keep improving, thank you again for the support and feedback!
Dude yeah great to meet, and thank you! I wont dox you don't worry haha
I'm following you on Github now so keep pushing commits and let me know if you get stuck again 🫡
Sorry about the trouble... Wanna jump on call today? I think we can figure this out in a few mins probably
This is a super common Git authentication issue! I have to do some googling everytime I go through this process myself, it's kind of annoying...
- First, ensure you've configured Git with your GitHub email and username:
git config --global user.name "Your GitHub Username"
git config --global user.email "your@github.email"
- Create a personal access token (PAT) on GitHub:
Go to GitHub.com → Settings → Developer settings → Personal access tokens → Tokens (classic)
Generate new token
Select repo scope
Copy the generated token
- When pushing, use HTTPS with your token:
git remote set-url origin https://YOUR_GITHUB_USERNAME:YOUR_PAT@github.com/YOUR_USERNAME/YOUR_REPO.git
Finally you can try:
git push -u origin main
If you're still having issues, verify:
- Your GitHub account has write access to the repository
- You're using the correct repository URL