Jump to content

Beginners Guide to Processwire


tarang9211
 Share

Recommended Posts

1.

2.

3. http://processwire.com/api/

Take a basic installation local and have a look at the basic-site profile templates as a example.

Try to get a HTML Template working in PW like in the first 2 videos and make next steps....i'm actually running trow this, too ;)

Processwire is great and the main thing is the concept of creating content.....reading form a other threat:

There is a rough translation between traditional terms and ProcessWire's, which is:

Templates = tables

Fields = columns

Pages = rows

Best Regards mr-fan (Tip the search in this forum isn't that best use google + site: search instead....)

  • Like 5
Link to comment
Share on other sites

no framework or layers like smarty but a blank canvas with a power api - everything is "a page"

http://processwire.com/talk/topic/2296-confused-by-pages/

http://processwire.com/talk/topic/5667-help-a-noob-get-started/page-2#entry55820

+> with processwire total freedom.

start here => https://processwire.com/talk/topic/4173-grouped-forum-posts-links-articles-tutorials-code-snippets/

avoid repeated beginners questions by first starting to dig categories in community support.

Lots of helpful members in the forum.

Welcome.

  • Like 1
Link to comment
Share on other sites

In response to this snippet:

There is a rough translation between traditional terms and ProcessWire's, which is:

 

Templates = tables

Fields = columns

Pages = rows

 

I checked my database, and the fields were created as a table. This is confusing. I am not sure of the terms because of that. I was told that a table is a template, buy myphpadmin revealed that a field was a table

Link to comment
Share on other sites

I checked my database, and the fields were created as a table. This is confusing. I am not sure of the terms because of that. I was told that a table is a template, buy myphpadmin revealed that a field was a table

You're right. Each field requires a table of it's own. "Templates = tables" is figurative speech -- that's just roughly how they function from the developers point of view.

The main point here is that each template is a collection of fields and in this way resembles table in database. Each page is connected to one template, and thus that template defines what data this particular page can store, and that's also why some people prefer to think that "pages = rows".

Does this make any more sense to you?

One noteworthy difference from database concept is that each field can belong to multiple templates. This is done so that fields with identical configurations (such as "body" field with same tools) can be used in many templates without having to add and configure new field for each template.

As a side note, most developers using ProcessWire never dive into the real database structure. You don't have to do that to work effectively with ProcessWire. Don't get stuck at those things since that's something that the system handles for you (and, in fact, it's never recommended to perform direct SQL operations on existing tables).

  • Like 6
Link to comment
Share on other sites

  • 2 weeks later...

greetings guys nice to see you here....there is also a bootstrap site for a demo usage and a addon kind a menuhelper!

http://modules.processwire.com/modules/process-wire-bootstrap3/

http://modules.processwire.com/modules/markup-simple-navigation/

this addon is very similar to showmenu2() function in WB!

Great to see some more WB heros here ;)

best regards mr-fan

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...