The General sidebar provides controls for the most top-level elements for how a project is registered and displayed across the system.
Use this field to update the project title, which displays on the project library and landing pages, as well as associated navigation menus. This field cannot be left empty.
Use this field to add or update the project subtitle, which displays alongside the primary title. This field is not required.
A publication date is required by the system to generate citations. The date input here refers to the project as a whole (versus individual texts contained within the project) and will be superseded by a publication date associated with specific texts).
A URL slug describes the exact address of a project on a Manifold instance. In the following example,
the-lab-book is the slug for a project of the same name on the University of Minnesota Press’s instance. The system will automatically create a slug for each new project based on the project title. You can use this field you can adjust the slug as needed.
This table allows you to modify or customize the avatar representing the project, which displays in the library on the landing page. If no custom avatar has been added to the system, the default icon—made up of eye glasses, a dialog bubble, and a pencil—shows in the left panel.
You can adjust the color of the default icon by selecting from one of the six preset options in the middle panel labelled
You can also upload (as a JPEG, TIFF, GIF, or PNG) a new avatar using the right panel labeled
Custom. All custom uploads should be no less than 400px along their shortest dimension.
Note that even if you add a book cover to display in the project’s hero block, you will also need to add it here as a custom image for the cover to show in library views.
Subjects provide a means to categorize projects, which readers can use as filters to sort through the collection of projects on the landing page (see Projects Library).
Subjects can only be created by users with Administrator roles. All other roles that can access the backend can only select from the list of subjects already loaded into the system. To associate a subject with a project, simply begin typing in this field, and the system will populate those subjects in the system that most closely resemble what you are typing. Once accepted the Subject name will appear beneath the
Add a Subject field alongside any others that have been associated with the project.
Unlike Subjects, Tags can be created by any user who has permission to modify a project and can be used to add further richness to the existing subject classification. Like Subjects, the Tag field provides a helper so that as you begin typing any similar tags that have already been created on your instance will be revealed.
To see how Tags can be used to curate Smart Collections, visit the Project Collections page.
For use when wanting to load and edit a project and its materials before publishing it for a broad readership. When toggled on, projects are only visible to users logged in with Administrator, Editor, or Marketeer roles—and to Project Creators on projects where they have
Can Modify Project permissions. New projects are set to Draft Mode by default, and Draft status is denoted in the project library, as well as on the project landing page.
When a project is in Draft Mode, users who have permissions to view the project may annotate, highlight, and even share texts that are part of the project. Links shared on social media will only work for those who also have permission to access the project and are logged in. All annotations, comments, and highlights will persist with the project’s text when Draft Mode is toggled off.
Determining when drafts are made public falls to the discretion of publishers.
Featured projects take pride of place on the home page in a section of the library all of their own. Only four projects display in this section at a time. If more than four projects are toggled to be featured, only the four most recent will show. By default, new projects are not set to be featured.
The Finished toggle is a means to indicate that a project is no longer actively iterating. When toggled on, Manifold will show the project’s published date rather than its last updated date in lists. When the switch is off, Manifold will show when the project was last updated.
Standalone Mode renders Manifold projects as distinct microsites. The standard Manifold landing page that showcases collections of projects—or a publisher’s entire content library—is not always appropriate or useful.
In situations where an instance only has a handful of projects or when a publisher wants to incorporate Manifold as part of their existing web presence, Standalone Mode can be employed as a solution.
Any Manifold project can be rendered in standalone mode or in library mode. Using the dropdown, users can configure the most appropriate rendering for a project:
- Disabled. If standalone mode is
Disabled, the project can never be viewed in standalone mode. This is the default setting for new projects.
- Enabled. If standalone mode is
Enabled, the user must come to that project with the following suffix appended to the URL for standalone presentation; otherwise users will encounter the default library view of the project:
?mode=standalone. This is useful for publishers who want to present a project as standalone when directed from a specific location (e.g., a publisher’s or author’s website), while allowing the same project to be viewed in library mode for those arriving to it from other locations.
- Enforced. If standalone mode is
Enforced, that project can only be viewed in standalone mode regardless of from where a user is coming to the project. Additionally, projects that are enforcing standalone mode are removed from the projects page library and the landing page, in cases where the instance isn’t displaying project collections.
When a project is offered in standalone mode, the header is replaced with a more minimal standalone header that persists down the page as a reader scrolls. The project’s title and subtitle are integral to this standalone header and serve as clickable links, returning users to the project landing page as they explore subpages within the project.
Additionally, when a project is in standalone mode, the following behaviors can also be expected:
- the standalone header will respect whether the project hero is set to light or dark mode,
- search in the project is scoped to the project,
- the reader menu only includes a link to the project, and
- project subpages for individual resources or resource collections show the standalone header with no breadcrumbs.
These settings work in conjunction with the top bar configurations, which can be adjusted on a project-by-project basis or generally across an entire instance.
See the Top Bar section below to adjust an individual project’s top bar text and link URL. Those with Administrator credentials can modify the top bar globally across the instance—its text, link URL, color, and behavior—on the Theme Settings page.
If you enable or enforce standalone mode on a project but don’t see a top bar on your project, check that the
Top Bar Text and
Top Bar URL fields (described below) are filled in. Or, if the project is intended to follow the default instance top bar theme, check the Theme Settings page to see that Top Bar Display Mode is not set to
Top Bar Text
The top bar is a thin, customizable band that serves as a means to contextualize a Manifold page for readers in relation to a larger mission.
- The top bar color and display parameters are only configurable for users with Administrator credentials from the Theme Settings page.
- If this field is left blank, the top bar settings for the project will default to the instance-wide settings
- The top bar is not required for standalone projects; it is highly configurable and can used on a project-by-project basis or it can be used in conjunction with standalone projects settings or generally across the entire instance.
- This field is not Markdown enabled and only accepts one line of text.
Top Bar URL
The top bar functions as a clickable link. The URL entered here will serve as the link target to any user who clicks on the top bar. As with the Top Bar Text above, the value entered here will supersede the input from the Theme Settings page.
Disable Public Annotations and Comments
When this local setting is toggled on, users will not be able to pin public annotations to any text that is a part of this specific project. This does not prevent users from annotating texts in this project entirely. Users will be able to leave annotations in the context of a reading group of which they are a member—and viewable to other members of that group—or as a private annotation, viewable only to the user themself.
Because of that, someone who doesn’t have an account, or someone who is logged in as a Reader, won’t see annotations on any text in the project so long as this toggle is engaged. The exception would be Readers who are members of reading groups: they will be able to see annotations that have been left in the context of those reading groups.
While this setting is engaged, it will not possible to convert a private annotation into a public one, and public reading groups will function as if they were private ones.
To learn how to disable public annotations globally across an entire Manifold instance, instead of locally for specific projects, see the General Settings section.
Likewise, that section describes how to further limit the annotation functionality by disabling reading groups across an entire instance. When publishers disable both public annotation and reading groups globally, users will only be able to leave private annotations they alone can see.