<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><br></div>How about this?<div><br></div><div>One site, one brand. </div><div><br></div><div>Restructure </div><div><div><a href="https://www.webarch.net/">https://www.webarch.net/</a></div><div><br></div>Abandon</div><div><div><a href="https://ecohost.coop/">https://ecohost.coop/</a> </div><div><a href="https://sysadmin.coop/">https://sysadmin.coop/</a></div><div><a href="https://ecodissident.net/">https://ecodissident.net/</a> </div></div><div><br></div><div><br></div><div><br><div><div>On 18 Nov 2014, at 11:13, Mark Nielsen <<a href="mailto:m@m9n.uk">m@m9n.uk</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">If there's a lot of duplication of content, I think I'd recommend putting most effort into a central hub site (<a href="http://webarch.net/">webarch.net</a>?) and having the other services/brands being pretty much one-page wonders - possible all following a "house style" in terms of layout, branding and "atmosphere". That way you'd have your cake and eat it - appealing to different target markets, and letting each market know their service is run by a solid, ethical core co-op with broad interests and experiences.<div><br></div><div>I don't know if that conflicts with your ideas? I do think that running multiple brands can be a massive drain, so trying to simplify them as much as possible would probably be a good principle to try to follow...</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 18 November 2014 11:04, Chris Croome <span dir="ltr"><<a href="mailto:chris@webarchitects.co.uk" target="_blank">chris@webarchitects.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto;">Hi<br>
<span class=""><br>
On Mon 17-Nov-2014 at 12:45:52PM +0000, Nick Hardiman wrote:<br>
><br>
> How does this sound to you?<br>
><br>
> <a href="https://ecohost.coop/" target="_blank">https://ecohost.coop/</a><br>
> single page site offering various types of hosting.<br>
><br>
</span><span class="">> requires page migration. Move pages from<br>
> * <a href="http://www.webarch.co.uk/hosting" target="_blank">http://www.webarch.co.uk/hosting</a><br>
> * <a href="http://www.ecodissident.net/virtual-servers" target="_blank">http://www.ecodissident.net/virtual-servers</a><br>
> * <a href="http://www.ecodissident.net/hosting" target="_blank">http://www.ecodissident.net/hosting</a><br>
> to<br>
> * <a href="http://ecohost.coop/hosting-plans" target="_blank">ecohost.coop/hosting-plans</a><br>
<br>
</span>It sounds good, but I'm not sure where other pages from the existing<br>
site, under hosting, <a href="https://www.webarch.net/hosting" target="_blank">https://www.webarch.net/hosting</a> would live,<br>
specifically:<br>
<br>
- <a href="https://webarch.net/domain-names" target="_blank">https://webarch.net/domain-names</a><br>
- <a href="https://webarch.net/email" target="_blank">https://webarch.net/email</a><br>
- <a href="https://webarch.net/certs" target="_blank">https://webarch.net/certs</a><br>
- <a href="https://webarch.net/backups" target="_blank">https://webarch.net/backups</a><br>
- <a href="https://webarch.net/colocation" target="_blank">https://webarch.net/colocation</a><br>
<br>
There are also the docs, we also need to add lots more documentation here:<br>
<br>
- <a href="https://webarch.net/docs/" target="_blank">https://webarch.net/docs/</a><br>
<br>
I almost wonder if we should duplicate all the information from the<br>
single pages sites:<br>
<br>
- <a href="https://ecohost.coop/" target="_blank">https://ecohost.coop/</a><br>
- <a href="https://sysadmin.coop/" target="_blank">https://sysadmin.coop/</a> (BTW we haven't registered this yet)<br>
- <a href="https://ecodissident.net/" target="_blank">https://ecodissident.net/</a><br>
<br>
On the <a href="https://webarch.net/" target="_blank">https://webarch.net/</a> site?<br>
<br>
I know duplication is bad but if we don't then we will have to keep<br>
directing people off the <a href="http://webarch.net/" target="_blank">webarch.net</a> site to the other sites and this<br>
might be more confusing?<br>
<span class=""><br>
> <a href="https://ecodissident.net/" target="_blank">https://ecodissident.net/</a><br>
> single page site for...what?<br>
<br>
</span>Shared hosting and virtual servers in Iceland and some text about the<br>
IMMI, <a href="https://immi.is/" target="_blank">https://immi.is/</a> and renewable electricity? I suggest we also drop<br>
all the special offer donations apart from the IMMI one:<br>
<br>
- <a href="http://ecodis.net/offer" target="_blank">http://ecodis.net/offer</a><br>
<br>
All the best<br>
<span class="HOEnZb"><font color="#888888"><br>
Chris<br>
<br>
--<br>
Webarchitects Co-operative<br>
<a href="http://webarchitects.coop/" target="_blank">http://webarchitects.coop/</a><br>
<a href="tel:%2B44%20114%20276%209709" value="+441142769709">+44 114 276 9709</a><br>
@webarchcoop<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
webarch-websites mailing list<br>
<a href="mailto:webarch-websites@lists.webarch.co.uk">webarch-websites@lists.webarch.co.uk</a><br>
<a href="https://lists.webarch.co.uk/mailman/listinfo/webarch-websites" target="_blank">https://lists.webarch.co.uk/mailman/listinfo/webarch-websites</a><br>
</div></div></blockquote></div><br></div>
_______________________________________________<br>webarch-websites mailing list<br><a href="mailto:webarch-websites@lists.webarch.co.uk">webarch-websites@lists.webarch.co.uk</a><br>https://lists.webarch.co.uk/mailman/listinfo/webarch-websites<br></blockquote></div><br></div></body></html>