give me the erd based on the below steps

Start with User Supertype:

Draw a box labeled "User" for the supertype.

Inside, list common attributes: UserID, Nickname, Status, Name, Twitter Handle, Facebook Page Link, SMS Contact Number.

Draw two lines from the User box to create subtypes: "General User" and "Group Member".

Site Supertype:

Draw a box labeled "Site" for the supertype.

Inside, list common attributes: Site ID$,$ Site Name, Site Purpose, Site Creation Date.

From the Site box, draw lines to create subtypes: "Public Site" and "Private Site".

Group Entity:

Draw a box for "Group" with attributes: Group ID$,$ Group Name, Date Created, Date Terminated, Purpose, Number of Members.

Draw a many$-$to$-$many relationship between "Group Member" and "Group".

For "Private Site", draw a relationship indicating it's associated with one or more "Groups".

Account and Posting:

Draw a box for "Account" with the necessary attributes and ensure it's linked to both "Public Site" and "Private Site" through the user's relationship.

Draw a box for "Posting" with attributes and relationships to "Account".

Complaints:

Add a "Complaint" entity with attributes: Complaint ID$,$ Date$/$Time Posted, Content of Complaint, Resolution Code, Date of Resolution.

Link "Complaint" to "Posting" to represent the relationship where a complaint is filed against a posting.

Add Additional Details:

Include attributes for each entity as discussed.

Use lines to represent relationships, adding arrows or crow's feet to indicate the nature of the relationship $($one$-$to$-$many, many$-$to$-$many, etc.$).$

Use a triangle symbol to represent the supertype$/$subtype relationships, pointing from the supertype to its subtypes.

Annotations:

Annotate relationships with cardinality $(1$:$1,1$:N$,$ N:M$)$ and roles, especially for the User, Group, and Site entities to clarify the access control for public vs$.$ private sites.

By following these steps and organizing the entities, attributes, and relationships accordingly, you can create a comprehensive ERD for the VC database's final phase. This visual representation will aid in understanding the database structure and how it supports the platform's functionalities and requirements.