asacolips wrote:I was actually just planning on starting a WordPress site as an SRD for this... ...If you're up for it, we might be able to merge those two project ideas and use yours as a base to start from. I could set up the structure and theme, and then you (and any one else interested) could work on getting all of the content in and cleaned up.
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.
asacolips wrote:Either way, I would definitely like to help on this. I'm an art director and web developer by trade, so I can contribute to it as time allows.
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.
asacolips wrote:I just saw your note about keeping it script based so that updates are push button. That would definitely be tricky with WordPress.
I'm less married to that idea (pure focus on the script) than I was when I posted that.
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.
That would be awesome.
All of the table of contents links are static urls like http://www.dustinian.com/stuff#named_anchor
. You'll want to strip everything from those URLs aside from the /bfrpg.html#named_anchor portion so that the file will work regardless of the domain.
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.
asacolips wrote:Performance on mobile devices is something to consider. With everything being in one .html file, phones have to pull in bits and pieces of the content at a time. It may be wiser to update the script to break each chapter into separate pages
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.
asacolips wrote:If you want, you can either give me access to your ftp to upload css files, or I can create a css file on my server and let you reference that in the head of your .html file. Once the css is completed, you can just copy the file over to your server and presto. I prefer the latter, as I would rather not have the ability to ftp in your site (security and all).
Right now the CSS is embedded in the document. If you could make your changes on the embedded stylesheet and then attach to a subsequent post, that would be ideal. I could then extract your CSS into a separate .CSS file later, one that would work with the PHP break-down I'm thinking of...
My first crack it this can be seen at http://bfrpg.llsrd.org/
. One thing I've noticed is that there really needs to be more classes in the HTML to help with styling specific sections. For instance, I wanted to break the spells into columns so that it would be easier to digest the amount of content there, but there's not a wrapper or class around the chapters so that the content inside them can be styled. With that said, navigation is starting to get quite bit easier now.
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.