Normally I just would have left a like and a review at RapidWeaverCommunity.com – but this stack doesn’t seem to show up there. So I’m raving here – if that’s inappropriate, let me know.
The stack is Scribe by Big White Duck. What do I like about it? I could tell you, but I’d prefer to show you…
This is a Scribe stack in a Foundry Overlap. Normally, to do what you see here I would have used two headers, some kind of stack that allowed floating images, a ParagraphPro stack, and another Paragraph stack. This is all one stack, though – the headers are markdown, the image and drop cap are child stacks that are built in to Scribe.
It’s just…nice. One other cool thing – every paragraph in the Scribe stack is wrapped neatly in it’s own <p> tags.
I’m a big fan of this stack, and of Big White Duck stacks as well. I admire the work that @tav puts in on these. And also – the name “Big White Duck!” Who doesn’t like that?
This is the case for absolutely any stack though assuming the user can code and can write their own CSS to support the HTML. Seems to defeat the idea of RW and stacks though.
Au contraire, @tav, old bean. It is very useful when transitioning from an old site created with an html editor, allowing you to paste paragraphs into your new RW site. In the long term, of course, I’d prefer to use Scribe or Paragraph stacks, although it sometimes takes me a long time!
As a big fan of Scribe, I’m sorry Peter, but adding some text to a HTML stack, presumably wrapping each paragraph in <p> is hardly doing the same as Scribe.
It’s a bit like saying you can do everything a car can do with a horse and cart.
I would like to chime in again with a practical example of what I used Scribe for not too long ago.
I am currently creating a website for a writer, and she wants a few examples of her work online. Each of these consists of at least two to three hundred paragraphs. I could have separated each paragraph out into a paragraph stack – but I’d probably still be doing that… Using Scribe, however, I just pasted the text in, and now the paragraphs are correctly formatted in html.
Also: when I showed the author the Drop Cap and Lead Paragraph features, she was very enthusiastic, so I’ve ended up using those as well.
@peterdanckwerts You can of course paste HTML straight into markdown areas and mix and match. The Scribe styling controls will work on both the markdown and HTML content. The markdown content is immediately processed into HTML in edit mode any how.
The more I use Scribe the more I learn and the more I become impressed at just how much this feature rich but lightweight stack can achieve - a formidable stack for sure - as a community we are seriously blessed to have @tav support us.
Thx for the review everyone!! I’m totally new to Raid Weaver and I’m learning how to use it. The concept is foreign to me and knowing what stacks to use for Type is very very helpful!!! -Allen
As per the first line of text in the demo file: “You do not need Foundation…” There is a list of stacks used in the project and none of them are Foundation. You can simply change the theme to Foundry. All the other required stacks to see the page as it is published are free ones.
The below example project uses the Foundry theme with the read more enabled for a custom paragraph using the template ^ symbol
I’ve also put in 2 floating images, one left and one right using the position setting in the Floating Image child:
Using Scribe, however, I just pasted the text in, and now the paragraphs are correctly formatted in html.
