Feature request ideas

It would be great if Super could support the display of Notion Buttons (https://www.notion.so/help/notion-academy/lesson/buttons) to make it easier to include CTA buttons on our pages that are styled consistently on Super, without having to apply custom CSS code that may or may not be supported in future Super releases. Currently, we use strong linked text with a bg colour in Notion to indicate we want to display a button on the Super page, and then include custom CSS code in Super site >> Code >> CSS to set with which bg color and txt color we want to display the button. The issue is that this requires a lot of custom code (from here: https://superhq.notion.site/Button-code-2bdd831102cd4021ac523bddfddca98b) Ideally, I could include a Notion button (by typing /button in Notion and using their features to add a link). If I want to change the bg color or text of that button across my site, then ideally, i could simply change the button bg color in Notion (to any of the Notion colors)....and Super would display a styled version of that notion CTA button, applying the override colours I have set in Super>>design>>colours>>notion and would style the CTA button radius, padding, any shadow etc as set in Super>>design>>Layout... This way, we: don't have to include reams of custom CSS to be able to display CTA buttons in various colors, to convey their intention - positive, negative, informative etc) avoid including custom CSS that may not be supported in any future release... and if we want to display strong, linked text in notion copy as strong, linked text on our super site, we can.

It would be great if you could offer to have a great experience for someone like me who offers a web page to users in different countries. I have translations of my pages in notion, but it’s currently not a great user experience to expose these to users. Some of my pages are translated, some of them are not (so there’s a fallback to English).

Notion does not have forms and so we use a third party tool like notionforms or chilipepper to have forms on our notion pages that go straight to the notion databases... but it would be awesome if we could have forms in super instead of in a third party tool.

It would be great for users to be able to select multiple filters on databases, rather than simply selecting from pre-built views, and also for them to be able to sort database items by any field.

The ability to customize the 404 page on your Super site.

I am aware of the third tool option, with MemberSpace in my case. I tried it but I found it a little bit technical. I think it would be a very nice improvement to add a membership feature as simple to apply as the password protection.

In case your database has more than 100 items, the ability to have a load more button to show the others items of the database (ie, from 101 to 200 and so on). Thanks

We need a button, not a colored background that interacts when you click

It would be great if, among the other typography options we already have, we could adjust the line spacing (the space between each line of text, regardless of font size) and paragraph spacing (the gap between each paragraph) to enhance readability on any font we choose. Helpful for any website with a lot of writing, including blogs and creative people who write stories. Unfortunately, with many fonts in Super, I feel like the lines of text are spaced too closely to each other, as well as the paragraph breaks which make it harder to distinguish each paragraph. Few fonts, such as Crimson Text, are exceptions but do not provide the feel for my website that I want.

I would like to use the search function on my site, but right now the function unfortunately also shows up pages as search results that either I do not want users to actually browse (like the CMS database page, which I did not add to Super, but the search still shows it) or that are irrelevant for the search. It would be neat to have a "Exclude page from search" checkbox available in the page settings to make that work. On the personal tier, you could at least exclude obviously irrelevant pages from the search this way. When on the pro tier, I could then add the CMS database page to Super and redirect or 404 it, plus exclude it from the search function.

One-button duplication of an existing site (that you own), for the purposes of e.g. creating a development version of the site while making major changes to structure/design/content while the 'master site' remains live, to get around the lack of sandbox functionality. Can be achieved at the moment by duplicating the site in Notion and copying across CSS / themes etc, but can be time-consuming if there is a lot of page-specific CSS or code, and/or changes have been made to Super navigation compared to the original structure in Notion.

I have a page with multiple sections and I frequently want to give people a link to a particular section. For example, here is the page: https://joshua.herzig-marx.com/pm-resources And I'd like to send people a link just to, say the Courses section, e.g., https://joshua.herzig-marx.com/pm-resources#courses-0423 In this particular implementation, the Anchor is created from a lower case version of the header text, each word separated by a dash, with a random four-digit number appended ensure disambiguation if multiple headings have the same text. I don't see either an automatic or manual way to do this today. Please see https://www.w3docs.com/snippets/html/how-to-create-an-anchor-link-to-jump-to-a-specific-part-of-a-page.html#creating-an-anchor-link-2 for context. Option for automatically adding the page section ID to the URL as users scroll through the site User friendly method of capturing page section anchor by block ID

For this like Notion's top page icons, it would be nice if we could adjust the size or these or hide them all together easily. We can do this in CSS now, so I imagine it would be possible to put an easy interface addition for each page to adjust these.

Currently, secondary database views are not linkable, meaning that users can't be sent directly to a specific language view or other subset of a database. The current process is to send them to the main database page with instructions on how to view the relevant tab, which is poor UX.