1. Please don't send plain text passwords. This might just be me, but man, that bums me out to EVER see my password.
2. Ok, so I just activated. Tell me better what to do here.
3. You can register for a class twice.
4. Remind me that once I enroll, the stuff is coming via email.
What's your plan going forward time wise? Still four hour chunks? Will you be keeping the blog up to date with that sort of info? I personally find it interesting.
* Gotcha... I'll change that soon
* Gotcha
* Yep, needs tweaking.
* Good idea
* Yep, I can't really do more than 4-hr chunks. With the blog, I've intended on keeping it updated daily but that hasn't happened. I will very much be keeping it updated with info as much as I can.
I'm planning on making a key change tomorrow based on the usage I've seen today i.e. if someone is not logged in, instead of telling them "Hey, log in or register", it will create a temporary user for them with the enrollment... and send them an email saying "Hey, you enrolled into this course. Click here to activate your account and confirm your enrollment."
After that change is made, I'll write another blog saying "I lost XXXX number of people who tried to enroll but couldn't because they were not logged in and they didn't register. Here's how I solved the problem..."
1. Use that valuable h1 tag (and h2) on every page to tell me something (and Google) about that page - something good and rich. Don't waste it on my name - or if you do, I should be allowed to say something about myself. Or there should be something else there. Just an important tag that I'd hate to waste.
2. Your image alt tag for your log needs improvement. Also a text tag line would be a good thing.
3. Set up a custom route and a field in your db where you make a friendly url for all the courses. "/course/2" should be "/course/how-to-use-brainbank". This should also be your page's title "How to Use BrainBank by _your_name_"
Out of curiosity, will the courses be reviewed? What's stopping me from having you send out something bad for me to anyone who signs up?
Ok, the kitchen won't clean itself.
Instead, store the salted hash of the password, something like sha1(password + 'this string is a secret!'). When a user tries to log in, compute the hash again, and compare it to the one you stored.