Week5 （Aug 5-Aug 13）

Weekly summary：

1. Add a PolicyList for policy edit. From the webUI, users can add their policy and use Xrom to save the policy in the local datebase.
2. Fix some bug in Edit page.
3. Add footer and repository link in the home page.
4. Improve some css.

Next week：

1. Studied the casbin policy and PML-EM rules for vertifing.
2. Store the user information and add a registration interface.

Week4 （July 28-Aug 4）

Weekly summary：

Has reconstructed the front-end.

1. Add a login page for user authentication and Flexibly sign in and sign out.
2. Change the Antd layout as the dashboard frame and reconstructed the routing module.
3. The table component in the home page has been modified for Paging Display.
4. In this frame. we can add/edit an Model/Adapter/Enforcer in another page(not in the home page). In the add/edit page, we can add some rules to get verified Model/Adapter/Enforcer.

Add some api functions for Update/Delete.

Next week：

1. Continue to optimize the web front-end. Add a policy page for edit.
2. Add the backend model for User authentication to manage dashboard user information.
3. Study the casbin rules for vertifing.

Week3 （July 17-July 28）

Weekly summary：

1. Changed the frame.
2. Add login page.
3. Add 404 page.
4. Fixed the edit function.

Next week：

1. Continue to optimize the web front-end.
2. Changed the backend,stuty Xrom frame to return suitable data for UI.

Week1 （July 7-July 16）

Weekly summary：

1. Fixed some bugs and issue10 issue83(https://github.com/casbin/casbin-dashboard/issues/83)(reviewing). Optimizing the web front-end.
2. Studied the Antd frame.
3. Changing the Layout of the UI.

Next week：

1. Continue to optimize the web front-end. Add a policies table on dashboard.
2. Add the User authentication pages for user management.
3. Studied the elementUI and antd, choose a suitable front-end frame for future coding.

Week1 （July 1-July 6）

Weekly summary：

1. Studied the fundamental architecture of Beego. Modifying the routing method and the api.
2. Optimizing the web front-end by react+antd.
3. Studied the casbin policy.

Before coding：

As the casbin is not responsible for User authentication, I think the dashboard needs to have a User authentication procedure to guarantee the security of the casbin platform.

Next week：

1. Continue to optimize the web front-end.
2. Add the User authentication model for user management.
3. Implement some enforcement api.