Plone has very good workflow for publishing pages and other information it is very easy to change how can create and approve the pages before publishing.
You talk about hebrew content - there is nothing in Hebrew right now so what are the plans? because if it is going to be Hebrew site or English site? It is very important to know that for the website design Can you write more what you mean by spam that people write? > pls see my comments inline. > > tks, > Amit > > On 5/9/06, David Siedband <[EMAIL PROTECTED]> wrote: > >> > Well, I know that there few open source projects maintained/created by >> > Israel developers. >> > May be python.org.il can contain references + small description to >> > those projects? >> > Thus it will promote the use of those projects in industry. >> >> I think that the potential of this site is really its ability to help >> grow the community and that Roman's suggestions are pointing to this. >> This site can be much more than a place to post documentation. >> >> It could include >> >> Directories of People >> Directories of Organizations/Companies >> Job Postings >> Community Calendar >> Listing of Projects >> Photo Gallery > Good idea - I'll try to remember bringing a camera next time... > >> Archive of presentations and hand outs >> Tutorials >> Glossary >> RSS feeds of each section > > I'd be happy if we'd get to a point where this is needed. Currently a > single feed would be enough (or maybe 2 - one for site updates, and > one for meetings section) > >> A CMS is really needed to do these things well. >> >> >> It all seems very nice, but unfortunately our current problem is >> >> generating contents, not how to manage it. >> >> Having content-types (like 'person', 'organization', 'project', etc.) >> also gives people ideas of things to add to the site. When people see >> other listings they naturally want to add themselves, their >> organization, etc. > > Did not have big success with this approach with current pages > e.g. the "Projects" or the "Python-IL Logo" page. > (both have big links to them from the main wiki page, but it seems > people did not notice so did not contribute) > May if the site had a more "shiny" look it would be better... > >> >> > * An easy way to edit the content >> >> Because Plone includes the web-based visual editor Kupu, the barriers >> to contribute are lower, there is no new wiki-syntax to learn. People >> can add content with tools that look familiar to them. example: >> http://plone.org/documentation/whatsnew/2.1/images/kupu.png >> >> > * Easy to join and contribute - login should be optional >> > * Automatic spam protection, because we don't have time to clean our >> > site >> >> I think that these two go together and that people should have to login >> to publish on the site. Requiring login to publish/comment combines >> with Plone's workflow process to prevent spam very well. >> > > 1) In the current system you already have to login to edit wiki pages. > This does not help much, because it seems like the spamming-scripts > already know how to automaticly create new mediawiki logins. > Fortunately for me, our mediawiki is enhanced by the efficient > spam-fighting utility called Shlomi Fish ;-) > > 2) Note that having to create a login for editing pages is a great > barrier by itself. > (and far worse if you have to wait for email confirmation, which might > sometimes take more than an hour) > You can't really expect an occasional reader who stumbled upon our > site to add her comments/corrections/links/typo-fixes if she has to > create a special account and password for that. > We are *NOT* the only editable site on the web, and most people > nowadays tend to be a bit (too) paranoid and would avoid having to > "keep track" of which sites they have passwords for. > > 3) My suggestion: > > Anonymous (not logged in) users can edit pages after getting a (time > limited) cookie from > a "verifycation" page using captcha Images ( > http://en.wikipedia.org/wiki/Captcha ) - note: it does not have to > contain any other input fields - no login needed. > Also - "major"/"main" pages are reserved for logged-in edits only > (to protect from vandalism). > Note that this should mostly solve both (1) and (2) above. > > If such a system is not already available, it should not be too hard > to implement, especially in a python-driven CMS. > >> > * We may create some content about Python (e.g tutorials) >> >> With Plone those can be illustrated html tutorials that can be made >> without them people having to code any html (visual editor, above...) >> >> > * Complete Hebrew support >> > * Good support for left to right section within right to left page >> > (e.g include code in a hebrew page) >> > > Note that it is widely agreed here that we should keep most of the > contents Hebrew, and only create English versions for "important" > pages, or per request by readers. > (It should probably apply to this list too. But I'm still replying in > English to English mails) > > Sticking to Hebrew was discussed and agreed on a few times, but we > still have a lot of English contents on the wiki, which need to be > translated. > >> Plone has very strong hebrew translations and RTL support, thanks to >> the hard work of Ofer and others. >> >> I have developed Plone archetypes for many of the content-types above >> which I will be glad to share, and I will volunteer to help customize >> them as help with any other Plone work as needed. >> >> I think that if we have a shared understanding of how this will help >> support and grow the community, then we will be able to convince an >> organization in Israel to help sponsor us for Plone hosting. >> >> kind regards >> -- >> David >> > Thanks all of you for your suggestions. > > Regards, > Amit >
