You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose a system where a user could provide a custom template & styling via HTML & CSS, with variables such as {{downloads}}, {{favicon}}, {{name}}, etc. By default, a preset would be automatically selected, but this option is there for those who wish to customise. The data could be stored via a user system, where banners and their meta data are linked to a specific user, and therefore could be changed at a later date without the image url changing. Alternatively, banners could be anonymous with the meta data is stored exclusively with the banner, and not linked to anything else - effectively immutable.
Thanks for your suggestion. We have a user system planned, but we haven't quite gotten to that point yet. This system is still fairly alpha. We'll consider the templating suggestion, but I worry that allowing full HTML & CSS would create a number of attack vectors. It'd have to be a heavy subset, or alternatively Markdown or something with styling controlled in some other way.
I agree that the URL changing with every customization option is gross -- this will be changed once we implement our user account system.
I propose a system where a user could provide a custom template & styling via HTML & CSS, with variables such as
{{downloads}}
,{{favicon}}
,{{name}}
, etc. By default, a preset would be automatically selected, but this option is there for those who wish to customise. The data could be stored via a user system, where banners and their meta data are linked to a specific user, and therefore could be changed at a later date without the image url changing. Alternatively, banners could be anonymous with the meta data is stored exclusively with the banner, and not linked to anything else - effectively immutable.https://github.com/radkovo/WebVector
The text was updated successfully, but these errors were encountered: