I do as little coding as possible because I don’t build sites for a living. My solution must have a WYSIWYG interface. I have several sites, so any solution that charges by the site and month won’t work for me.
The newest version of RapidWeaver does a great job with responsive web design on a range of devices, automatically serving up images scaled to those devices without me having to create all those image sizes for each one, like other web-building apps require.
I strongly considered Wordpress but the learning curve was just too steep to get the look & feel I wanted in a reasonable amount of time. But the Stacks on which Rapidweaver sites are built remind me a lot of the new Wordpress Gutenberg systems of blocks. Wordpress is the world’s #1 site builder & has a huge following so it should last a long time. But the Wordpress ecosystem is a notorious hacker target since it’s so big.
#Tvn hu imagesize lsn mac
My RapidWeaver sites are built on my Mac and hosted by my webhost. Stacks are the essential building blocks, which you can get from Next you’ll need a robust framework of components. The two top candidates are Foundry & Foundation by started with Foundry but then went to Foundation once I discovered they play well with Hoefler web fonts, which I’ve used for years. weavers.space has a bunch of other great stacks built on Foundation, and a robust user community.
#Tvn hu imagesize lsn pro
I initially bought Font Pro with the intention of using it with Foundry, but couldn’t get my web fonts working so decided to get Foundation to replace Foundry hoping they would play nice together, both being part of the weavers.space ecosystem. I struggled for a couple more days getting my web fonts to work. Finally, I asked myself whether it might be because I hadn’t published the site yet. To that point, I’d just been building the basics on my Mac. Nothing happened at first. But then I noticed this at the bottom of the Hoefler Font Family Setup box: “In order to preview your fonts, you must add "127.0.0.1” to your domain list in Hoefler (RW7 only)“. I’m on RW8.7 but thought I’d give it a try. It worked! Not sure which fixed it, as I did one right after the other and it might have taken a minute for the publishing to trigger something in my Hoefler account, but I don’t really care since it’s working now. Weavers.space developer has lots of tutorial videos which are really helpful but it took me awhile to realize he’s developing stuff so fast that many of the videos are from previous versions. For example, he talks a lot about swatches but I couldn’t find anything that said "swatch” in Site Styles, which is the nerve center of Foundation. That’s because since the video was posted, swatches have matured into Font & Text, General, and Component swatches.
Once I realized that, things got much easier. I have Font & Text swatches for my text style, link style, and heading styles from h1 to h6. I have General swatches for background colors and for margins. You can use swatches as a “class,” which you can apply to almost any stack on a page by tagging it with the class name. You can also apply swatches to a long list of stack types. I have two Component swatches: Top Bar Styles & Menu Styles.ĭoing this means you don’t need to tag them with the class, but it affects all such objects on the page. Speaking of Top Bar & Menus, I’m rebuilding all my sites with a black background (more on that later).
Some devices are small enough that the menu wraps to more than one line, and the leftover space was a light grey, which looks bad. I worked for a couple days trying dozens of options before figuring out a hack.
0 kommentar(er)
