Constellation.Foundation.PackageVerification 9.1.1.20775

There is a newer version of this package available.
See the version list below for details.
dotnet add package Constellation.Foundation.PackageVerification --version 9.1.1.20775                
NuGet\Install-Package Constellation.Foundation.PackageVerification -Version 9.1.1.20775                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Constellation.Foundation.PackageVerification" Version="9.1.1.20775" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Constellation.Foundation.PackageVerification --version 9.1.1.20775                
#r "nuget: Constellation.Foundation.PackageVerification, 9.1.1.20775"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Constellation.Foundation.PackageVerification as a Cake Addin
#addin nuget:?package=Constellation.Foundation.PackageVerification&version=9.1.1.20775

// Install Constellation.Foundation.PackageVerification as a Cake Tool
#tool nuget:?package=Constellation.Foundation.PackageVerification&version=9.1.1.20775                

VERSION 9.1 is compiled for Sitecore 9.1 use and will not work on earlier versions.
Requires Sitecore 9.1
Requires .NET 4.7.1

Constellation is a collection of utilities for .NET CMS implementers.

The Foundation.PackageVerification library can be used to create NuGet packages that "self install" Items in Sitecore
during the Sitecore initialization process. This can be very handy if your library requires a few "traffic control"
Items or some Core/Sheer/SPEAK Items in order to run. It can also be used to prevent users from breaking your install.

To use, install this NuGet package and review the provided example configuration file. for each Package you want to
"verify," supply the name of the package (must be in the /packages folder) and the ID and database of Items you can use
to determine if the package was previously installed. If these Items are not located, the package provided will be
installed. Results are logged.

It is possible to create your own package processor if your verification needs are more substantial. See the provided
configuration example for where to override package processing on a package-by-package basis.

Product Compatible and additional computed target framework versions.
.NET Framework net471 is compatible.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (12)

Showing the top 5 NuGet packages that depend on Constellation.Foundation.PackageVerification:

Package Downloads
Constellation.Feature.Navigation

Requires Sitecore 10.3 Requires .NET Framework 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Feature.Navigation library addresses the three most common forms of Navigation on Sitecore sites: Declared (static) Navigation: (explicitly defined, may differ from the shape of the content tree) - DeclaredNavigationRepository.GetNavigation - Accepts a Navigation Menu item and assembles a full tree-like ViewModel for immediate processing in your View. If you need context highlighting in your navigation, be sure to pass in the Context Item as well. When using NavigationLink objects, there are usually several opportunities to supply the text of a given link. NavigationLink.GetBestLinkText() evaluates all of them and attempts to supply the best fit. The strategy is based on overriding the concept of "name". Here are the rules: - If Use This Display Name is checked on the NavigationLink item, it wins. - If the Link.Text is supplied by the user, it wins. - If the Link.TargetItem exists and inherits from Page Navigation Title, and the field value is not null, it wins. - If the Link.TargetItem exists its DisplayName is used. - Assuming all other things are not true, use the NavigationLink's DisplayName. Note that in this condition if you intended to point to a Sitecore Item, you have a bad link. Branch (Context) Navigation: (implicitly defined. It follows the shape of the Content Tree) - BranchNavigationRepository.GetNavigation - Accepts the request Context Item (should be a Page) and generates a tree of BranchNodes representing the nearest LandingPage, its children, as well as the descendants of any children that are Ancestors of the Context Item. (will also create Children for the Context Item node in the tree). Use this to produce the expanded navigation seen on many sites with deep content. Breadcrumbs: (implicitly defined. It walks up the Content Tree to get the path) - BreadcrumbNavigationRepository.GetNavigation - Accepts the request Context Item and Context SiteInfo. Generates an array of Breadcrumb models you can enumerate on your View. The breadcrumbs will start on your Site's StartItem and end with the supplied Context Item, which will be marked IsContextItem so you can change your rendering behavior. Uses the Item.Axes.GetAncestors() method to generate the list of breadcrumbs. The included package must be installed to use this library. This should happen automatically after you build and deploy your project.

Constellation.Feature.PageAnalyticsScripts

Requires Sitecore 10.3 Requires .NET Framework 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Feature.PageAnalyticsScripts namespace contains controllers that will render 3rd party analytics and reporting scripts to the page. To get the controllers and supporting Data Templates, the included Sitecore package must be installed This should happen automatically when you build and deploy your project. After installation, some configuration within Sitecore is required. 1. You need to select a location for Page Analytics Scripts Items. 2. For each of the Controller Renderings provided in the package, you need to set the Datasource Folder field to the above location. 3. It is recommended that you create placeholders for the Html Header tag as well as the top and bottom of the Body tags. You can then assign the provided Controller Renderings to those locations in the Standard Values of your most basic Page Items. This module isolates the analytics script kit from actual pages, so you may share scripts on multiple pages (typically every page on a site references the same datasource). You can also "stack" scripts by adding multiple instances of the controller renderings with different datasources. This module does not directly support page/experience editor because: 1. Scripts are invisible 2. Their location in the HTML document may make it difficult to provide access to the rendering. Because maintaining these scripts requires knowledge of Javascript and Marketing Technology, it is recommended that only users familiar with the Presentation Details dialog maintain these objects.

