<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi AeroGear, FeedHenry<br>
<br>
As part of a review of Digger (Build Farm) docs, I created a <a
href="https://github.com/aerogear/aerogear.org/pull/687"
target="_blank">PR</a> to attempt to improve user navigation of:
<br>
</p>
<p><a href="https://aerogear.org/" target="_blank">https://aerogear.org/</a><br>
<br>
Feedback on that PR raised the question of general navigation of
this web site:<br>
<br>
* What should be in the Getting Started menu to help me get
started with digger? (I think digger is more than a code snippet
or library)<br>
<br>
* If I'm interested in digger, should I expect any digger info
under module or platform menu items?<br>
<br>
* I sometimes navigate to a page, but can't remember how I
navigated to it, then cannot find the info again.<br>
<br>
These issues can be resolved, but will require a lot of effort,
but another question is:<br>
<br>
* Will it provide us a platform to build the community we want?</p>
<p> The web site looks great, and I learn a lot from browsing it (eg
I didn't know about <a
class="m_-7459261403132971927moz-txt-link-freetext"
href="https://aerogear.org/sync/" target="_blank">https://aerogear.org/sync/</a>
until today), but I wonder if it is doing the job we want it to
do? and how do we keep it up-to-date? (<a
class="m_-7459261403132971927moz-txt-link-freetext"
href="https://aerogear.org/docs/planning/" target="_blank">https://aerogear.org/docs/<wbr>planning/</a>)<br>
<br>
Meanwhile over at:<br>
<br>
<a href="http://feedhenry.org/docs/" target="_blank">http://feedhenry.org/docs/</a><br>
<br>
Not much there at the moment, but it will be the location for
mobile.next doc <br>
<br>
* Do we want users switching from MCP doc on <a
href="http://feedhenry.org" target="_blank">feedhenry.org</a>
over to digger doc on <a href="http://aerogear.org"
target="_blank">aerogear.org</a> and back again for some fh.sync
doc?<br>
<br>
These are difficult and challenging questions, I don't expect them
to be easy to resolve and I'm happy to agree with whatever the
communities decide to do. All this mail hopes to do is to raise
the question of<br>
<br>
* How do we communicate the "mobile.next" (i.e. feedhenry mcp and
aerogear digger) message as cleanly as possible?<br>
<br>
(The real challenge occurs after that, convincing them to adopt
mobile.next, but users will never adopt if they can't find
answers they hit the first stumbling block)<br>
<br>
thanks,<br>
<br>
Paul</p>
</body>
</html>