Re: Static pages for PUGs?
От | Jonathan S. Katz |
---|---|
Тема | Re: Static pages for PUGs? |
Дата | |
Msg-id | 8BFD618B-16A9-4472-9822-B79E8EFEC87E@excoventures.com обсуждение исходный текст |
Ответ на | Re: Static pages for PUGs? (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: Static pages for PUGs?
|
Список | pgsql-www |
> On Thu, Jan 26, 2012 at 15:35, Jonathan S. Katz > <jonathan.katz@excoventures.com> wrote: >> On Jan 26, 2012, at 9:23 AM, Magnus Hagander <magnus@hagander.net> wrote: >> >>> On Thu, Jan 26, 2012 at 15:21, Alvaro Herrera >>> <alvherre@commandprompt.com> wrote: >>>> >>>> Excerpts from Magnus Hagander's message of jue ene 26 06:37:12 -0300 2012: >>>>> On Wed, Jan 25, 2012 at 23:52, Josh Berkus <josh@agliodbs.com> wrote: >>>>>> WWW, >>>>>> >>>>>> Since pugs.postgresql.org has died, do we want to create some static >>>>>> pages for the various active PUGs, which will have links to the mailing >>>>>> list and external resource (wordpress, Meetup.com, etc.) for each? >>>>> >>>>> I think the general idea was to have a wiki page (or more) for each. >>>>> And probably a wiki category for all of them (Category:UserGroups for >>>>> example). That will also give you an automatic index. >>>> >>>> So would we have a redirect from pugs.postgresql.org to that wiki >>>> category? >>> >>> We could if we wanted to, yes :-) But first, we need to actually have >>> those pages on there... >> >> Would a viable alternative be to use the organizations from the main site and just classify which ones are PUGs? > > Certainly - but I thought the organizations wanted to be able to add > their own custom information and not be bound by the limited number of > fields there? > > Or do you mean just use that as a list, and use the URL field there to > point to the custom page? Both? ;-) FWIW I don't think PUGs really need too much custom info - name, managers, brief description, URL to meetup/whatever page,link to events posted in the system. I also realize by making these suggestions that I am most likely volunteering myself for these changes...
В списке pgsql-www по дате отправления: