Feature Ideas

Filter

  1. Locked/internal/private workspaces

    Nobody can see the pages without being specifically invited. We'll likely do something similar to Notion, with "private" and "published" folders in the sidebar.

    Artyom Kazak

    12

  2. Password-protected pages

    Everyone voting for this idea: please describe your usecases.

    Artyom Kazak

    19

  3. Drag and drop blocks

    We already have drag and drop for images & tables, but nothing else. This card is about Notion-style drag and drop. Note: this will only be implemented when the CKEditor team gets to it. See this issue.

    Artyom Kazak

    3

  4. Customizable page headers/footers

    Artyom Kazak

    8

  5. Full-text search: for page visitors

    This is an issue for adding an option to let your sites' readers search the site. It's separate from https://brick.frill.co/roadmap/full-text-search-for-page-editors.

    Artyom Kazak

    3

  6. User Roles

    Need a more robust user roles defined for the system. Suggested as below: Super Admin/Account Holder: can do everything inside the account, create users with specific roles, edit/delete, coding, styling, create pages and accept pages creation, etc... Collaborators/Managers: can create pages, and accept pages creation, create lower-level roles such as editors NEED A BRICK ACCOUNT ALLOCATED FROM THE SUPER ADMIN LICENSES. Editors/Authors: can create pages but need acceptance from higher roles, can edit pages and delete NEED A FREE BRICK ACCOUNT Contributors: can edit pages but DO NOT NEED AN ACCOUNT BUT MUST DO THIS ONLY WITH THE PASSWORD PROTECTED PAGES! Readers/Viewers/Guests: viewing only

    Quang M
    #Improvement πŸ‘

    1

  7. Custom favicons

    Currently we can't set favicons via "Manage page head".

    Artyom Kazak
    #Deal Breaker πŸ’”

    15

  8. Linking to Sections of Pages (anchors)

    Useful for looooonnggg pages and to have a Table of Contents within the page.

    Lou

    1

  9. Autogenerated table of contents / page outline

    Table of contents from our h1 h2 h3 etc with the TOC on a sidebar!

    Chris
    #Improvement πŸ‘

    7

  10. Backups to external cloud

    We have email-based backups for content, but they don't support accounts with more than 25 MB worth of images/content. Also, getting an email every week might be annoying. Note: when upvoting this idea, please also specify which platform you'd like to get backups to (Google Drive, OneDrive, Dropbox, etc).

    Artyom Kazak

    8

  11. A "duplicate page" button

    Two possibilities: a) either it should clone the whole subtree, or b) only one page. When voting, please specify whether you need (a) or (b) or both.

    Artyom Kazak

    7

  12. Built-in email newsletters

    Please upvote if you personally would use Brick to post email newsletters. Also, describe the minimum functionality you need for newsletters.

    Artyom Kazak

    4

  13. Collaboration without a Brick account

    One usecase I've heard is using Brick for teaching β€”Β Google Drive/Docs is a PITA apparently. Please post more usecases.

    Artyom Kazak

    5

  14. No-Code Theme Customization

    Customize colors, fonts, element sizes, etc. without using code

    Lou
    #Improvement πŸ‘#Styling 🎨

    1

  15. Public API

    I heard the following usecases: With a simple API for retrieving & creating pages, Brick could be used as a headless CMS With ??? API, Brick could be somehow used in conjunction with Shopify, although I didn't understand how I have never used headless CMS and never built anything with CMS API (e.g. I know Notion has an API nowadays but I don't know what it's used for). When upvoting, please provide examples of things that you could build with an API, and what's the minimum API necessary to build them.

    Artyom Kazak

    9