In hindsight, I don't think there's a lot of benefit to using WordPress for this, as that would only make it easier to update the specific issues in the content. And it would add PHP/mySQL database overhead that we don't need. Keeping it in .html files is probably the best route, but we would need to separate them into several individual files, I think. If we were to use a CMS and templating, a lightweight flat file CMS like http://picocms.org/ might work well.Dustinian wrote:I am up for that. Let me know what I can do to help and/or facilitate. I'm not familiar with Wordpress. Would you like the HTML converted to... BBCode? Truly, I'm not familiar with Wordpress at all.
That works for me.Dustinian wrote:Thanks. I'm an ex-technical writer. I'm good at single-sourcing and document structure, but I'm terrible (or, at best, generic at true "design"). So the best thing an art director can do for me would be a good stylesheet so that I can stay focused on my document structure, trusting that "look and feel" are taking care of themselves. That would delight me.
I still think it's a valid point though. When I made my first attempt at an SRD, I probably spent a full two period just trying to clean up the content, and it was never completely cleaned up. Breaking it down into scripts like this is a much more forward looking option in the long run.Dustinian wrote:I'm less married to that idea (pure focus on the script) than I was when I posted that.
I've actually started work on both parts of this and there is a mobile/tablet theme in place. For whatever reason I can't get work out why it's not working on actual mobile devices yet, but you can resize your browser window to get an idea of where I'm going with it.Dustinian wrote:That would be awesome.asacolips wrote:I can put together a really nice stylesheet that's responsive for mobile devices and includes a fixed navigation system, so that the user doesn't have to scroll back to the top.
 I've got the mobile and tablet bugs worked out now. I hadn't updated my .html file to include the script files, which prevents the tables from breaking out of the content area. That bug has been resolved, so this is now usable on a mobile or tablet device. Performance is a bit dicey though, like we were expecting.
I goofed. I saved the files locally so that I could work on it until we figure out a better solution, and didn't think about how saving the HTML files would make those links non-relative.Dustinian wrote:No, the links are relative. Did you look at the document's source, or hover over the hyperlinks? If you hover over, yeah, they look like absolute links. But they're not. I'm a better tech writer than that.
Like I said up top, the script idea is good and it's only the single .html file that's less than ideal. It should be pretty trivial to do some file working where we can define a generic html portion (maybe the head and footer sections) and then break everything else into chunks. We could then make separate files starting with the generic portion and then copying in the chapter chunks.Dustinian wrote:I had been arriving that that conclusion myself. That's why I'm less married to the script notion than before. My new notion is to break up the document into a bunch of PHP files, and then "include" them into different templates.
jQuery 1.11.1: http://bfrpg.llsrd.org/jquery.min.js
Scripts File: http://bfrpg.llsrd.org/script.js
Eh, I could go either way on that. I've used divs more times than I can count, but I've worked with articles and some of the new HTML5 markup quite a bit as well. I'm not too worried about it, as long as we can get some classes on them, like <div class="chapter" id="part_1_introduction"> or the same thing, but as an article.Dustinian wrote:That's awesome. I should be able to add part/chapter wrappers. Do you prefer divs or these newfangled "article" HTML5 things? Either way, let me know and I can spend some time tonight working on editing the script.
For now, yard work calls. Thank you, asacolips, for the excellent reply and thoughts.
Update: Holy crap, that is super awesome. I hadn't actually tried the TOC when I posted the above. Your TOC is AWESOME. Please let me know how I can continue to facilitate your excellent work.