The Drupal CMS utilizes various “taxonomies”, “content types”, "nodes", “views”, and “blocks”.

• Taxonomies are groups of terms or phrases used to classify content.  For instance, most blogs utilize two particular types of taxonomies- categories and tags.  In Drupal, content can be applied to various categories called 'taxonomy terms'. Generally, the word 'taxonomy term' is interchangeable with what you might think of as a 'category'.  Content that can be tagged with categories are actually taxonomy terms that are managed through the Drupal taxonomy interface.
• Vocabularies are the groups of taxonomy terms
• Taxonomy Terms are individual classifications

• Nodes represent each entry/post/record saved in Drupal.  For example, an 'About us' page is a node, each team member bio is a node – essentially every piece of individual content is referred to as a node. Site administrators use forms with a predefined set of fields to visually create the node, which is then stored in the database. When a user visits the site, the node content is pulled from the database and passed to the design templates, which is how the end result is displayed on the screen.

• Content Types represent generalized types of content used on the site.  Content types are custom created based on the needs of the site.  An easy way to understand content types is to know that anything in the 'create content' menu is a content type.

• Paragraphs - when listed in a specification document, this refers to a custom data object. The "Paragraphs" Drupal module allows data architects to define a group of custom fields for repurposing,such as the fields used to represent all the content of a single slide in a slideshow (headline, caption, link, picture). In turn, there may different formatted slideshows on various types of content, but at their core, the building blocks/foundation remains the same.  When a collection of fields are defined in a paragraph bundle, content managers have the flexibility of deciding the display order and position within the templated layout.
• Field Collections - when listed in a specification document, this refers to a custom data object that can be repurposed.  When a collection of fields are defined in a field collection, the rendered data has a fixed position in the templated layout. 
• Blocks represent repurposable/preformatted components (sometimes referred to as widgets).  On many websites, this would include secondary navigation/menus, calls to action, advertisements, etc.
• Beans represent blocks with custom fields and layouts.

• Views represent data driven components to the site.  These components can be an entire page, such as the news landing page, or blocks, such as “recent news” that might appear in the sidebar of a page or on the homepage.

• Entities represent data objects or data representations.  These may include individual content types, paragraph types, blocks, views.

In addition, your website's design may include these industry-standard components/features:

• Callouts/Call-To-Actions (CTAs): Callouts usually consist of a small to medium sized image with a descriptive link that site visitors can click on. Callouts are used to visually compel visitors to other important areas of the site.
• Hero Images:  large-scale image typically featured on the homepage of a website or a landing page.  They usually take up the majority of the browser window.
• Masthead Images/Banner Images:  panoramic/wide-scale images shown across the top of the page, generally as part of the header or immediately following it.