is completely static. And page requires you to blog at
. Latest news/upcoming issues are also generated during site
deployment.
Karel
On Tue, 15 Oct 2013 08:20:15 +0200
Erik Jan de Wit <edewit(a)redhat.com> wrote:
Created an issue AEROGEAR-1334 and will look into arquillian site to
see how
they are doing this. Pull request coming
Cheers,
Erik Jan
On 14 Oct,2013, at 15:56 , Jay Balunas <jbalunas(a)redhat.com> wrote:
>
> On Oct 14, 2013, at 2:51 AM, Erik Jan de Wit <edewit(a)redhat.com> wrote:
>
>> Hi,
>>
>> So my suggestion was not to have something like
planet.jboss.org where we
>> have duplicate posts, but to have an aggregator to get blog posts from our
>> personal blogs that contain a special tag, 'aerogear' for instance, and
>> have jekyll download that rss.xml file then we can have a page somewhere
>> on the
aerogear.org site, that is the same style as the rest of the site,
>> with just links and maybe a short intro to the actual blog. That way
>> people searching for things about aerogear don't have to know all our
>> personal names and blog addresses and it doesn't kill SEO it supports it
>> as our blogs will even ranked higher in google. The only issue with this
>> approach is that we don't update the site that often, but that is also
>> something we could live with.
>
> This was my thinking as well but also perhaps looking into a way to use JS
> to update the article list from the feed instead of needing a full re-deply
> for updates. I believe Awestruct has some similar features for blogs and
> tweets.
>
> Imo at least something to look into. Erik - could you update the jira with
> some of this info and/or link to the thread so we can capture these ideas?
>
>>
>> On 11 Oct,2013, at 17:37 , Douglas Campos <qmx(a)qmx.me> wrote:
>>
>>> On Fri, Oct 11, 2013 at 04:52:52PM +0200, Heiko W.Rupp wrote:
>>>>
>>>> Am 11.10.2013 um 16:49 schrieb Jay Balunas:
>>>>>> Duplicated content hurts SEO, that's why I've been
avoiding it...
>>>>>
>>>>> Do you know the degree of impact here, or links for more details
for
>>>>> us to review. I did some quick searches and read some of them, but
>>>>> a lot seemed mixed, some good, some bad.
>>>>
>>>> SEO is one part of the game. The other is the visibility on
jboss.org
>>>> and also the feeds from it that people may have already subscribed to.
>>>
>>> AFAIK, our blogs are on
planet.jboss.org (at least my posts tagged with
>>> 'aerogear' appear there :P)
>>>
>>> Either way, our site is pretty different from
jboss.org (ours is 100%
>>> static html), and I don't think it'll be healthy to pull this feeds
on
>>> the client side. And this feels a little bit old too - hence why I'm
>>> trying to avoid the 'aggregator'.
>>>
>>> --
>>> qmx
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev