Jump to content

Search the Community

Showing results for tags 'wiki'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 4 results

  1. Does anyone see that the wiki pages doesn't work for them either? I click any link that goes to the wiki and I get this : http://wiki.processwire.com/index.php/Module_Creation If someone could help me out or tell me what's going on with the wiki that would be great.
  2. Hi, I'm hammering out the details of a project for a consortium of counseling organizations. They need a new site for sharing private case information and related knowledge, and they have a very small budget. My question is: Is this site a good fit for ProcessWire, or should I build this using a Wiki engine like MediaWiki or DokuWiki? Or something else? Here are some of the requirements: The site is access-protected so that only authorized accounts can see any site content at all—approximately 20 active users at a given time. Content types: The majority of content would be informational articles in formatted text, but the site will give them easy control over a dynamic, hierarchical category list under which content can be easily organized. They will also need to upload and link to documents, including PDFs and Word docs. All content, including uploaded files, would be available only to logged-in user accounts. Multiple editors: Users can update text, create new pages, add categories, and upload and link documents. All users would have editor privileges, but they anticipate fewer than 10 will actually do it. Recent updates: They want a section that lists recent substantial updates to the site. Based on the discussion, they prefer not to include minor article edits (like a phrase being changed to bold, for example), but only edits that change the content in substance—sounds like this could easily be accomplished with an internal blog. Alerts: Any member can post a comment on an article to note current questions or issues about the content. The purpose is to resolve the questions or issues and improve the article content, not to maintain a persistent discussion about article content. Full-text search Quick navigation: A concise list of links to highest-traffic content will be available on every page. This navigation menu should be easy to add, remove, sort, or edit links by the editors. I have two further requirements, for my own sake: Simplicity of user-facing interface: I don't want the publishing software to present the editors with superfluous configuration and options they might use to break the site, or require extensive documentation for. Stablility, security, and ease of maintenance: I don't want to introduce security vulnerabilities or create long-term maintenance difficulties simply by customizing the front-end page designs. It occurs to me that Wiki software has most of the above features built-in. But I have a few misgivings about using a Wiki: Wikis include a lot of built-in functionality that I imagine would make it incredibly complex to create a skin. I know that ProcessWire would allow me to write my own markup, and keep the page designs as simple as possible. I'm also afraid that I might introduce security vulnerabilities or maintainability problems if I create my own skin for a Wiki. I know that ProcessWire enables you to include back-end functionality in front-end templates, but you don't have to do that. I'm confident that I would have to do some obvious and deliberately reckless design in order to create any security problems with ProcessWire. On the other hand, I don't want to spend weeks building out functionality that a Wiki, or other easily-available software, offers with basic installation. Any guidance, warnings, advice, or further thoughts would be greatly appreciated. Cheers! John
  3. Hello to all Processwire people, i'm from Spain, migrating from drupal to PW, looking for something less PHP memory heavy (yes, still there are servers with less than 32MB of PHP memory). And for now, quite happy with it, flexible, fast, friendly and fun. But one thing a did not found easily was a starting guide or something like that (till now, just discovered wiki.processwire.com), so my question is, ¿why there is no link to it in any of the main pages? and for a basic website tutorial? The videos are nice but they mostly show a couple of functions and characteristics. By no means i'm trying to rant, be picky, annoy or start a flame war; just the thought about newcomers like myself, looking into a new CMS and not finding a direct link to the wiki or basic tutorial. Best regards.
  4. Joss

    Processwire Wiki

    I have just dipped my toe into the large space that is the ProcessWire wiki. At the moment, that just means that I have just logged on and am just creating a couple of templates and some other bits and pieces - nothing complicated, I don't have enough time! Once I have done that, I will start scribbling. For the moment, all I have done is a half complete help page about starting a new article (click on help in the left navigation), and created two categories - Drafts and Pending. Hopefully this will help with anything anyone writes which they want to flag up as not finished or need checking. More info on the help page. Talking of categories - if someone has any good ideas about what categories should be created and how they should be organised - that would be really useful! Joss. (PS: If anyone needs a logon for the Wiki, please ask Ryan, not me!)
  • Create New...