[tracker] Bolt 4.0 Wireframes - File Management page

[sbonardt]

The Bolt 4.0 File Management page Wireframe(s)

Starting point will be what's set up as wireframe for the File Management page from Bolt 3.x.

For now:

• What improvements can be made?
• Are there items/functionalities missing or useful to add?
• ...

File management - 01 small screens

File management - 02 large screens

[sbonardt]

#7401

[rossriley]

Things I can think of from common feedback/feature requests.

1. No ability to rename files, an OS like double click to inline edit would be good.
2. Organising the Filesystems, Bolt has one filesystem for uploads, one for a theme, another for config... maybe rebranding these as 'Spaces' or something similar as a top-level nav that would allow users to switch.
3. Maybe think about the 'Stack' it does seem to confuse people although it's a useful feature sometimes, perhaps some UI sugar could help or perhaps a new name or just some inline help on the files page to explain.

[Boorj]

problem

4. no ability to select several files and process them.

suggestion:

Probably we could find a library for file management? Like

• Jquery FancyTree http://wwwendt.de/tech/fancytree/demo/index.html#sample-3rd-jQuery-contextMenu.html

• Vue component: vue-file-tree

• ckfinder .

  

• https://filebrowserapp.herokuapp.com/

  

• webix

We can make a research, and find the best lib to use.

---

2. maybe rebranding these as

I agree with the fact, that it's hard to understand to non-devs, that these folders are just "mounted" folders with some specific names. For example, sign files:// makes people think: and what's inside other folders?

So some rebranding could help. Some ideas for name that could be used (beside Space): area, zone, cloud, directory, storage, pool, box, pocket, bag,

3. Maybe think about the 'Stack' it does seem to confuse people ... or perhaps a new name or just some inline help on the files page to explain

I agree with @rossriley . Stack is a quite unexplained feature. My clients don't use at all. Renaming and/or cool hints system could help

[jadwigo]

The stack could be renamed to "Your most recent files"

[sbonardt]

@rossriley

1. Renaming seems a good idea! But how will this work when renaming already linked files in for instance saved content type items text fields/file fields? Seems tricky...
2. Don't know about this. Seems like a bit step. Something for @bobdenotter I think
3. Definitely some UI sugar and more explanation. And another name would help 👍

[Boorj]

Guys, for ready-to-use file browser google for 'javascript file tree' (browser, manager etc - works worse)

Fancy tree

https://github.com/mar10/fancytree/ is my personal favourite:

Could be used on other pages to select

http://wwwendt.de/tech/fancytree/demo/#sample-api.html

halower/vue-tree

this one is for Vue.JS

angular-filemanager

resume

I understand, that we'll probably have to rewrite everything from scratch, relying on frontend framework. But these are examples that we can take for design.

[Boorj]

5. add panel at right

see the image below

6.a. add ability to process several files,

Probably that could depend on extension, like "resize" for jpegs/png. For example

• "optimize jpg size".
• "resize"
• convert to database values (for csv / excel / xml / json) dropped by users.

6.b. probably add ability to delegate processing to plugins

And we can add ability to add plugins processors for files. For example: we make registry, which will contain:

file_processors:
   jpg: MyPlugin/Processors/Imagewatermarker::process()
   png: MyPlugin/Processors/Imagewatermarker::process()

7. add ability to multi-rename files

obvious one

[SvanteRichter]

Isn't this some serious feature creep? Sure the ability for extensions to do stuff is nice, but does bolt core really need to batch move/rename /extract files?

[Boorj]

I agree. Probably yes.

[romulo1984]

I suffered somewhat from the way Bolt manages images, and even extended the application to make images look more robust.

It may be interesting for each image to represent a record, making it indexable, allowing developers to extend and create multiple image crops, audit features, copyrights, and features that professional content publishers need.

Below are some screens of my implementation in production:

Button that opens the gallery

Overview

Filters

New image with crop and additional info

Latest images widget (does not work as a stack, but could)

WYSIWYG Editor

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. Maybe this issue has been fixed in a recent release, or perhaps it is not affecting a lot of people? It will be closed if no further activity occurs, because we like to keep the issue queue concise and actual. If you think this issue is still relevant, please let us know. Especially if you’d like to help resolve the issue, either by helping us pinpointing the cause of a bug, or in implementing a fix or new feature.

[romulo1984]

Is this really meant to be closed?

[sbonardt]

Hi @romulo1984, no I dont think so. But we do need to get back on track with these wireframes and the dev on V4. Currently, a lot of work is done on the backend, by various people. I dont have the overview what the status is. I hope @bobdenotter can add to this soon.

Your suggestion and work looks really nice and sounds like a good idea! Hope this approach of images being more like a record is something that fits with v4 as well. It would indeed make it more robust and extendable. I'll reopen this one, but maybe your suggestion deserves its own feature.

[JarJak]

I like this thread and would love to see it in Bolt 4 - PRs are welcome!