In addition to importing images from your Photos library or other resources, users can now simply select the service from sources, type in a search query, then drag the desired content into your project. This functionality also extends to individual blog posts by modifying the Social Tags section for each entry.Īlthough unfamiliar with royalty-free stock photo service Unsplash prior to upgrading, the new integration in RW8 has made me a fan. By checking Generate Social Tags under Settings > General in the sidebar, web designers can now make sure proper meta tags are written for both Twitter cards as well as Open Graph. RapidWeaver 8 offers five new built-in themes, bringing the total number to 61. This is a solid step in the right direction and welcome addition to be sure, but I’d love to have the ability to save window states on a project by project basis, rather than as a single universal setting. This feature works across all open windows, so your preferred layout applies to every future project (that is, until you change it again). The simulator isn’t the only area of the application where you can restore the previous window state. The new device simulator mode updates in real-time as changes are made, but it’s still now quite a replacement for true WYSIWYG editing. You can even position multiple layouts side by side on the screen and RW8 will remember them next time a project is opened. The simulator isn’t as comprehensive as the one in Adobe Dreamweaver, but there’s an option that allows designers to drag windows to a desired size and save those custom dimensions as other devices. Many of the sites I create are static and informational.RapidWeaver 8 plugs up a few holes in the application’s feature arsenal, starting with a device simulator to preview how sites should look on ten different iPhone, iPad, and Mac models in portrait or landscape mode, all in real-time as changes are being made. Also, with advances in HTML 5 and CSS 3, there’s also a lot of functionality that can be leveraged just knowing HTML & CSS well, maybe even enough for a simple basic website, which is where I prefer Blocs as you can see your code. I’m re-looking at my use of RW as development does not appear to be progressing. I’ve currently chosen the framework route with RW as frameworks are easy to keep updated although they are also more expensive. You also need to know which stacks your site depends on to work (so you don’t delete it) and if you maintain a number of sites that may well be a whole lot of info to keep track of. Over the years I’ve accumulated such a cruft of stacks with no real way of knowing which are still supported. There is an integrated update feature, but nothing to tell you if your stack contains deprecated code or if the developer has ceased updating. With RW where I have my main experience the stacks management is not the best. It can also add more code to your website if plugin developers are using the same open source code and you might get some occasional quirks where different plugins don’t work well together (although that’s very occasional). The difficulty is that the code behind the plugin is developer dependent. These all have to be purchased separately or in a framework (essentially a group of the plugins this is by far the best route in RW.) For example they can allow you to easily add social icons or media players or parallax views. These are essentially plugins that provide extra functionality when creating your site, they are plug and play. For RW and Blocs a lot of functionality comes through RW stacks and Blocs bricks (although with Blocs I believe you can also see the code).
0 Comments
Leave a Reply. |