I think this has been brought up before, but a thought I've had: Apart from
the fact that it will require a ton of work in coding, what would keep us
from separating templates (and, for that matter, images) from the article
text? Article text would exist by itself, and categories, templates, imag
Right. Wikipedia is about interesting and useful information, not about
coding.
Fred Bauder
> Really good points. I still advocate moving the possibility for these
> "ugly" constructs to templates, so that we keep all the magic tricks
> we have now, but lose the ability to make an article that is
- Original Message
> From: Stephanie Daugherty
> To: fredb...@fairpoint.net; Wikimedia Foundation Mailing List
>
> Sent: Thu, December 30, 2010 2:55:28 AM
> Subject: Re: [Foundation-l] Template Overkill
>
> Where there exists a clean elegent technical solution to a social
> problem
On 30 December 2010 08:55, Stephanie Daugherty wrote:
> Any solution that calls for endless templates is a bad one socially as
> well as technically, and at the point where you even consider
> something on that scale you should probably be consulting developers
> for a better way
> This goes for
- Original Message
> From: Fred Bauder
> To: Wikimedia Foundation Mailing List
> Sent: Thu, December 30, 2010 2:16:55 AM
> Subject: Re: [Foundation-l] Template Overkill
>
> > What project are you speaking of? At en.WS the entire navigation
> > structure of
> > how to move between
Domas Mituzas wrote:
> now that we have blinking banners, I'm sure we should try out how full-screen
> banners work, with "click to go to wikipedia".
If you could convince the fundraising folks that it would generate enough
money to justify ignoring the complaints, I'm sure it could and would be
i
now that we have blinking banners, I'm sure we should try out how full-screen
banners work, with "click to go to wikipedia".
Domas
___
foundation-l mailing list
foundation-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/f
Really good points. I still advocate moving the possibility for these
"ugly" constructs to templates, so that we keep all the magic tricks
we have now, but lose the ability to make an article that is "write
only" by littering it with code that only the wikigods and the parser
itself could decypher.
Where there exists a clean elegent technical solution to a social
problem then it wasnt really a social problem to begin with.
Where it comes to something like ws maybe a tool to do an outline
grouping a large multiarticle document into a single coherent one is
whats really needed.
Any solution t
> What project are you speaking of? At en.WS the entire navigation
> structure of
> how to move between Chapters within a book is encoded in templates. I
> can't
> imagine how they could be scapped.
>
> Birgitte SB
>
[[Moby Dick, chapter 2]] might work.
Fred Bauder
__
While i generally agree that its too much templates do have their
place. The interface for using a template needs to be easier (see all
the recent wysiwy* traffic), but used right they can even make the
text easier to edit.
The problem therefore is to make sure they are used right, and that
proble
> Most of the templates in our project, imho are just more clutter.
>
> The number of people who know how to use any particular template, can
> probably be counted with a box of marbles. However when others see the
> templates, they just shy away, they don't bother to try to learn them.
>
> If we
12 matches
Mail list logo