Constellation.Feature.PageTagging

Requires Sitecore 10.3 Requires .NET Framework 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Feature.PageTagging namespace contains controllers that will render the following meta tags when installed on page: - name=keywords - name=description - name=publisher - name=author - name=robots - name=twitter:card - name=twitter:creator - name=twitter:site - property=og:url - property=og:title - property=og:description - property=og:image These tags provide good SEO support as well as good support for Facebook and Twitter. The Sitecore Package in /Installation-Packages must be installed to take advantage of this library. The package includes: - Data Templates for the fields required to support these tags. Your pages should inherit from these to take advantage of this library. - List items where fields have a limited choice of values. - Rendering definitions. The package should self-install when you build and deploy your project. To use, in your Layout, at the appropriate location enter the following: @Html.Sitecore().Rendering("/sitecore/layout/renderings/feature/constellation/page tagging/page metadata") @Html.Sitecore().Rendering("/sitecore/layout/renderings/feature/constellation/page tagging/page search engine directives") @Html.Sitecore().Rendering("/sitecore/layout/renderings/feature/constellation/page tagging/page social metadata")

Constellation.Foundation.Datasources

Requires Sitecore 10.3 Requires .NET 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Foundation.Datasources library is an opinionated information architecture for Sitecore. It includes "base" templates and Item information rules to enforce the architecture. Core Architecture Concept: Web Site Items are one of the following types: Context Datasource: A "page" Item in Sitecore, has a URL, has presentation, loads a Layout and has placeholders for additional Renderings. Subcontent: A "page fragment" Item in Sitecore, specifically an Item designed to be used as the DataSource for a Rendering. It is required for the Rendering to render. Subcontent is optional page content, but is unique to the page it appears on. Widget: Also a "page fragment" Item in Sitecore, specifically an Item designed to be used as the DataSource for a Rendering. It is required for the Rendering to render. Widgets are optional page content, but are designed to be shared by multiple pages. The primary information architecture for this design involves the storage of SubContent vs Widgets. All Pages on a site should get a _subcontent folder beneath them which is where Items of type Subcontent should be stored. This allows for Renderings to specify their Datasource location as "./_subcontent" Widgets should be stored beneath the /tenant/site node (using Helix methodology) typically in a /widgets folder, possibly broken up by widget type or marketing intentions. You can use the following Rule Conditions to enforce this Information Architecture: * ItemIsContextDatasource * Item IsSubcontentDatasource * ItemIsWidgetDatasource * ItemSupportsSubcontent (in some cases Pages should not support subcontent, for example, wildcard pages or pages imported from an external system) You can use the following Rule Actions to enforce this Information Architecture: * CreateSubcontentFolder In general you need a rule like this: On Item Saved, if the Item Supports Subcontent, Create a Subcontent Folder (if none exists) An example is provided in the attached package. After setting up this rule, ensure that your Renderings are organized into Widgets and Subcontent with appropriate Datasources established. Installation: Add this NuGet package to a Web Application project. After building and deploying, this library will automatically install the Sitecore package containing the necessary rules and templates to support this architecture.

Constellation.Feature.Redirects

Requires Sitecore 10.3 Requires .NET Framework 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Feature.Redirects namespace contains two discrete functional components: Page Redirects: Items that are meant to be interspersed with Page type Items in the content tree so that dynamically generated navigation will list these Items as if they were part of that tree branch, although the actual target is elsewhere, or an entirely different site altogether. Marketing Redirects: Items that represent "short, catchy" URLs that then redirect deeper into the site. Also a way to teach search engines about URLs that have been permanently relocated. Marketing Redirects are managed through a discrete "application" in the Sitecore desktop. Exporting and importing redirect lists is supported. All redirects are tested for validity before they are allowed to be imported. The porting and development of this library has been kindly supported by Verndale (verndale.com)

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
10.3.0.23221 3,947 6/16/2023
10.2.0.29227 18,227 11/12/2021
10.1.0.26447 8,592 3/4/2021
10.0.1.16481 6,996 8/6/2020
10.0.0.22406 7,006 8/4/2020
10.0.0.22217 503 8/4/2020
9.3.0.27935 6,290 6/4/2020
9.1.2.20552 16,746 4/11/2019
9.1.1.20775 7,942 3/6/2019
9.1.0.29104 8,152 12/6/2018
9.1.0.21607 1,644 12/6/2018
9.0.6.25105 7,899 10/20/2018
9.0.5.23264 13,251 10/4/2018
9.0.4.16508 3,254 8/15/2018
9.0.3.21612 4,768 6/15/2018
9.0.2.26899 3,051 5/30/2018
9.0.1.29093 2,355 5/29/2018
8.1.3.18004 520 5/18/2020

Updated to renumbered Sitecore NuGet packages