Break up "for authors" about journal_information HOT 8 CLOSED

Right now it seems like a combination of all of the above, plus notes to ourselves

So, right now it's all in one file because that's what the website gives us. In terms of what we WANT:

I think what you lay out is pretty good. I think we can shuffle things around, but it will be pretty easy once all of information is out.

Here's my suggestion. We start writing out these different documents in markdown in the journal_information repository. We can then decide if we want to turn them into articles (like in LaTex, but easy, since just text), or put them some where else, like a Github pages.

David, how do you want to divide up the work on the documents?

from journal_information.

@mrshirts - I'm going to start with working on "Why LiveCoMS" and will see how far I get; I don't have that much time this weekend, so it's unclear. Why don't you start where you want, and I'll start with that, and then we can meet in the middle?

(In other words, maybe you can post a list of things you'll work on in order, and when I start working on these I'll start at the bottom and work my way up.)

from journal_information.

1. I will break up the "for authors" sections into roughly what you describe above. I will put the separate sections as .md files in editorial_material for now. Should be done today (11/19).

2. Once that text is in, I will experiment with two ways of posting it; as webpages on a github pages, and as pdf articles on Livecoms. Probably just start with one, since I will probably have to move the article to latex.

from journal_information.

A single article with well-delineated sections may be all that's needed; as I noted above one issue we're fighting with for material on the actual website is that the text is quite big so it looks like we have tons of random material on there even if we don't. If you format as a PDF, well organized into topical sections with clear headers, it will probably look like a nice short amount of material that's easy to read.

Though, it still may ultimately make sense to split things up into at least a couple varieties of documents, as we're dealing with pretty disparate types of information here, including instructions and policies, info about how things work, etc.

from journal_information.

I'm thinking fewer articles, organized into sections might be better. Let me think about how to organize.

from journal_information.

OK, I've rewritten the information as a shorter for_authors.md page, which I have copied over to the main web site. It now links out to https://livecomsjournal.github.io for the expanded information, but this could be turned into an article on the journal as well. I figured since this was the OTHER way to display the information (other than an article), it might be easier to start with displaying it this way, and we can try turning it into an article after.

This is PR #10

from journal_information.

Note - one the Markdown formatter on the scholastica web page leaves in page breaks. So if we page break the .md files in github, then they look weird. I could erase them when we copy the files over -- not a big deal if it happens somewhat infrequently.

from journal_information.

I think this all looks rather good to me now (at least as of my PR #9 which resolves some remaining issues), so I'm marking this as closed for now. Re-open if you disagree.

from journal_information.