Feature requests collection

[kolbykruger]

Hi Prismic team,

I want to start off my saying that I am in love with your CMS, and have been enjoying my time working with it thoroughly.

I compiled a list of feedback & features that I think could be really impactful. I'm unsure if you want these broken out into separate features, as it didn't specify in the feature requests spec, so I will include them all in one thread. I believe I have removed the requests that would be duplicates of other posts (anchor links, media folders, etc).

Fields

Images

A range slider could be really nice for image cropping. This would provide much needed accessibility for users who have difficulty using a mouse-wheel. I know I've had trouble in the past when I previously used a mouse that had a notched scroll-wheel, preventing me from getting a precise crop.

Multi-select

The current recommended method of achieving this is to ether use the document tags (which only would work for a single multi-select field) or create a group field, with a select box in it.

My main issues with the second method is that the document tree becomes quite large and lengthy (especially when selecting 2+), and it dominates the view. It would be ideal to have a single field that operates in this capacity. If a field could be created similar to the document tags (without the full functionality of document tags) that would be ideal.

Improved writing experience

One of my wishes for Prismic is to offer a better "writing experience" for users. Right now, using the Rich Text field to write an entire post has a few pain-points:

• Visual clarity
  • font size is really small, especially for lengthy documents
  • hard to distinguish a rich-text field from other fields
  • toolbar is far away from field in most cases - especially on large screens
• Formatting options that are missing from the normal
  • horizontal line/rule
  • links - anchor links for documents is a high use-case
  • image options - adding an option similar to labels for images to allow for alignment/floats/custom classes
  • underline
  • strikethrough
  • code
  • superscript + subscript
• Utilities
  • Word counter
  • Full-screen editing?

I've found that most of my users prefer to write their posts outside of Prismic, and then copy and paste them in. With versioning built in, it's preferable that they write their posts within Prismic.

Slices

The possibility to collapse the content within a slice - especially useful for really long documents.

Custom Types

Disable the preview button based on the custom type. Some custom types / repeatable types don't necessarily become pages, but rather options for "content relationships" for other documents. A good example of this is an author custom type, where you can have many authors that are then attached to a post to create dynamic content. However, the authors may not have their own specific page.

Documents

Ability to re-order created tabs. If you create them in the incorrect order, or want to add one later that is more important than the rest, it would be nice have the ability to re-order them.

Bookmarking / saving filters

Ability to bookmark certain collection types, and potentially add a button on the left-hand side to easily navigate to that filter. In my case, I would love to have some preset filters to sort the content.

• For example, I have posts as a repeating type. I would like the ability to save a filter with the collection type of post and order them by publish .
• For example, I have projects as a repeating type. I would like the ability to save a filter with the collection type of projects and order them by alphabetical .

This would provide a really nice way to navigate between collection types without the hassle of filtering, un-filtering every time.

Support

• Ability to disable the documentation button in the navigation (question mark icon). Most of our clients do not need access to the documentation.
• Ability to disable the intercom button (bottom right). When allowing clients access, we prefer they contact us (the developers) rather than you for questions about their website. This can be confusing for clients.

I'm happy to dive deeper on these if you would like. If you would like them split out into separate posts, I can definitely remove this one and create individual posts over the next couple of weeks (as not to spam).

Thank you very much for what you all do!

[Phil (Phil Snow)]

Hey Kolby,

I'm glad to see you're enjoying Prismic. Yeah this is a long one haha it took me a while to put this response together but here we go. I'll try and address each point as best I can. In the future we encourage you to create separate threads as we can have full conversations about each point that way.

Images (Range Slider):

I totally agree with this one, it's an edge case I never thought of. I've passed this to the features team.

Multi-select:

I'm not totally clear on your use case here, can you explain a little further?

Rich text editor:

We have plans in the future to do a full overhaul of the rich text editor, so we won't be implementing any features in the current iteration, but I'll address each point anyway.

font size is really small, especially for lengthy documents

The font-size is a pretty standard 14px, it's possible to increase the font-size in the browser by zooming if it's hard to see. We could enable an option to make the font-size larger in the repo, but this might give the impression to content writers that this would be reflected in the front-end and this could cause confusion.

hard to distinguish a rich-text field from other fields

That's interesting, it's true until you click on the field it's not clear it's a rich text, maybe placeholders can be used to make this clearer. Do you have any suggestions on how we could make this more distinct?

toolbar is far away from field in most cases - especially on large screens

I'm not sure what you mean by this one can you share a screenshot to explain?

Formatting options that are missing from the normal
We have documented in a another thread how to add additional styling options to the rich text field.

More Rich Text Formatting Options?

