Some feature requests

[rallisf1]

Is your feature request related to a problem? Please describe.

1. You cannot exit the program if you have unsaved changes, which is good, but there is no prompt about it and people have to guess to save first.
2. Adding a component from Primo Library needs an unnecessary extra step: first add to Site Library and then add that to the Page
3. You cannot edit the code of content block, you have to go to Components > Create to create a custom component
4. Drag'n'drop on images is not working and I doubt this is a Windows only bug
5. Ability to export/import custom components

Describe the solution you'd like

1. Any kind of prompt/alert/warning would be ok
2. Merging the 2 libraries would be wrong as you need to customize your local component copies, but that extra step is confusing. Better have the action for Primo Library components changed to Add to Page which would also add it to the Site Library.
3. Make it so the content block is a custom component by default and give it a random name like block_34gjh2g43 in the Site Library
4. Enable drag'n'drop for images, check here
5. Plain json just like how sites are saved in %AppData%\Roaming\primo\sites is ok

[mateomorris]

Thanks for this @rallisf1! I'm gonna convert this into a discussion and break out the individual items into separate issues

[mateomorris]

You cannot edit the code of content block, you have to go to Components > Create to create a custom component

What are you hoping to be able to do with the content block? Edit its HTML/CSS/JS like you would a regular component, or just style it? Styling can be done from the page/site CSS by targeting .primo-content, and specific sections by inspecting the page to get their ID and using .primo-section#section-id. I think the content would be editable as HTML, but I haven't how that would work with TipTap if the user modifies the content into HTML.

[rallisf1]

Sure, but that's not intuitive at all. People expect to add/edit columns by clicking on a button when they are using a website builder.

[mateomorris]

I'm curious if you're passing the site off to a content editor who you'd like to have the ability to change the design without modifying the CSS? Or would you just like an easier way of building layout?

[rallisf1]

Little bit of both. Don't get me wrong this is an amazing tool so far and it gets better by the day, but there are tons of site builders out there that have had features like this for years. Myself I am a developer and have been using svelte for a couple years. Primo seems godsent allowing me to quickly develop layouts and collaborate with non-coders. Exactly because non-coders will use Primo it's a shame to have them disappointed because they need to code (or bug me in my case) for such basic functions.

[mateomorris]

We're moving in the direction of enabling content editors to make design decisions like that, but at the discretion of the developer. So compared to traditional site builders which try to enable every design option (e.g. color and font pickers) with the goal of replacing developers, we're focusing on giving developers the ability to decide which design options will be available to content editors.

So in this case, we wouldn't specifically implement a column selector which applies specific CSS, but the ability for the site developer to add that functionality themselves by creating fields on the Content Block and modifying the Content Block's code to apply different HTML/CSS (here just columns: 2) based on those fields.

This is mostly possible now by creating a Page Field (e.g. Two Columns - two_columns), accessing that value in the Page head HTML and setting a CSS variable with it (e.g. <style>--content-columns: {two_columns ? '2' : '1'}</style>), then setting the CSS variable from the Page CSS (e.g. .primo-content p { columns: var(--content-columns)}. That's obviously a bit tedious and not specific to each Content Block, so the former solution would be ideal. But for now we're focusing on more pressing things.

[rallisf1]

As I already said #130 your position on this is fair and my proposal is to have Primo extendable by plugins so that me or whoever else can implement his own code-free functionality.

[mateomorris]

Ability to export/import custom components

Good idea. I was going to say you could Copy/Paste them between sites, but I just realized that feature's broken since Electron has its own Clipboard API. So instead of managing two copy/paste APIs between desktop & server, I took your advice and implemented upload/download functionality with each component being a JSON file. It adds a little more friction compared to copying + pasting, but I think people are going to find it more intuitive.

[carstenjaksch]

I'd like to hop in for that point:

You cannot exit the program if you have unsaved changes, which is good, but there is no prompt about it and people have to guess to save first.

Such a prompt displays after clicking on Back to Dashboard, but I think it should be possible to discard changes – like a component (see screenshots).

My proposal: Use the same prompt from the component for quitting the program and exiting to the dashboard.
Bonus: Add a button to save changes directly from the prompt.

Screenshots

Try to exit site with unsaved changes:

Try to exit component editor with unsaved changes:

[togelian]

I would like to just have site fields that I could tap into in any component. Nested components could be a solution, such that you change the static field on a component, that is part of other components, the other components update too.