Duchess Meghan Markle's coat of arms revealed by Kensington Palace

Just six days following the wedding of the year, Kensington Palace released details of Duchess of Sussex's new coat of arms. The announcement was made on Friday morning after the queen approved the details, alongside Mr. Thomas Woodcock, the Garter King of Arms and Senior Herald in England.

According to the palace, Meghan worked closely with the College of Arms to create her personal coat, in order to show her own style and history.

Meghan's coat includes a blue background, representative of the Pacific Ocean, and two rays to show her California roots. The depiction also includes three quills to demonstrate "communication and the power of words." The flowers included on the grass show poppies, California's state flower, and wintersweet, which are grown at Kensington Palace, the couple's new home. The florals were all also included in Meghan's intricately designed wedding veil.

This content is not available due to your privacy preferences.
Update your settings here to see it.

Kensington Palace also explained that the Coronet, which was "assigned" to the new Duchess, is the "Coronet laid down by a Royal Warrant of 1917 for the sons and daughters of the Heir Apparent." It also shows the arms of a married woman with those of her husband, side by side. The left hand side of the arms are to represent Prince Harry.

Related: More times Meghan has deviated from tradition:

This content is not available due to your privacy preferences.
Update your settings here to see it.

And in true Meghan fashion, the coat seemingly broke royal protocol. The coat is typically given to the bride's father ahead of her royal wedding, but given the circumstances, the coat was given directly to Meghan herself -- a huge break for the crown. Kate's coat of arms, which were given to her father ahead of her 2011 nuptials to Prince William, included three acorns to represent the three Middleton children.

Related: Royals break their own protocol

This content is not available due to your privacy preferences.
Update your settings here to see it.