addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgoogleimageimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Re: [dfwPython] DFW Python URL reorg

From: Sheila A.
Sent on: Sunday, August 14, 2011 5:11 PM
On Sun, Aug 14, 2011 at 4:49 PM, Ralph Green <[address removed]> wrote:
On Sun,[masked] at 12:01 -0500, Brad Allen wrote:
>     http://dfwpython.blogspot.com/
>
> I propose that we make the DFW Python blog site the main front page
> for our
> group, because I think it's very easy to manage,  and has important
> functionality needed for a front page (links, live feeds, blog posts,
> etc.).
>
Howdy,
 I think this is a bad idea for several reasons.  The proposed site is
a blog, and not really good for displaying the most important
information about the group.  The dominant part of the screen is taken
up by these blog posts, which are listed purely chronologically.  So,
important posts will float down the lists to obscurity.  I have nother
against having such a blog, but I don't think it should be the first
thing people see.

The Blogger platform has a lot more functionality than a blog, and provides the ability to create pages with arbitrary content .For example, see the tabs across the top of the PyTexas site, such as <http://pytexas.blogspot.com/p/prizes.html>. This page has no chronologic content.  

Also, note that rich sidebar, header, and footer content can be made globally available across the site.
 
 These posts have the disadvantage of being controlled by one person.
For example, on a wiki, I would have edited this last entry to note that
there was a second presentation.  I won't make a separate entry for that
talk, because it was much smaller than the primary talk and does not
deserve the same weight as the first talk.

Well, it might be worth a second entry. After all, that blog post was a review. Others can be granted permission to edit the blog and add content and edit the site design. 
 
 A wiki, such as we have for dfwpython.org is much more flexible.  I
agree that the current appearance of dfwpython.org is a little
unappealing, but the wiki software used is very flexible and we can make
it better.

Nobody has done so in the past five years of its existence. In fact, very few people ever edit the wiki site. I do sometimes, once in a blue moon, just to fix the occasional glaringly outdated nugget of misinformation.
 
 I can't think of any way in which the blogspot site is easier to
manage.  It does look better, but it is harder to manage than our
current wiki.  Please explain, because I may just not understand your
claim here.

The blogspot site provides a rich set of GUI tools for designing and laying out web pages, and allows the introduction of gadgets of varying functionality which can be placed anywhere on the page.
 
 The current wiki is under our control, which is a plus for me.  Google
may provide backups, but they will never care about the site as much as
the current webmaster.

True, we lack the means to modify or review the code of the underlying Blogger software platform. However, in this case, I don't think that's where our true interests lie. We are more interested managing and presenting the content of the site.  

The truth of this claim is evident, in that attempts at building a DFW Python web application site ("Project Mongoose") have floundered. Meanwhile, much of the functionality requested for that site has been built in one day (today) on http://dfwpython.blogspot.com.



Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy