Open Mement0o opened 4 years ago
Thanks for pointing this out !
The mass edit function seems to be a too small place to edit datas such as custom-head
.
In fact custom head is a strange case, it's between CONTENT and METADATAS (as in the W logic). As it's displayed in the edit page, this should be a METADATA and should be editable using the mass edit function as every others metadatas.
But, as I said, it does not look like the right place to me, but maybe i'm wrong. Or maybe the mass edit function should have it's own, larger page, to be more confortable... that's another question.
A default custom-head
settable in the admin panel looks very easy and make sense directly to me.
I think that's what I will code first.
But yea, mass editing is another kind of command, and this will remain an issue not allowing user to mass edit custom-head
Okay, this is made me think of deeper design problems.
there are two possibilities :
custom-head
when you create a pageglobal-head
, that is always editable and always present, just like global-css
is.I think the second option is more interesting.
The first one is finally part of a bigger problem : the default page template. for me the best solution would be :
select default page in the page database, every page will be created using this datas.
Even better would be : a default page template settable for each user separately.
But this is another issue... #75
Where should be stored this global-head
?
Actually, clobal-css
is stored only as a .css
file in /assets/global/
. Maybe this is not a good idea, if an user want to move all is website, he or she have a lot of risk to forget this file.
So the global.css
& global-head
should be into the config.json
file ?
What do you think @n-peugnet ????
It would be cooool to give a custom head for all the new pages created like in the page creation options in the admin section. And also in the mass edit function.