@RobMustard
Right, apologies for that. Basically I was speculating on a potentially simple solution which would allow people to go to a simple site, paste in a URL and get back a table of all the stacks that were used on the page residing on that URL. I think it would be pretty straightforward.
But now that you have articulated what you really need its possible to be a bit more helpful (hopefully).
Firstly, I completely understand where you are coming from. The demo pages for stacks and things can look, somehow, just beautiful, then when you go and try to recreate it - even with the same stacks… you end up, if you are anything like me, with a dogs breakfast.
Annoying.
The explanation, I think speaks to the difference between a web/ui designer and a draggy/droppy Rapidweaver or other WYSIWYG jockey. Just because you can drag a stack onto a page, that does not make you a designer, or at least, a good one.
The people who are putting those nice pages together have some skills, such as an understanding of space and compositional rhythm. How to use colour and styles to create pleasing elements which flow together effortlessly. No stack or theme can teach you this as far as I know.
I have three suggestions:
1/ Study, as much as possible, pages or sections which ‘work’ for you. Take the time to deconstruct what the designer has done to create the effect. Ask yourself why it works for you… For me (personally) its usually because the content is styled tastefully with no garish twirling flashing crap and is easy to consume.
2/ Practice. Take the time to recreate - very very carefully, layouts and elements from example sites you liked. Take your time and experiment with padding/margins/colours/gradients/textures/fonts/outlining/smoothing techniques/overlays/one-page-one-effect and so on. One thing I used to do was go to ThemeForest: https://themeforest.net/ look at the best selling themes then every couple of days try to recreate one of those theme layouts or pages in a scrap RW project. You learn fast that way!
Often you can make a project much better by removing crap you just don’t need. You have to keep at it. Practice and get feedback.
3/ Cheat. Well, sort of. Have you seen these?:
http://rapidweavercentral.info/modules/
They are some of the best Rapidweaver work ever produced, to my mind. These modules are ideal for you to reverse engineer, exploit and learn from. Marten is doing stuff in these modules that a few short years ago was proper ruddy awkward to do in RW. Mr Duck’s next-gen stacks might have had something to do with that too
Never give up. Never surrender.