> While Greg is right when he says that we can't choose a CMS without
> knowing , it is also clear that if we want to try
> them ourselves first we need to install them etc, and this takes time
> anyway.
>
> Let's see. Who can help installing and setting up these CMSs?
>
> - Drupal - http://live.gn
[snip]
> How do we get people to value our fundamental strengths, and not
> superficial advantages, like a powerful feature that may show up in the
> next version of Windows or OS X (or some app)? If our users value what
> we truly value, then they won't disappear when someone provides them a
> shi
--- Gergely Nagy <[EMAIL PROTECTED]> wrote:
> Quim, and Gazim was it? "Not scrolling" is soo
> overrated. Screen sizes
> (and windows sizes!) are not uniform, so there is no
> way of avoiding
> scrolling. (To rant a bit, I hate designs which
> impose too much
> structure on a web page. It might lo
Hi everyone!
I hate to interrupt all this awesome w.g.o work, but here's a topic I've
thought about for a long time, and still haven't figured out. And I
think it's important that we have great answers for it.
How are we compelling to regular people?
Every time a technical friend asks me to expl
On Mon, 2006-08-07 at 19:31 +0100, Michael Maclean wrote:
> If you want, I can host an eZ publish install and answer any questions
> about it, or failing that refer them to the folk who write it. I'm not
> wanting to be seen to be shoving it at anyone, but I do like it and
> think it suits this
El dl 07 de 08 del 2006 a les 18:21 +0100, en/na LeeTambiah va escriure:
> I guess thats your intention right?
Yes, the CMS needs to be adapted to our look'n'feel, not the other way
round.
About the design of the primary navigation, have a look at the one used
at http://guadec.org since it was
El dl 07 de 08 del 2006 a les 22:53 +0200, en/na Claus Schwarm va
escriure:
> Most users who are likely to visit wgo are probably happy with the
> screenshot tour, a link to gnomefiles, and links to some other project
> homepages.
Conclusion: we need to add the GNOME tour to
http://live.gnome.org
El dl 07 de 08 del 2006 a les 19:00 +0200, en/na Gergely Nagy va
escriure:
> How about the evolution of gnome, i.e. how it all started? We cannot
> guarantee somebody won't come up with an app/project/product name that
> won't clash with other "normal" content...
Language is so rich, we can find
On Tue, 8 Aug 2006 04:15:04 +1000
Jeff Waugh <[EMAIL PROTECTED]> wrote:
>
> I started on this thread by suggesting that we're approaching the
> problem the wrong way. I'm still saying it. Does your Mum want a
> software map? Mine doesn't. Mine wants to know more about "Tomboy"
> when her friend t
Gergely Nagy wrote:
> We ought to test as many aspects as possible before deciding, including
> installation, administering, enter sample content, manage the content,
> try themeing, etc.
If you want, I can host an eZ publish install and answer any questions
about it, or failing that refer them t
On Mon, 2006-07-08 at 15:54 +0200, Gergely Nagy wrote:
> Gezim and Jeff: controlled duplication of information is not a bad
> thing. One reason is aggregation, for example the blog planets. There is
> added value in pulling info together from a number of places. Another is
> repetition while drill
> The original subject of this thread was Software Map
Which is the wrong way to think about the problem, isn't it? That's why I'm
pushing for a different way of thinking about it.
> Currently /projects/* _is_ just a list of applications
It's not really. Have a look. It's a grab-bag of crud. L
On Tue, 2006-08-08 at 02:36 +1000, Jeff Waugh wrote:
>
>
> > Jeff: I'm obsessed with URLs because it reflects the organization of
> > content, which is what we are discussing here.
>
> Talking about URLs just distracts from your focus on the design. You're
> putting the horse before the cart. Al
>The CMS outputs webpages, and we want them to look GNOMEy. So we need a
>design to create a template or theme from.
Now I understand, well in that case then I think mockups should be made
graphically. When the CMS has been chosen then the template can be made for the
CMS via PHP, XHTML and CSS
> Hmm. So we are talking about leaving wgo/projects/* _as is_ for this
> release
Given the state of plans for dealing with /projects/ I'd say that ought to
be an unqualified YES (though I've suggested this before).
> My humble vote is against a bastard solution where both old and new "CMS"
> co
On Mon, 2006-08-07 at 17:12 +0200, Quim Gil wrote:
> If you were looking for info about Evolution you probably will know. If
> you don't have a clue what Evolution is, /app/evolution won't give you
> much more info ("it is an application" - "great, but almost everything
> in gnome are apps, so what
> One thing that is baffling me at the moment is talk of the CMS, If we
> create pages for wgo, wouldn't we have to implement this into the CMS
> anyway? In other words why are we creating a template when we will be
> using a CMS. I believe I have a misunderstanding here, could someone
> explain?
Referring to http://live.gnome.org/GnomeWeb/LooknFeel I would say from
the examples we are looking for something like at
http://www.java.sun.com in terms of the header and drop down menus.
However the use of drop down menus is a concern for assess ability I
tested the Java site and no drop down men
> > For example, someone mentioned wgo/inkscape during the discussion, and
> > it's hard to see what makes Inkscape so special to, well, "deserve" our
> > special attention.
>
> True, that was a bad example I provided without much context. Please
> substitute in our discussion wgo/inkscape by wg
El dl 07 de 08 del 2006 a les 18:02 +0200, en/na Claus Schwarm va
escriure:
> For example, someone mentioned wgo/inkscape during the discussion, and
> it's hard to see what makes Inkscape so special to, well, "deserve" our
> special attention.
True, that was a bad example I provided without much
> Jeff: I'm obsessed with URLs because it reflects the organization of
> content, which is what we are discussing here.
Talking about URLs just distracts from your focus on the design. You're
putting the horse before the cart. All this talk about projects.go and
/apps/ and so on - these *are* im
We ought to test as many aspects as possible before deciding, including
installation, administering, enter sample content, manage the content,
try themeing, etc.
On Mon, 2006-08-07 at 17:44 +0200, Javier Vazquez wrote:
> Hi!,
>
> El lun, 07-08-2006 a las 17:35 +0200, Quim Gil escribió:
> > While
Hi,
On Mon, 07 Aug 2006 17:12:05 +0200
Quim Gil <[EMAIL PROTECTED]> wrote:
> I still don't see why it is us wgo maintainers offending people.
Because *we* obviously decide which projects gets "promoted" with the
GNOME web resources. If our choice appears to be arbitrary, people
may get angry (o
Hi!,
El lun, 07-08-2006 a las 17:35 +0200, Quim Gil escribió:
> While Greg is right when he says that we can't choose a CMS without
> knowing , it is also clear that if we want to try
> them ourselves first we need to install them etc, and this takes time
> anyway.
>
> Let's see. Who can help ins
While Greg is right when he says that we can't choose a CMS without
knowing , it is also clear that if we want to try
them ourselves first we need to install them etc, and this takes time
anyway.
Let's see. Who can help installing and setting up these CMSs?
- Drupal - http://live.gnome.org/GnomeW
El dl 07 de 08 del 2006 a les 15:54 +0200, en/na Gergely Nagy va
escriure:
> I suggested the wgo/apps/appname URL instead of wgo/projects/appname
I think at this point we agree that we are talking about
applications/products/software and not about projects/teams/people for
this specific case. We
Hi,
mega answering roll follows
First of all, Quim, thanks for coming up with such a great diagram! I
think it illustrates well what we are aiming to do, and it can help the
discussion a lot.
Jeff: I'm obsessed with URLs because it reflects the organization of
content, which is what we are disc
Thanks Gezim for your ideas about the wgo homepage. I have picked them
and I have listed them at http://live.gnome.org/GnomeWeb/NewWgoStructure
("Homepage") together with some more ideas that were at
http://live.gnome.org/GnomeWeb/LooknFeel
We need to build a sensible proposal for the homepage wit
Hi Marcus,
On sam, 2006-08-05 at 15:47 +0200, Marcus Bauer wrote:
> Remaining question: they need the GNOME logo in web and print
> resolution. A web logo is not too difficult to find, but in print
> resolution I don't know where to take it from.
You can find the SVG version of the logo here:
htt
Hi all,
On dim, 2006-07-23 at 11:46 +0200, Quim Gil wrote:
> Agree on date and time for a chat during next week and I will be there.
> European mornings and nights are better for me, afternoons are really
> complicated.
>
> El dg 23 de 07 del 2006 a les 17:40 +0800, en/na Davyd Madeley va
> escri
El dc 02 de 08 del 2006 a les 15:00 +0100, en/na Joachim Noreiko va
escriure:
> What should wgo provide to a visitor?
... or what wgo wants visitors to provide. ;)
First we need to identify the visitors we want to satisfy best. Let's
concentrate on
* third party developers
* public administra
31 matches
Mail list logo
