Redesign the `Page Styles’ interface so a) you can see what colour item you have selected. Personally loved the old radio buttons from way back when…
1 Like
Actually it’s 2,037!
2 Likes
That’s more like it…bonkers!
I really need to know that the RW contact page will not result in failed emails (SMTP support) from prospective sales / customers!!! All Gmail email fails using the RW contact page (for me anyway)… This defeats the primary function of most any website doesn’t it??
An overhaul of the UI would be nice, more customisable in working arrangements & layout.
Compatibility with older Macs (High Sierra, purely for my own selfish reasons) would be good.
Don’t know if it’s a macOS/RW/Stacks thing but a dropdown colour picker would be nice, rather than the system one appearing on the opposite side of the screen where you don’t need it to be.
3 Likes
Second on the color picker. Either better integration with the os picker (not sure what that looks like?), or an integrated RW color picker.
2 Likes
Surely it is possible to make RW a bit more intelligent when it comes to publishing. I mean, you add a comma and it republishes more than 600 files!
2 Likes
Publishing has been getting flaky for me. What used to work perfectly now just hangs at a certain point. Sometimes it will work by changing the mode or the publishing method. Something changing the speed helps. Nothing consistent however. At this point, my largest site cannot be published to my web server. I have to publish to a folder on the desktop and then use Transmit to update my files on the web server. I am not happy that this workaround has become necessary. It would be very nice to have the publishing tool identify the page that may be the cause of the problem. That, at least, would allow for the possibility of fixing a problem page and thus allowing the publishing tool to function again. For me, this ranks as #1 and well beyond any other wishes on the list.
4 Likes
Auto Save… Auto Save… Auto Save…
@ablx – Almost everything that is “auto” is dangerous. Better to avoid it or disable it.
5 Likes
I’d like to see the promised rework of the blog feature finally see the light of day. We were told it was on the roadmap in 2018, but nothing has materialised. It also needs to integrate with stacks. I do not have one site that does not require a blog. Blog is a must these days. Yes there are lots of CMS plugins, but then I may as well switch to a CMS as a full solution. I like RW, but feel the development is coming mainly from the stacks developers rather than RW itself. If Stacks disappeared there would be nothing keeping me using RW.
Sorry for the direct comment, but it doesn’t help you as a developer if I beat around the bush.
There is a lot of competition out there, Blocs, Pinegrow, Static Site Generators as well as most hosting companies now make using Wordpress extremely easy. Gone are the days when you needed to mess about with mysql databases yourself. Themes like Divi (to which I own a lifetime licence), make it possible to create extremely fully featured websites. I like using RW and don’t want to switch and have to learn a different framework, but I’m increasingly being asked for sites that require information to be chronologically presented and RW is coming up short without plugins or stacks.
11 Likes
This may be out of scope/out of your control but many of us have been having issues with using cloud storage services and something about the RW project file doesn’t play nicely with services like Dropbox. It may be an issue on Dropbox’s end but it seems to be solely related to RW files (it’s worked flawlessly with all other file types for me).
I know some services seem to work better than others and, as mentioned, it may be out of your control anyway, but if there is anything that can be done to make the files more reliable with syncing services, that’d be great.
2 Likes
Hello,
All the experts wrote a great wish list for RW9: adding
- Publishing (I agree with @greggd1) a publishing tool to identify the page that may be the cause of the problem.
- NO Auto Safe (as it is dangerous).
I am hoping developers will read this comment and develop for us a better (Booking Stack and a Checkout), as the current ones are limited, it is the most requested by clients. Thanks
5 Likes
Top thing I’d love to see in RapidWeaver 9 is a better way to manage outputted resources.
When RapidWeaver compiles the HTML, including stuff output by Stacks and so on, I would love to be able to tell RapidWeaver that all of the static content (CSS, JavaScript, images, not the HTML/PHP) is going to be hosted on a separate (sub)domain.
Structure like this:
- example,xyz/contactus.html
- cdn.example,xyz/contactus_files/some_css.css
- cdn.example,xyz/contactus_files/some_js.js
- cdn.example,xyz/resources/contactus-title.jpg
- etc… (using commas to avoid it being real links)
This would allow for all of that static content to be hosted on a CDN. It’s fine if the entire output does not contain any PHP, but if a stack/plugin writes PHP code (e.g. a contact form), it is very hard to unravel the static content from the dynamic content in order to put the CDN-worthy data elsewhere.
I realise that this is perhaps “advanced” stuff, but FTPing files to a hosting service is so last decade!
@dan
It’s almost been three weeks, well eighteen days, since you asked. Which requests are going to make it into RapidWeaver 9? Is there a features roadmap that we could see to help manage expectations about what innovation we can expect and when?
I’ve been using Rapidweaver since version 3 and currently use version 7.5.5. I bought version 8 but it initially had trouble getting software updates on MacOS El Capitan 10.11.6. I plan on updating to a new Mac when MacOS 11 Big Sur comes out and will be looking for new website software to install on it.
I use one of the built-in themes (Affero) that came with Rapidweaver 7 and it supports Bootstrap. I don’t use Stacks, and I don’t think that Rapidweaver should have to depend on Stacks or Foundation in order to create nice looking web pages. Rapidweaver should be awesome on it’s own.
For Rapidweaver 9
-
I would like to see a responsive grid system built into Rapidweaver that either supports Bootstrap, Flex Box or is custom coded.
-
I would like to see drag and drop elements like containers, rows and columns that would support the grid system.
-
I would like to see a code view editor and be able to make edits on the page and in the code editor. Several other website software applications allow you to edit in design view and code view.
-
I would like to see an improved photo gallery page that supports a lightbox feature.
7 Likes
If Auto Save makes it into RW9, it needs to be switched OFF by default. Auto Save is so dangerous!
2 Likes
Ease of use/work flow requests all about resource management
- Could we have a simple indicator as to whether an asset was currently in use in the project?
- Could it also include the ability to show approximately ‘where’ it is in use used?
- Could we have the ability to 'refresh/reloa/‘swap out’ the asset in Resources Window then have each instance within the project replaced with this ‘updated/new’ version of the asset?
If this sounds like After Effects then we are on the right track.
Thanks For Listening
Cheers,
Craig
1 Like
Better support for Japanese fonts. Current implementation (inline html font specifications for each block of text) is really not suitable for all-Japanese websites, and current fallback font specifications (e.g., MS P Gothic, etc.) are long out of date. Given the numerous and continuously changing device-specific, font-display problems that can occur with Japanese text, we really need user specifiable fallback settings, and built-in support for Google web fonts.
1 Like
Screen Real Estate is always a problem so it would be good to be able to have a ‘tabbed’ windows. Example: one window with a tab for Resources and a tab for Library. Others may want to expand on this idea but for me this is a no brainer –– save valuable screen space, less fragging/opening/closing windows. All-to-gether enhanced productivity.
Thanks for listening.
Cheers,
Craig
Ha! It’s one of those things that really divide people. I loath tabs and always turn them off in browsers. Still, that doesn’t mean it shouldn’t be an option. Chacun à son goût!