R/C Naval Combat

Hey guys,

I've got some free time coming up in the middle of May between school and work - and I'd like to improve the Scuttlebutt with whatever you think it needs.

So feel free to leave comments, constructive criticism, or especially suggestions as to what you'd like to see added or changed?

Thanks guys!

Carl and I need to get up off our lazy butts and start writing articles for you. I think Carl just posted the nascent form of an article on cannon efficiency in the Technical: Weapons section. Some editing and fact checking are in order, but I think he's got a good start. There are some articles at RCWarships.org, under the Naval War College MkII that you might be able to get permission to print. Included there are some stuff on NASWCA and the creation of Big Gun (those may need some editing to make a single, whole article, though), modifications to radios, fiberglass hull construction, historical flags, prop and strut construction, and other goodies.

Consider that neither a web site nor a newsletter is a 100% perfect communication solution (nothing is) & that ideally they should complement one another.

My recommendation:

Use a newsletter for content that has a "short shelf life". IOW, for the types of content where interest tends to be time-sensitive. Examples include upcoming events, battle accounts/scores/photos, personal recognitions, fluff/filler. In general, whatever is interesting [I]right now[/], but is likely to be less interesting a month from now, should go into a newsletter.

Use a web site to offer content that is interesting for a longer period of time. Technical articles, longer-term event schedules, ongoing cumulative scoring, contact lists, etc. are perfect for a web site. Subject matter that isn't particularly time-sensitive should go on a web site.

A major exception, that isn't really an exception at all, is that a newsletter archive is a perfect fit for a web site. Past newsletter content sometimes needs to be referenced, & a web site makes a handy place to put it even though it may seem to technically fit the "short-term interest" model. It's generally a lower-priority type of long-term-interest content, though, & should be accessible but not prominent.

Another apparent exception is that a web site needs to have a very current "Current Events" (& near-past) page that's prominently displayed, preferably when most general visitors land. Nothing says, "We're an active, dynamic, going concern!" quite like an initial landing page that shows you the absolute latest news, both immediate past & upcoming (i.e. yesterday's & today's results, today's & tomorrow's schedules). OTOH, nothing says "We're not doing much" like a site that has "upcoming" events 2 years old, or the same pictures, articles, etc. every single time that a visitor lands there. Again, this isn't really an exception to the general rule, but rather an expansion that probably should be made. A web site is ideally suited for content that is of interest either in the very immediate short term (i.e. right now, today, ± 1 day) OR long term (> 30 days); the newsletter fills the gap in-between.

JM

quote:

---

Originally posted by JohnmCA72



Another apparent exception is that a web site needs to have a very current "Current Events" (& near-past)

---

He is right, newsletters can have "current events"; simple small info tidbits if they are ultimately right or wrong doesn't matter... just opinion.

Example: of "very current" developing stories:
The "Big Gun Confederation" conversation you and Rob are having?

quote:

---

Originally posted by JohnmCA72
Yeah, that may be an interesting current topic to some. Later, once the whole issue is resolved, dropped, moved...
JM

---

This is what I was talking about... I'm suggesting that it could be an article, even though it is not yet done. Even if nothing ever comes from the conversations.

People are constantly trying to do things... even if they fail to actually accomplish something it's still news.

Thanks guys, as far as articles go I'm not the best person to be writing them - due to other work, and I admit I am not that knowledgeable in the technical aspects of this hobby. However, I would be more than happy to publish any articles such as the one discussed above if one of you are willing to write it.