Some starting questions

[Peter Knight]

Hi folks

Wondered if anyone could answer the following questions. Just a pointer in the right direction would be a great help.

Rich text Editor

Maybe I'm spolit from using Redactor on my other CMSs but I hate Tiny MCE. Any plans to bring redactor to PW?

User submitted content

Is it possible to have a public facing webform. A user can submit content which is confined to certain fields. That content would then create an unpublished page for me to approve /edit and make live?

Ideally I'd like to be able to specify in the form under which "section" a new page would be created.

Manager

Are there any plans to redesign the Manager, give it a facelift and maybe build it within Bootstrap 3 or some responsive framowork?

Thanks guys.

[adrian]

Hi Sparrow,

There is a module for using CKEditor instead of TinyMCE:

http://modules.processwire.com/modules/inputfield-ckeditor/

It also has an inline mode which you might prefer.

Also, take a look at this:

http://modules.processwire.com/modules/inline-editor/

It is not production ready, but might give you some ideas of what is possible.

You can get Ryan's form builder module:

http://modules.processwire.com/modules/form-builder/

or look at some of these posts to build it yourself:

http://processwire.com/talk/topic/2089-create-simple-forms-using-api/

Why not try some of the admin themes - there are some really great options in there:

http://modules.processwire.com/categories/admin-theme/

[Peter Knight]

Thanks Adrian.
Looking at them now.

>>>It also has an inline mode which you might prefer.

Meaning I can add API calls directly into the Text Editor? 

[adrian]

Inline mode: http://ckeditor.com/demo#inline

[BUCKHORN]

Inline mode means ckeditor isn't loaded until a user clicks into the textarea. After doing so, the ckeditor toolbar is loaded and the textarea is changed to a rte. This is more efficient than say having 4 standard ckeditor RTEs on one page all loading at the same time.

[MatthewSchenker]

Greetings Sparrow,

A lot of what you say is a great way to use ProcessWire.  I'll address your questions on front-end forms (user submitted data).  I've been building a lot of ProcessWire sites with front-end forms.  In fact, the more I work the more I do this.  (I'm working now to package these activities into functions).

With front-end forms, there are two major ways to set up your fields:

1. Call ProcessWire "inputfields"

2. Use HTML form fields

Adrian gave you a link to a great post from Soma about the first method.

I've done most of my work using the second method.  I posted something a while back on doing this, which you can find here:

http://processwire.com/talk/topic/3105-create-pages-with-file-upload-field-via-api/

Take a look at all this, then follow up with specific questions on your needs.

Thanks,

Matthew

[Peter Knight]

Hi guys and Matthew. Thanks for the follow up. It's great to know that the PW community is so helpful. Looking at that link now

[MatthewSchenker]

Greetings,

Sparrow: doing front-end work is great and ProcessWire allows for really nice custom elements.

Keep in mind that there are multiple goals here:

1. Enter the material via forms (as discussed above)

2. Editing and/or deleting existing pages

3. Checking for existing pages when creating and/or editing to prevent two pages with the same title/name

4. Different page views depending on user roles (can consolidate certain views with actions mentioned in step 2)

This is fairly standard app development stuff, of course.  The point is, ProcessWire makes it pretty easy to implement.  You just need to focus on each part, one at a time.

Follow up with questions on particular parts and you'll get answers!

Thanks,

Matthew