- There are two diffent login type : members and admins.
- Members can open book advertisements.
- The ads can be listed after Admins approve the ad.
- After a member added a new ad on system, this ad will be listed in Admin's Awaiting Approval Page.
- Approval processes are listing on Approval logs page with process details like Admin Id,date etc.
- Making ads active or inactive is possible for Members also Members can delete their ads.
- While opening a new ad, members have to search author and book. If author or book (or both of them) is not registered in library, members have to have add them. Thus, the author and book will be added and other member can use them in the future.
- Books and authors are listing in Library page.
- Authors and books have individual page.
- In Author's page, the books whose belongs that author are listing.
- In book page, The active ads which related to that book are listing.
- Global state management provided with Context Api + Hooks. Every induvidual member accesses their own pages with their Member Id's.
- Role based authorization added. It was provided by JWT Tokens.
- After members logged in the system, they are given an object from backend which includes access token, roles and member Id. This informations are storing in global state management to ensure secure routes and communicate with backend.
- Passwords are saved to DB via hashing. I used Bcrypt as a hashing algorithm.
.Net 5.0 with Entity Framework Core + Mssql.
React.js with Semantic Ui,Axios,React Router Dom.
