Project Collections are a way to customize and control the way projects are displayed on the Manifold homepage. Following the Feature section, Collections displace a publisher’s library of projects on the landing page in favor of “blades” or “blocks” of projects curated manually or algorithmically around specific subjects and tags. Thus, instead of showcasing a library of projects, ordered only by title, it is possible to portion out the Manifold landing page by theme, around specific events or conferences, current events, or as a means to suggest titles to readers they may not have otherwise considered to be of interest.
Only those collections denoted in the backend to
Show on homepage will appear on the Manifold landing page. There is no artificial limit to the number of collections that can appear on the homepage, but the more collections that appear, the longer a reader will need to scroll to review those projects to which you wish to draw attention. Conversely, if only one collection is marked to show on the homepage, only that collection will appear, followed by links to see projects on the instance or, for those who are logged in, a link to those projects that are being followed.
All collections marked as
Visible in the backend, regardless of whether they are set to appear on the homepage, will appear on an instance’s Project Collection page, accessible by clicking
See Project Collections at the bottom of the Projects page. Collections that are not set to be visible will not appear on either the homepage or Project Collection page.
This section is broken up along the following themes:
- Creating a New Project Collection
- Modifying Existing Project Collections
Creating a New Project Collection
To create new or modify existing project collections, a user will need to log into the Manifold backend with Administrator, Editor, or Marketeer credentials. From the backend dashboard, navigate to the
Projects menu and then select
Project Collections from the submenu:
Below the sidebar of existing collections there will be a button to create a new collection. Once clicked a drawer will open from the right side of the screen allowing you to create either a Manual or Smart collection.
Manual Collections allow a user to cherry-pick any project in the project library and add it to the collection.
The collection title appears at the top of the collection blade beside the collection icon. The input for this field is plain text. Formatting for things like bold, italic, or hyperlinks are not possible here for collection titles.
The description field allows a user to orient the reader to the contents of the collection. This field accepts Markdown input, so limited text formatting is possible with bold, italic, and hyperlinks. The text from this field is rendered below the project title and above the first row of project thumbnails on the frontend.
The visible slider enables the user to create a collection and toggle whether or not readers can access it from the frontend. If toggled off, the collection won’t appear on the homepage or on the Project Collections page. If toggled on the collection will appear only on the Project Collections page. See below for how to make a collection appear on the homepage.
Show on Homepage
This toggle allows users to showcase their collection on the instance’s homepage, so long as it is also toggled to be visible. It is not possible to have a project collection appear only on the homepage and not on the Project Collection page.
When a new collection is created a user must select one of the available icons to associate with it. It is not possible to customize or add new icons to the system at present. The collection icon will sit beside the collection title on the fronted.
Once saved, this new manual collection will be empty. To populate it with titles see the section on Adding and Removing Projects from an Existing Collection.
Smart collections allow users to set certain filters that, when they are satisfied by a project, allow Manifold to automatically include them in a collection. Presently the available filters are a project’s status as being Featured, as well as what Subjects and Tags are associated with it.
The fields required for a Manual Collection—Title, Description, Visible, and Show on Homepage—are likewise required for Smart Collections. However to properly calibrate a smart collection, the following fields are also required:
This field expects numerical input and controls how many projects that meet the collection’s filter criteria are displayed in the Smart Collection.
This works in conjunction with the collection’s sorting preference—Newest, Recently Updated, Title A–Z, or Title Z–A—which is available to define once the collection has been created. (For more on how to adjust the sort preference, see the Ordering Collection section below.)
Thus if the collection’s filters match twenty projects and a value of
10 is set in this field, only the ten newest or the ten most recently updated or the first or last ten alphabetical entries will appear in the collection.
This provides a user a means to have a wide filtering criteria while only surfacing a specific subset. For example, if a collection criteria is set to include only featured projects, it is possible with this setting to showcase only a certain number of the most recently updated featured projects.
If this field is left blank, the system will not limit the collection by any sorting preference; all projects that match the search will appear in the collection.
The Featured Projects slider is a filter that allows a user to limit a collection to only those projects that have been marked as being Featured. Enabling this slider does not prohibit other filters from also shaping the contents of the collection. Thus it is possible to have a collection made up of only featured projects that also have a specific Subject or Tag associated with them.
The Subjects field allows a user to type and then select from the list of established Subjects in the instance to use as filters to determine which projects are included in the collection. For example, if there is a
History subject in the instance, and it is selected here, only those projects that have been associated with
History will appear in the collection.
More than one subject can be included in the collection criteria, and they can be paired further with the Featured Projects field, and project Tags, also described in this section.
To remove a subject from the criteria, simply click the
x beside its name below the
Add a Subject button.
The Tags field allows a user to type and then select from the list of Tags being used in the instance to use as filters to determine which projects are included in the collection. For example, if there is a tag for
australia in the instance, and it is selected here, only those projects that have been associated with
australia will appear in the collection.
More than one Tab can be included in the collection criteria, and they can be paired further with the Featured Projects field, and project Subjects, also described in this section.
To remove a tag from the criteria, simply click the
x beside its name below the
Add a Tag button.
Modifying Existing Project Collections
The Project Collections page will display a list of existing collections on the left sidebar. The sidebar displays the collection’s title, number of projects in the collection, a toggle to quickly change its homepage visibility status, and a handle to manually adjust the order of their appearance on both the home and collection pages by dragging and dropping.
To adjust the collections further, or to delete a collection outright, click on a collection title. Doing so will display a grid of those projects in the collection with a header to adjust its settings.
Adjusting a Collection’s Settings
When you click on a collection’s
Settings button, a drawer will open from the right allowing you to modify all of the fields that were set when the collection was originally created. Additionally there are options to delete the collection or adjust its slug as it appears on the collection page (e.g.,
Ordering Projects within Collections
When a collection is selected, a user can adjust how the projects within the collection are sorted and displayed for readers through two means: a dropdown that offers four sorting options (Newest, Recently Updated, as well as forward and backward alphabetization) and the
Order Manually slider.
Order Collection By dropdown is available for both Manual and Smart Collections. From this dropdown a user can choose to order projects in the collection by four different criteria:
- Newest. Newest titles are those that have been most recently added to the instance and not the collection, specifically.
- Recently Updated. This speaks to the date a project has been modified with the addition or a new text, resource, or added/updated metadata.
- Title A–Z. Ordering the projects alphabetically by title.
- Title Z–A. Reverse alphabetical order of the projects by title.
This dropdown works in conjunction with the
Projects Visible field, allowing users to, say, create a collection of eight most recently updated projects in a certain subject area.
For Manual Collections an
Order Manual slider is available. If activated the
Order Collection By dropdown will disappear and a user can reorder the projects within the collection manually by dragging and dropping them with their mouse.
Adding and Removing Projects from an Existing Collection
To add projects to a Manual collection, select the collection from the sidebar and then click the
Manage Projects button beneath its name. A drawer will slide open from the right, showing a paginated view of all the projects on the instance.
From this view projects can be added to the collection by clicking on the green plus sign beside their thumbnail. The green plus sign will then turn to a blue checkmark. Conversely, projects that have been added can be removed by clicking on the blue checkmark.
Users can scroll through this paginated view to review which projects to add or use the search bar to find those of interest more directly.
To add or remove projects from a Smart Collection, a user needs to adjust the filters by which the system is evaluating projects for inclusion in the collection.