@Summers, I agree that we don't have to document whole process of setting
the environment up,
but the docs should at least guide users that are completely new to the
subject appropriately.
Use case: I haven't developed anything on native Android yet, and I want to
change that. I want to make that shift with AeroGear. But what should I do?
I know AeroGear, nothing else. Where should I go now to get the basics
AeroGear expects from me?
So First Steps guide can cover what are expectations from the user on
development environment side. It may just contain brief description of
prerequisites and few links where people may get more information.
It can also contain our preferred/opinionated way of Android development,
being it an IDE of our choice or whatever.
On Wed, Feb 18, 2015 at 5:37 PM, Summers Pittman <supittma(a)redhat.com>
wrote:
On 02/18/2015 10:14 AM, Lukáš Fryč wrote:
Hey guys,
the new site is in baking for a quite some time, but I believe the
results are already shaping up. The Big Thanks go to Andres off course!
I must say it is NOT COMPLETE yet, but I believe we can start receiving
issues. Especially kind of "we need complete rework of this section" kind
of issues ;-)
http://staging-aerogearsite.rhcloud.com/
Please discuss bigger issues right here,
I need to make a JIRA to change the Android section of first steps. There
is no reason anyone should be compiling the Android library. However part
of that will include moving the how to build the Android library docs.
Where should those go? Also what should replace it? Getting started with
he Android libraries is basically include the stuff you want in your
build/pom and use it.
Also, I noticed the getting started docs for Cordova include a lot of
basic "what is cordova" flavored information. Should we really be
concerned on the project page with teaching people how to use the platform?
but file any smaller issues under appropriate place in the New Design
Epic:
https://issues.jboss.org/browse/AEROGEAR-1546
Few bigger issues I identified and that I will need a help with:
1. filling in Core and Security landing pages
2. Guides for First Steps are missing for some platforms (they don't have
to be overwhelmingly verbose, but at least we should have some)
3. connected individual's blog to News page (powered by
planet.jboss.org,
more info on IRC)
Few issues that we still need to tackle - I believe we can cover that
with Andres, but help is always welcomed!
1. make News page work javascript-wide (filtering, etc) [me]
2. document how-to + style guide for drafting/posting new posts on
aerogear.org [me]
2. style individual Guides
3. style individual Posts
4. HTML structure corrections (e.g. wrong use of HTML tags) [Andres]
5. grammar/typo corrections [Catherine offered help here]
Some features I planned originally will slip from the first release, but
the main priority now is get the New Site out!
ETA: the site could be nearly production-ready end of this week.
Cheers,
~ Lukas
_______________________________________________
aerogear-dev mailing
listaerogear-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev