There's always going to be that fuzzy line between, "how do I do this?" and, "how do I do this with Sigil?" There's always contention about what belongs and what doesn't, but I don't really see the point of toeing a rigid party line when it comes to answering questions in a subforum. The moderators (and I have to constantly remind myself that I am one of those for this subforum) will move what they deem across the fuzzy EPUB/Sigil line. For the rest of the posts, my attitude is to respond if I know the answer. The answer will follow it to its new home if the post is moved.
The fact that Sigil still claims WYSIWYG editing of epubs as a feature automatically means that we're going to get questions from people who don't know enough about (x)HTML/CSS to do what they're trying to do with Sigil. I suppose we could turn them away at the door with links to various (x)HTML/CSS/EPUB tutorials, but that won't generate much goodwill toward Sigil. So I tend to answer the questions AND point to the fact that they may want to brush up on (x)HTML/CSS (unless it's so far out of scope that it needs to be moved).
Bottom line is that many people simply don't know what's, "NOT Sigil." And a terse, "that's NOT Sigil" response won't help them to do so.
|