I’m interested in working on the "GUI for Plone Import/Export"" project. I have a few questions regarding the UI design:
Should the UI be based on the which provided in issue , or would it be advisable to redesign it for a better user experience?
Who will be the mentor for this project? This information isn't mentioned in the project details.
I believe using React and Python will make the implementation easier, although I anticipate that most of the time will go into testing. I plan to implement the project in small, incremental changes to ensure thorough testing at each stage. However, the main challenge right now is the UI design.
It could be volto only. In which case it would be react
personally I think this is a reasonable tradeoff.
It could be supporting only the existing json format and file structure.
In which case you would have to ask if there is much value in there being a GUI because the json formats main usecase is to export from an old site Plone site and import into a new plone site. And a developer capable of making a new Plone site is probably capable of using the current procedure to do an import.
Other people might have other opinions on the goal, but the mockups were made with the following goals in mind
a non technical admin can
export some content and metadata, make bulk modifications to it and reimport it to have it updated.
get some images, files and content from elsewhere and bulk upload this new content
export metadata on current content to do things like reporting and analytics
This is why the idea was to use CSV and normal files inside a zip (or directory), rather than json.
Of course in addition to this supporting the above goals, supporting GUI export of json and then import of JSON to a new site would be a plus but I don't see it as a primary goal.
One thing that might not be evident about all this is that a big technical problem to overcome is having an api for plone that allows efficient streaming for upload and download to handle large imports or exports. This means either breaking it up into different transactions and losing the ability to undo, or somehow handling memory well and informing the user the site might perform badly.
so basically it will take time , can you provide me documents and resources so I can research more and understand how I can achieve goal. this project is more interesting than I thought .