Jump to content

Search the Community

Showing results for tags 'community'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • Login Register Pro
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 5 results

  1. From the recent discussion about the roadmap & wishlist for 2021 and some other posts by @ryan, it comes to my mind that developing and coordinating the whole project for one person is becoming harder and harder and leads nearly to the reverse of expanding the ProcessWire ecoysystem. This is not against Ryan, i think everyone here knows how engaged he is about ProcessWire, but he has only 24/7 (sometimes i think he's got far more than that...). We as the community could support the project (financially) to relieve Ryan and could take over some tasks from him. This could be, but is not limited, to: Building a Foundation/Association/Company to ensure the persistence of the project and to fund the work put in ProcessWire of Ryan (and others). Nearly every other CMSs i checked has something like this (Drupal Association, Typo3 Association, Joomla Foundation, Wordpress Foundation, Contao Association, ...). This also puts more trust in the project, if someone new will check on his engagement in ProcessWire. Assigning persons/teams to work on things: Extending the core (when necessary) Developing and maintaining major modules (e.g. page builder, admin themes, internationalization, marketing, ecommerce system, ...) Testing and inspection of modules developed by others Making translations of modules (translation of the core is mostly covered, i think) Working on PRs & issues submitted on github Working on the homepage Coordinating the community efforts I know, some resorts are already covered by others (e.g. @Pete for the forum, @horst for images, ... ), but there are many other areas where this ist not the case. By joined efforts by the ProcessWire community this hopefully will also attract new developers to the system and by a growing number of users this assists in the things above in a circular process. What do you think?
  2. Hi all. First of all, I want to thank you all who blessed us with this great CMS. I have done 20+ sites with this and I'm very happy. I love the API. In case anyone is interested in using Discord to chat and talk about ProcessWire, I made server for us. Discord is a free voice and text chat app designed specifically for gaming, but it's very good for our kind of communities too. Chatting is similar to IRC, voice is similar to TeamSpeak or Mumble, and there will be coming new features like video chatting. Also chance to use notifications when someone talking in a specific channel, but the server's default is only notified when mentioned. There can be multiple channels in one server; general, help, devtalk, security, specific languages. All can be public or accessed by only for a certain role. And if you're not there, let's say for five days, you can still search or read things what people have talked since you were there last time (if mod did not purge that channel). Windows and Mac clients are very good ones, but Linux is still in beta. And of course, there is webchat too. More information about Discord can be found here: https://discordapp.com/ Of course, all the ProcessWire developers can get moderator access to the server. Forums are, of course, very good place to discuss things (and I have found many answers from here), but that is not real time and getting the answers you need can take a lot of time here. People want to get their answers faster, right now, so that’s why Discord can be a very good way to grow our community. Think about it. Invite link to server
  3. Hi, it seems to me there are some PW-users in Germany, but is there a community site in progress? I am using ExpressionEngine for 5 years now. I did several client projects but had difficulties to "sell" EE to clients. ProcessWire could be my next main-CMS. At the moment I rebuild some of my old sites with ProcessWire. Yesterday I talked to a web agency about PW. They said "Well, PW seems to be great but it's unknown in Germany. We do have work for WordPress, Contao or Joomla." I showed them http://webkrauts.de/artikel/2012/processwire but their reaction was like "Ok, nice. But can you do the next project with Contao or WordPress? Because our clients heard about these CMS before." ExpressionEngine has similiar problems in Germany, but costs money. I worked on a german Community-site für ExpressionEngine, but then EllisLab changed their pricing structure and philosophy. So I'm leaving EE and there will probably never a german EE-site. But what's about a german Community site? Is anybody working on this or would like to participate? -Thomas
  4. Lately I’ve been building a little script for a local journalist who manages a open Google Docs spreadsheet where Swiss journalists can enter there social media data like Twitter names etc. The script updates a Twitter list with the collected Twitter names in the spreadsheet, means it gets the document feed through Google Docs API and updates the list through Twitter API. Long story short I’ve been dealing with the oauth authentication mechanism. I started thinking about creating a module for PW to connect user accounts with oauth providers like Twitter. Could be helpful in more community focussed projects.
  5. Hello, I am in the early evaluation stage for PW. Coming from the Drupal 7 world and not being a software developer but coming from the design-side, these are my main goals for a new project: design ...is everything: The normal webpages need to be as flexible as possible to design whereas is ok in the community area to have a more standard layout. PW is PERFECT for me, Drupal has limits (even with modules), a main reason for my unhappiness (and yes, I know how to make my own templates) Organization:I am making a brochure style Webpage, PW is perfect here. (Drupal plays it's role when having millions of pages, which needs different organizations, like automatic menus, Taxonomy, views. Developing speed. Drupal needs 10000000+ clicks for installation. And for every new project the same mess again. PW can be adapted easily. Membership fun (forums, galleries, friending): Drupal is good, PW has nothing like that E-Commerce: Drupal has unfinished stuff, PW nothing. I don't blame PW for its limitation with membership management and E-Commerce. Those limitation is also a strenght and beauty because PW is not feature-overloaded and easy to handle. (A reason for me to have arrived here!) And there are pefect solutions for that existing already, like the IP_Board and Magento. I am now thinking of combining the specialists in it's fields like PW and IP_Board to have the best of both worlds that would by far more manageable than Drupal with its modules. What about using the fine grained Bulletin Board membership membership management and use this to access users to PW content (and editors and admins to the PW backend). Isn't it easier to write a "bridge" module than adding membership features to PW and trying to re-invent the wheel? The IP_Board has a strong API for authentification. (This site is also using the IP_Board.) Which means that users register and login to the board to have access to PW privileges also (through synchronizing the user base or bypassing the PW auth). That would be perfectly bypassing the PW limit of not having a fine grained frontend user (users level1,2,3) and backend users (editors, admins). (I a same way e-commerce functionality could be added with another auth-"bridge".) Is there something in PW (a module?) I have overlooked that does this already? Otherwise I would like to post this here as a starting point for ideas and discussion. Thanks for reading all this. I am very curious about your opinions. Cheers Carl from Berlin
×
×
  • Create New...