Four step registration process and admin area - DevDiary #4
Last week I wrote that only some legal writing and the admin area are missing. I forget about one thing: The registration process. I decided it needs to be a four-step process, but I will talk with David about that again. Usually, I implement details how I see fit and then speak with David about it. I don't want to write for every single thing. That is what I did last week.
There is now this menu at the bottom of every page. There are symbols for social networks (not linked, though and kofee doesn't have that many social networks) and links to legal texts. It still needs something like a "terms and conditions for usage", so that we are legally allowed to use their logos and images on our website. Legal stuff is such a complicated mess. I prefer writing code :D
This is the first step of the registration process: Mail and Password you want to use for the account. Those are the information that firebase authentication will save for us. Then a verification email is sent.
After pressing on registration, the user has to verify the given email. That is what the page is asking for. If you press on the button, you get another email. We can't have people spam our database with fake organisations by using a lot of counterfeit mails. I don't believe it will happen, but I know someone could do that and I can't accept that.
After the email was verified, we ask some personal information from the person. Who are you? How can we call you? What type of organisation do you represent? The last one is important because we are a voluntary work organisation, not a job search platform. We don't allow every form of organisation on our platform, at least not without a chat. Those data are saved in a database, that can neither be read nor modified from the outside. That information is personal information that should be protected. The only person that can read it is me. Firebase security rules are beneficial in that case.
You should already know this form. It is the organisation's data form. We moved it at the end of the registration process because we don't need accounts without representations.
After creating the organisation on our platform, the card is marked as private until an admin makes it public. Now that I think about maybe there should be the option to ask to make it public, instead of the Admin just assuming the card should be openly accessible. Let's talk about admins. They are saved in a list, that can only be read. I still struggle to give the admins permission they need. It should be possible with firebase security rules, but I didn't manage to achieve that yet. Because of that, there is no image of the admin area. It is no ready at all. I will need another week to finish it.
Last week I also talked about my other project: An eBook reader for my book Tales of Nowardo. I didn't change anything except the content. I released it as a beta. The design will change, and I will implement an option to leave comments. And of course, I want to track my visitors. At the moment, I have no idea how many people visit my site and how far they read. And I want to know where they are from and so on for pure curiosity. You can check it out here: http://tales-of-nowardo.com/
There is now this menu at the bottom of every page. There are symbols for social networks (not linked, though and kofee doesn't have that many social networks) and links to legal texts. It still needs something like a "terms and conditions for usage", so that we are legally allowed to use their logos and images on our website. Legal stuff is such a complicated mess. I prefer writing code :D
This is the first step of the registration process: Mail and Password you want to use for the account. Those are the information that firebase authentication will save for us. Then a verification email is sent.
After pressing on registration, the user has to verify the given email. That is what the page is asking for. If you press on the button, you get another email. We can't have people spam our database with fake organisations by using a lot of counterfeit mails. I don't believe it will happen, but I know someone could do that and I can't accept that.
After the email was verified, we ask some personal information from the person. Who are you? How can we call you? What type of organisation do you represent? The last one is important because we are a voluntary work organisation, not a job search platform. We don't allow every form of organisation on our platform, at least not without a chat. Those data are saved in a database, that can neither be read nor modified from the outside. That information is personal information that should be protected. The only person that can read it is me. Firebase security rules are beneficial in that case.
You should already know this form. It is the organisation's data form. We moved it at the end of the registration process because we don't need accounts without representations.
After creating the organisation on our platform, the card is marked as private until an admin makes it public. Now that I think about maybe there should be the option to ask to make it public, instead of the Admin just assuming the card should be openly accessible. Let's talk about admins. They are saved in a list, that can only be read. I still struggle to give the admins permission they need. It should be possible with firebase security rules, but I didn't manage to achieve that yet. Because of that, there is no image of the admin area. It is no ready at all. I will need another week to finish it.
Last week I also talked about my other project: An eBook reader for my book Tales of Nowardo. I didn't change anything except the content. I released it as a beta. The design will change, and I will implement an option to leave comments. And of course, I want to track my visitors. At the moment, I have no idea how many people visit my site and how far they read. And I want to know where they are from and so on for pure curiosity. You can check it out here: http://tales-of-nowardo.com/
Comments
Post a Comment