Drupal Main Theme page - A Suggestion for Improvements
Dries, can you +1 this and Robin and myself will implement it. Thanks, Trae --- Original email sent to themes@drupal.org --- Hi all, If you go to this page: http://drupal.org/support You will see a variety of information for someone looking for support. However, if you go to the main Drupal Themes page, you are simply confronted with a bunch of themes to download. I suggest we create a Launching page for the Main Themes page too. We should have at least the following: 1. Prominent Large Image pointing to the Themes Gallery (Think Drupal News Letter "Ad" on the front page of Drupal.org) Perhaps links to themes hosted elsewhere. (offsite from drupal.org) 2. Themes Help area that lists the following links: - Basic Themes Help: http://drupal.org/node/39451 - Manage inconsistancy in themes: http://drupal.org/node/37156 3. IRC Channel This should simply mention the #drupal-themes irc channel on irc.freenode.net. 4. Mailing list info Info about this mailing list. 5. Other stuff... ... I'm not sure who is the person that would or does have the permissions to do this. I would not mind doing it if Dries gave me access to the site to do it. Thanks for your time, Trae -- Trae "occy" McCombs || http://occy.net/ Founder - Themes.org // Linux.com CivicSpaceLabs - http://civicspacelabs.org/
It might be a good idea to come up with a generic mechanism to provide 'Relavant links' or 'Context-sensitive information' on drupal.org. The obvious solution would be using blocks. We have 'information blocks' on http://drupal.org/cvs and handbook pages already. So, +1 but take a moment or two to come up with a generic solution that can be standardized for different pages or sections of drupal.org. On 20 Dec 2005, at 19:21, Trae McCombs wrote:
Dries, can you +1 this and Robin and myself will implement it. Thanks, Trae
--- Original email sent to themes@drupal.org ---
Hi all,
If you go to this page: http://drupal.org/support
You will see a variety of information for someone looking for support. However, if you go to the main Drupal Themes page, you are simply confronted with a bunch of themes to download.
I suggest we create a Launching page for the Main Themes page too. We should have at least the following:
1. Prominent Large Image pointing to the Themes Gallery (Think Drupal News Letter "Ad" on the front page of Drupal.org)
Perhaps links to themes hosted elsewhere. (offsite from drupal.org)
2. Themes Help area that lists the following links: - Basic Themes Help: http://drupal.org/node/39451 - Manage inconsistancy in themes: http://drupal.org/node/37156
3. IRC Channel This should simply mention the #drupal-themes irc channel on irc.freenode.net.
4. Mailing list info Info about this mailing list.
5. Other stuff...
...
I'm not sure who is the person that would or does have the permissions to do this. I would not mind doing it if Dries gave me access to the site to do it.
Thanks for your time, Trae
-- Dries Buytaert :: http://www.buytaert.net/
Yessir, we'll do that. :) Trae Dries Buytaert wrote:
It might be a good idea to come up with a generic mechanism to provide 'Relavant links' or 'Context-sensitive information' on drupal.org.
The obvious solution would be using blocks. We have 'information blocks' on http://drupal.org/cvs and handbook pages already.
So, +1 but take a moment or two to come up with a generic solution that can be standardized for different pages or sections of drupal.org.
On 20 Dec 2005, at 19:21, Trae McCombs wrote:
Dries, can you +1 this and Robin and myself will implement it. Thanks, Trae
--- Original email sent to themes@drupal.org ---
Hi all,
If you go to this page: http://drupal.org/support
You will see a variety of information for someone looking for support. However, if you go to the main Drupal Themes page, you are simply confronted with a bunch of themes to download.
I suggest we create a Launching page for the Main Themes page too. We should have at least the following:
1. Prominent Large Image pointing to the Themes Gallery (Think Drupal News Letter "Ad" on the front page of Drupal.org)
Perhaps links to themes hosted elsewhere. (offsite from drupal.org)
2. Themes Help area that lists the following links: - Basic Themes Help: http://drupal.org/node/39451 - Manage inconsistancy in themes: http://drupal.org/node/37156
3. IRC Channel This should simply mention the #drupal-themes irc channel on irc.freenode.net.
4. Mailing list info Info about this mailing list.
5. Other stuff...
...
I'm not sure who is the person that would or does have the permissions to do this. I would not mind doing it if Dries gave me access to the site to do it.
Thanks for your time, Trae
-- Dries Buytaert :: http://www.buytaert.net/
-- Trae "occy" McCombs || http://occy.net/ Founder - Themes.org // Linux.com CivicSpaceLabs - http://civicspacelabs.org/
Hmmm, this sounds like common need ... <moshe checks contrib ...> Contextlinks: http://drupal.org/project/contextlinks Whatsrelated: http://drupal.org/node/24307 Dries Buytaert wrote:
It might be a good idea to come up with a generic mechanism to provide 'Relavant links' or 'Context-sensitive information' on drupal.org.
The obvious solution would be using blocks. We have 'information blocks' on http://drupal.org/cvs and handbook pages already.
So, +1 but take a moment or two to come up with a generic solution that can be standardized for different pages or sections of drupal.org.
Op dinsdag 20 december 2005 22:42, schreef Moshe Weitzman:
Hmmm, this sounds like common need ...
Contextlinks: http://drupal.org/project/contextlinks Whatsrelated: http://drupal.org/node/24307
May I add http://drupal.org/node/24719 ? That is a general API for handling weblinks. It comes with great examples and all that. There is currenlt a lot of work done to get this ready for 4.7. *All Your Links Blong To Us* Also known as: just store them centrally via an API and let *any* module (yes, that includes aggregator.module AND profile.module) benefit from these links and code transparancy. Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]
There is also this: http://drupal.org/node/39822 On 12/20/05, Bèr Kessels <ber@webschuur.com> wrote:
Op dinsdag 20 december 2005 22:42, schreef Moshe Weitzman:
Hmmm, this sounds like common need ...
Contextlinks: http://drupal.org/project/contextlinks Whatsrelated: http://drupal.org/node/24307
May I add http://drupal.org/node/24719 ?
That is a general API for handling weblinks. It comes with great examples and all that. There is currenlt a lot of work done to get this ready for 4.7.
*All Your Links Blong To Us* Also known as: just store them centrally via an API and let *any* module (yes, that includes aggregator.module AND profile.module) benefit from these links and code transparancy.
Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]
Relatednodes isn't really well suited for this task. It is pretty bulletproof regarding various attacks -- it just figures out what nodes share the most taxonomy terms with the currently displayed node. I based it on AutoWitch's awTags related block, and obviously works best with free tagging vocabularies. That makes it great for bloggy and newsy sites that want to provide easy listings of 'similar stories,' but it makes it relatively expensive and cumbersome when trying to manually list static collections of 'related information' on nodes that are visited frequently but changed infrequently. --Jeff
-----Original Message----- From: Khalid B [mailto:kb@2bits.com] Sent: Tuesday, December 20, 2005 4:03 PM To: development@drupal.org Subject: Re: [development] Drupal Main Theme page - A Suggestion forImprovements
There is also this:
On 20 Dec 2005, at 22:58, Bèr Kessels wrote:
Contextlinks: http://drupal.org/project/contextlinks Whatsrelated: http://drupal.org/node/24307
May I add http://drupal.org/node/24719 ?
That is a general API for handling weblinks. It comes with great examples and all that. There is currenlt a lot of work done to get this ready for 4.7.
The (web)links module is in the too-much-overhead-and-complexity-for- a-simple-task camp. We just want to display some context sensitive information. That information can either be text, links or a combination of both. IMO, a simple block or block region -- maybe with some extra CSS -- should do the trick, and creates virtually no run-time or maintenance overhead. -- Dries Buytaert :: http://www.buytaert.net/
Op dinsdag 20 december 2005 23:30, schreef Dries Buytaert:
The (web)links module is in the too-much-overhead-and-complexity-for- a-simple-task camp.
You obviously misunderstand that project. Or so I hope. Weblink module != links links is really nothin more then a * standardised SQL table with a * general weblink api. (if it would be core it would be link.inc) Nothing more nothing less. Really! Now, all that 'cruft' around it, is there to please the audience. No-one buys a weblink_api.module. Its sad, but true. People do buy a 'weblinks-with-cool-javascript-to-post-your-links-like-delicious.module. Yes, that is sad. because this links project with a very simple bookmarklet does the same! You can build your own delicious, with drupal! We, the Drupal internals know this, but that person (loaded with funds) looking for 'the definite delicious killer' will not. But, that is a different story. That cruft includes a links_related.module (only 600 lines of PHP, for much much more funtionality than those two 'standalone' projects') which does what we want: "We just want to display some context sensitive information. That information can either be text, links or a combination of both." Yes, it does so in a block. Bèr -- PGP ber@webschuur.com http://www.webschuur.com/sites/webschuur.com/files/ber_webschuur.asc PGP berkessels@gmx.net http://www.webschuur.com/sites/webschuur.com/files/ber_gmx.asc
The (web)links module is in the too-much-overhead-and-complexity-for- a-simple-task camp.
You obviously misunderstand that project. Or so I hope.
While that project might make sense in other contexts that warrant the complexity, it does not make sense for a handful of links on drupal.org. -- Dries Buytaert :: http://www.buytaert.net/
Trae has given me the data for a block, so I'm working on that now. Robin On 12/20/05, Dries Buytaert <dries@buytaert.net> wrote:
On 20 Dec 2005, at 22:58, Bèr Kessels wrote:
Contextlinks: http://drupal.org/project/contextlinks Whatsrelated: http://drupal.org/node/24307
May I add http://drupal.org/node/24719 ?
That is a general API for handling weblinks. It comes with great examples and all that. There is currenlt a lot of work done to get this ready for 4.7.
The (web)links module is in the too-much-overhead-and-complexity-for- a-simple-task camp. We just want to display some context sensitive information. That information can either be text, links or a combination of both. IMO, a simple block or block region -- maybe with some extra CSS -- should do the trick, and creates virtually no run-time or maintenance overhead.
-- Dries Buytaert :: http://www.buytaert.net/
-- Merry CHRISTmas! Robin Monks, CSL Web Administrator robin@civicspacelabs.org
I've added a block, comments welcome. Robin On 12/20/05, Robin Monks <devlinks@gmail.com> wrote:
Trae has given me the data for a block, so I'm working on that now.
Robin
On 12/20/05, Dries Buytaert <dries@buytaert.net > wrote:
On 20 Dec 2005, at 22:58, Bèr Kessels wrote:
Contextlinks: http://drupal.org/project/contextlinks Whatsrelated: http://drupal.org/node/24307
May I add http://drupal.org/node/24719 ?
That is a general API for handling weblinks. It comes with great examples and all that. There is currenlt a lot of work done to get this ready for 4.7.
The (web)links module is in the too-much-overhead-and-complexity-for- a-simple-task camp. We just want to display some context sensitive information. That information can either be text, links or a combination of both. IMO, a simple block or block region -- maybe with some extra CSS -- should do the trick, and creates virtually no run-time or maintenance overhead.
-- Dries Buytaert :: http://www.buytaert.net/
-- Merry CHRISTmas! Robin Monks, CSL Web Administrator robin@civicspacelabs.org
-- Merry CHRISTmas! Robin Monks, CSL Web Administrator robin@civicspacelabs.org
On 12/20/05, Robin Monks <devlinks@gmail.com> wrote:
I've added a block, comments welcome.
Good work Robin. This was much needed. Comments: General rewording needed by someone who specializes in documentation, for consistency, tone, ...etc. For example: === You can * Get basic help on themes. * Find out how to handle theme differences. * View the theme developer's guide Selecting a base theme If you are looking for a simple fixed theme it is recommended that you start with BlueMarine, Box Grey or argeebee . More advanced themes are table-less, a good example of this is Friends Electric. CivicSpace has multliple layouts and styles to choose from, however it also has several browser specific fixes which can be difficult to work with. For support on themes, check the IRC channel #drupal-themes on freenode. You can also signup for the themes mailing list. === A link to the themes forums is also in order.
:/ it is kind of cramped but at least the information exists. I still say we should lay it out like I did here: http://civicspacelabs.org/home/drupalthemes Trae Robin Monks wrote:
I've added a block, comments welcome.
Robin
On 12/20/05, *Robin Monks* <devlinks@gmail.com <mailto:devlinks@gmail.com>> wrote:
Trae has given me the data for a block, so I'm working on that now.
Robin
On 12/20/05, *Dries Buytaert* <dries@buytaert.net <mailto:dries@buytaert.net>> wrote:
On 20 Dec 2005, at 22:58, Bèr Kessels wrote:
Contextlinks: http://drupal.org/project/contextlinks Whatsrelated: http://drupal.org/node/24307
May I add http://drupal.org/node/24719 ?
That is a general API for handling weblinks. It comes with great examples and all that. There is currenlt a lot of work done to get this ready for 4.7.
The (web)links module is in the too-much-overhead-and-complexity-for- a-simple-task camp. We just want to display some context sensitive information. That information can either be text, links or a combination of both. IMO, a simple block or block region -- maybe with some extra CSS -- should do the trick, and creates virtually no run-time or maintenance overhead.
-- Dries Buytaert :: http://www.buytaert.net/
-- Merry CHRISTmas! Robin Monks, CSL Web Administrator robin@civicspacelabs.org <mailto:robin@civicspacelabs.org>
-- Merry CHRISTmas! Robin Monks, CSL Web Administrator robin@civicspacelabs.org <mailto:robin@civicspacelabs.org>
-- Trae "occy" McCombs || http://occy.net/ Founder - Themes.org // Linux.com CivicSpaceLabs - http://civicspacelabs.org/
I still say we should lay it out like I did here:
This could be done through editing the description for the term "Themes" in the project vocabulary. Project.module outputs the description (at this point, the message "The contributed themes are not part of any official release...").
On 20 Dec 2005, at 22:42, Moshe Weitzman wrote:
<moshe checks contrib ...>
Contextlinks: http://drupal.org/project/contextlinks Whatsrelated: http://drupal.org/node/24307
- Contextlinks: + Works on node pages only? + Confuses the heck out of me. + Does not seems to escape its input on output. It looks vulnerable to XSS attacks, although I haven't tested it. - Whatsrelated: + Can link to nodes only? + Does not seems to escape its input on output. It looks vulnerable to XSS attacks, although I haven't tested it. + Does not work with HEAD. -- Dries Buytaert :: http://www.buytaert.net/
Dries Buytaert wrote:
- Whatsrelated: + Can link to nodes only?
Indeed. And renders only through phptemplate. Definitely a some-assembly-required module.
+ Does not seems to escape its input on output.
Well, that would be quite a serious bug if true, and one I'll definitely fix
+ Does not work with HEAD.
...and won't until after 4.7 release. jh (Whatsrelated's author)
participants (10)
-
Bèr Kessels -
Dries Buytaert -
Dries Buytaert -
Jeff Eaton -
John Handelaar -
Khalid B -
Moshe Weitzman -
Nedjo Rogers -
Robin Monks -
Trae McCombs