Ahh CSS filters is exactly what i meant, i forgot the word.
The icon pack is just a general icon pack for quick usage that designers can choose from, for example, you need a keyboard icon, you click on the Icons tab, search for keyboard and you find a couple different keyboard icons that you can then also color.
What I mean by a more robust selector system based on relationships is being able to do things like this. Letās say Iām making a card module and inside I want to style an image, heading and paragraph text:
You could easily make other card classes that style the elements inside in different manners without making a ton of classes for each element. Iām not saying this is this is the only way to do something like this, but I find that itās easier to iterate on different ideas and styles and keep the code smaller and cleaner.
For pseudo selectors, I mean stuff like ::before, ::after, and :nth-child and :nth-of-type. These are probably more advanced selectors to work with so not everyone would use it but itād be nice to have it baked into Webflow natively without custom code.
Good list⦠Iād add something basic like the ability to disable the Edge Lines. Make it so the name just shows when itās highlighted. So it would be Hide/Show/Disable Edge Lines.
Cool how it goes away when you are adjusting a color. Would just like the ability to disable it, if need be.
Perhaps youāre talking about something that Iām missing, but isnāt the relationship selectors feature you want the same as the nested element classes you can achieve with the rich text blocks?
For example, you pull in a rich text block and assign it the class ācard.ā Then your paragraphs, images, and headers within that .card rich text block can all be styled in a way that does not affect other paragraphs, images, and headers outside of it.
@ctotty Yes, thatās the same concept Iām talking about and your suggestion is certainly another way of doing that. For my simple ācardā example above, this would work because it only uses parent > child relationship but there are many others that wouldnāt work with the rich-text block (i.e. adjacent sibling selector).
Anyone with a portfolio site likely has upcoming appearances: speaking, performing, conferences, trade shows, etc. and itād be great to list them and show upcoming events (as I have in the preview site).
Photo Grids / Gallery
Beyond just a scroll, itād be great to be able to display grids of photos by tag, so if we tag a photo it automatically appears. For example, Iād like to have a grid of photos under each page (āComedyā, āStandupā, āStartupā, etc.)
Dynamic Content Templates (like for above: event calendars, galleries, etc.)
If you let people share (and even resell) dynamic content templates (rather than just clone entire sites), people can develop these templates, making it easier for everyone. For example, Iād love to make a template all event producers can use to share a showcase calendar (multiple performers per show). Great for conferences, performances, etc.
This isnāt a feature, but charging extra to run a blog is stupid when Medium is free and embeddable. Plus, itās almost the same code, just multiple pages under the headline of āblogā. Wix doesnāt charge extra. I know itās a good way to pull another $5-10/mo, but itās likely pushing away many of the people who will share your tech the most.
Itād be great to get an incentive to pull sites from WIX, etc., and to have some app that would convert the sites into Webflow code.
The blogging interface can use an advanced option (data tables, charts, photo grids, etc.). Itās pretty good, but should be as good as Tumblr and default Wordpress.
Give us build-in charts & grids and UI elements (and allow us to choose & edit colors/style). Many of us are making / mocking up dashboards.
7b. FontAwesome and the like should be standard (for icons). Really, all GoogleFonts should be, too (ok to include this with paid).
Give us a toggle to stop Google/etc from spidering specific pages. Bonus if you can password-protect pages / folders. This way we can share info, but not have random folks finding it.
Do a refer-a-friend thing where we get a free month if a friend signs up. Also a tag at the bottom of the page where if people copy our template, etc. we get a bonus, rev share, etc.
Enable us to duplicate a Slide (or any element), but change the name, so we can copy slides with images/etc and then edit with a new name. Ideally we can just select text & images into a table/csv/xml/etc, so we donāt have to manually do this. (If this is already possible itās not clear.)
Enable us to record actions (like in Adobe), so we can repeat the same complex set of steps with one button press.
Make the a āpaste without formattingā toggle DEFAULT, so we donāt have to clear it after, or paste into the URL field, notepad/atom, etc.
Give us the ability to revert to previous versions ala Wikipedia or Wordpress. This is popular for a reason ā we/the system will fuckup and sometimes itās just faster to take a step back.
To help increase page speed: Automatically resize images (the actual file size) down to the maximum possible dimensions for that view (mobile, tablet, and also smaller desktops) Because we have retina-size screens we have to have large images, but itās a HUGE pain to manually swap the image ID for each view to a smaller size. Images should be smarter and call a smaller file to speed the image.
What about a community driven GFX library where community members could upload things like icon packs, colour palettes and other various ātemplatesā
I like how things like NuGet allows the community enhance the product