Hi @rrkuepper, sorry that I wasn't clear. You have the ability to use subscript, superscript, strikethrough, or any other custom styling option using Rich Text labels. Here is an article that explains how to do this:

image options - adding an option similar to labels for images to allow for alignment/floats/custom classes
This is not something that we plan to implement, we plan to properly deprecate labels for images as we prefer that people use slices to build options to use and align images because of the complexities that arise with images within text fields.

Word counter

I like this idea, I think this could be really useful I've added a tick to our feature request tracker for this.

Full-screen editing

Can you elaborate on this further?

The possibility to collapse the content within a slice - especially useful for really long documents.

Cool idea, I've passed it on.

Custom Types

Disable the preview button based on the custom type.

If we were to implement this then this would cause release previews to break if you created a new author and a new document linked to this author. You wouldn't be able to preview this unpublished document.

Documents

We've addressed the ordering question here before:

Sorting documents?

Have you read this help page on ordering results from the API?

Bookmarking / saving filters

We do have the collections feature, were you can apply features on types. Although your extra filter options are interesting but they fall under the sorting conversation again I think.

Create Collections of Documents

Support

Ability to disable the documentation button in the navigation

This is not something that we plan to do as our documentation also includes user guides for content creation. We are planning a documentation overhaul though which might make this divide clearer.

Ability to disable the intercom button (bottom right). When allowing clients access, we prefer they contact us (the developers) rather than you for questions about their website. This can be confusing for clients.

I agree on this one I think we could make this clearer what that contact button is for. I'm not sure how we could do that though hopefully the design team will have some ideas.

Hopefully this answers some of your questions and we can talk more at length about anything or any of our decisions, but yeah maybe we'll have to break this thread up a bit.

Thanks.

[kolbykruger]

Hi Phil,

Thank you very much for taking the time to respond, I know there was a lot there. I think pretty much everything you said makes a lot of sense, and made me realize edge cases that I didn’t think about for a few of the requests.

There’s a few that you asked for more context on, so I will provide that below:

Multi-select

I’ll provide you with an example: I have a construction company for a client, and they enter their projects in. Each project can have quite a few different options, for instance:

• Category (Heathcare, Commercial, Residential)
• Type (Renovation, Addition, New Construction, Redevelopment)
• Architect (A list of architects they work with)

Each one of these listed above can have multiple options selected. So for a sample project, it can be:

• Category: Healthcare, Commercial
• Type: Renovation, Redevelopment

There isn’t really a great way to model this in Prismic, as you can have a field where you ask them to type it in, however that leads to mistakes, typos, and causes problems with potential filters moving forward. You can have it as a group with a single select box, but this takes up a lot of room in the document, and can be confusing for users to enter the information.

Ideally this would work similar to a select box, where they can select multiple options, or even offer a checkbox field, so they can select multiple out of the given options.

Rich-text Editor

I’ll start with the fact that I am really excited about the rework to the rich text editor!

toolbar is far away from field in most cases - especially on large screens
I’ve attached a screenshot to show you what I mean. The toolbar for the rich-text is at the top of the page, and the rich-text field I am working in is at the bottom. There’s no context to tell you that they’re associated, and no real indication upon focusing in that field that the toolbar options are available.

I’m honestly not sure how to fix this one, but because the toolbar is far away from the field, and the change when clicking into the field is minimal, you may miss the fact that you have formatting options.

Thank you for taking the time to respond to my suggestions, I appreciate it. Like I said previously, I am having a great time working with Prismic, you all make it really easy to content model, and most importantly it’s actually really fun to work with in the development setting.

Thanks again!

[Phil (Phil Snow)]

Hey again Kolby,

Sorry about the delayed reply, both your examples are much clearer and I really agree for the multi-select. I think it could be really useful and have added another tick to the feature request tracker for that. We have also previously discussed it here:

MultiSelect Dropdown in prismic

Hi @saddagatla-contracto, as you’ve seen Prismic doesn’t currently have a Multi-select field. The way you can model this is by putting your Select field inside of a Group field. This will allow a content author to select as many of the options as they need. I will pass this along to the @features-team to add to our feature request tracker as a possible improvement for the future.

For the rich text, I see what you mean now though I don't think the product team will change this in the near future as like I said they are looking at an overhaul. I've passed it to them anyway so they can see what issue people are having.

Thanks you for your genuinely constructive feedback, it really helps us understand the user experience and build a better product.

Cheers.

[pablo (Pablo Giralt)]

+1 to all this feature requests, specially to multi-select and ability to collapse slice content. About the collapse feature, it would be cool to be able to select the field which is visible when the slice has been collapsed (the Flexible Field in Wordpress Advanced Custom fields has this and it is pretty useful)