Jump to content
anderson

beginer questions?

Recommended Posts

Hi all,

I'm a new to website building. Learned some CRASH course of js,jquery,php. Then I found CMS. Still learning around forum, youtube....

Anyway, please help me with some beginer questions:

1, About template - please correct me if I understand wrong : every page should be (or recommended) built on a template. So if in total I'll have 10 pages, 2 of them have same layout, I'll need 9 templates.  And, what fields a page includes, is not defined in page, but defined in the template that page uses. 

2,  Where to see what modules I've installed? is it in "Modules - Site"? 

3, I installed "PageTable Extended", then what?  As in a youtube tutorial, it should appear in Setup tab, but it doesn't.  What's in there: templates,fields,logs,comments. (I installed "Uikit 3 site_blog profile".)

4, I did a search in Processwire website for the famous "repeater matrix" module, and can not find it, there's a Repeater, as well as a Matrix. Is it not a module?

5, I watched this youtube tuts: https://www.youtube.com/watch?v=IHqnLQy9R1A

Anybody familiar with this tuts please help: 

After he analysed a target webpage layout he wanted to mimic, he created some fields, some template, then based on those he created a page and input some "content" in there, then clicked "view", it's just some text. So, here comes my question, he copied a folder "assets" (subfolders are: css,fonts,js,img) over, then the page have the appearance/layout he wanted to mimic. Where does that assets folder come from?

Appreciate any help.

Share this post


Link to post
Share on other sites

Hi @anderson and welcome to ProcessWire

In answer to your questions:

1. Short answer is yes, if you have 10 pages of which 2 have the same layout, then you will need 9 templates. HOWEVER, I recommend you read up on "Regions" and delayed output. You can have the _main.php template with all the common elements eg the header and footer, then you only need templates for the bits that are different, eg the page body. Alternatively, you can include  files such as header.php and footer.php into each page template file.

2. Yes, Modules - Site (or other tabs on that page)

3. "PageTableExtended" is an Inputfield module. Create a new field and assign it as type PageTableExtended then add it to your template(s)

4. There is a core fieldtype called "Repeater". This is not installed by default. You can install it from Modules - Core. 'Repeater' is a prerequisite of the commercial module, "ProFields" https://processwire.com/store/pro-fields/ which includes a number of fieldtypes including 'Repeater Matrix'.

5. The '/site/assets' folder is automatically created on the web server when you install ProcessWire. It's used by PW for all sorts of stuff and you can add your own files/folders if you wish. Typically you would access it with FTP or similar. It's not visible in admin area by design and a good place to store files you don't want to change

  • Like 2

Share this post


Link to post
Share on other sites
30 minutes ago, psy said:

Hi @anderson and welcome to ProcessWire

In answer to your questions:

1. Short answer is yes, if you have 10 pages of which 2 have the same layout, then you will need 9 templates. HOWEVER, I recommend you read up on "Regions" and delayed output. You can have the _main.php template with all the common elements eg the header and footer, then you only need templates for the bits that are different, eg the page body. Alternatively, you can include  files such as header.php and footer.php into each page template file.

2. Yes, Modules - Site (or other tabs on that page)

3. "PageTableExtended" is an Inputfield module. Create a new field and assign it as type PageTableExtended then add it to your template(s)

4. There is a core fieldtype called "Repeater". This is not installed by default. You can install it from Modules - Core. 'Repeater' is a prerequisite of the commercial module, "ProFields" https://processwire.com/store/pro-fields/ which includes a number of fieldtypes including 'Repeater Matrix'.

5. The 'assets' folder is automatically created on the web server when you install ProcessWire. It's used by PW for all sorts of stuff and you can add your own files/folders if you wish. Typically you would access it with FTP or similar. It's not visible in admin area by design and a good place to store files you don't want to change

WOW, thanks so much for your detailed help!

  • Like 1

Share this post


Link to post
Share on other sites

Hi @anderson 

I also started ProcessWire with this video. A must to do for a beginner.

 

About the asset folder containing images, css and js, this folder come from the free theme that you have to downloaded there : https://templatemag.com/demo/Spot/ (this is the theme the author is using to build the final website).

Once extracted, you can find the assets folder and it should be placed in the folder site/templates of your ProcessWire installation - along your templates - then you can continue to follow the tutorial. Do not mix this assets folder (which could be renamed of whatever you want, eg: mythemeassets) and the assets folder in site/assets which is a core "required" folder created by ProcessWire.

 

Good luck, you are on the good road ! 💪

On the same road you can pick that 

 

 

Edited by flydev
links
  • Like 2

Share this post


Link to post
Share on other sites
5 minutes ago, flydev said:

Hi @anderson 

I also started ProcessWire with this video. A must to do for a beginner.

 

About the asset folder containing images, css and js, this folder come from the free theme that you have to downloaded there : https://templatemag.com/demo/Spot/ (this is the theme the author is using to build the final website).

Once extracted, you can find the assets folder and it should be placed in the folder site/templates of your ProcessWire installation - along your templates - then you can continue to follow the tutorial. Do not mix this assets folder (which could be renamed of whatever you want, eg: mythemeassets) and the assets folder in site/assets which is a core "required" folder created by ProcessWire.

 

Good luck, you are on the good road ! 💪

Thank you, sir.

Share this post


Link to post
Share on other sites
10 minutes ago, flydev said:

Once extracted, you can find the assets folder and it should be placed in the folder site/templates of your ProcessWire installation - along your templates - then you can continue to follow the tutorial. Do not mix this assets folder (which could be renamed of whatever you want, eg: mythemeassets) and the assets folder in site/assets which is a core "required" folder created by ProcessWire.

Gotta love ProcessWire... it's so flexible. You can put stuff where it works best for you. I prefer to create a folder for my original HTML theme in site/assets. That way I know it's always going to be clean, then any changes/overrides go in site/templates. Whatever works for you 😉

  • Like 1

Share this post


Link to post
Share on other sites

true, I should must have specified that 😉

I just wanted to be sure he do not mix the 'assets' of the video and the the created one by PW by placing the 'assets' in the 'assets' folder hihi 

  • Like 1

Share this post


Link to post
Share on other sites
56 minutes ago, flydev said:

On the same road you can pick that 

 

 

You guys are so nice, first day I begin to love this place.

And exactly, this video tuts I was watching is from your post!

At the end of that thread, @Kiwi Chris talked about Bootstrap. I only heard about bootstrap, is it mainly about fitting PC,tablet and cellphone screen? If so, I am very interested, I could start my site base on that. Any bootstrap template/theme/profile recommendation? ---- my site will be a very simple one for a friend for his personal business, just like a business card.

Share this post


Link to post
Share on other sites
55 minutes ago, psy said:

Gotta love ProcessWire... it's so flexible. You can put stuff where it works best for you. I prefer to create a folder for my original HTML theme in site/assets. That way I know it's always going to be clean, then any changes/overrides go in site/templates. Whatever works for you 😉

I'll learn.

And thanks again, I appreciate it.  Though I know nothing about coding, I'm good at photography photoshop, if you guys need anything, just ask.

Share this post


Link to post
Share on other sites

Yes, Bootstrap https://getbootstrap.com/, Zurb Foundation https://foundation.zurb.com/ & UiKit https://getuikit.com/ are good places to start if you're unfamiliar with responsive websites. Actually, even if you are, they can save you a lot coding time.

ThemeForest is a good place to start.

I often buy a license for Canvas, https://themeforest.net/item/canvas-the-multipurpose-html5-template/9228123 which is based on Bootstrap, then place all the files in site/assets and as mentioned previously, use overrides/changes in site/templates.

ProcessWire uses UiKit3 as it's default responsive admin theme

 

  • Like 1

Share this post


Link to post
Share on other sites
2 minutes ago, psy said:

Yes, Bootstrap https://getbootstrap.com/, Zurb Foundation https://foundation.zurb.com/ & UiKit https://getuikit.com/ are good places to start if you're unfamiliar with responsive websites. Actually, even if you are, they can save you a lot coding time.

ThemeForest is a good place to start.

I often buy a license for Canvas, https://themeforest.net/item/canvas-the-multipurpose-html5-template/9228123 which is based on Bootstrap, then place all the files in site/assets and as mentioned previously, use overrides/changes in site/templates.

ProcessWire uses UiKit3 as it's default responsive admin theme

 

OK.

UiKit3? already on it. 

  • Like 1

Share this post


Link to post
Share on other sites

Hi @anderson,

welcome to the forum! If you want to learn and improve this is a great place to be. ProcessWire is a little different to other CMSs, meaning it is a LOT more flexible, but it is also a little bit more "complicated". In other words: It is more tailored towards the needs of developers and not people who want a quick&dirty click-click-done website.

Did you already do (and I mean DO, not READ 😉 ) the hello world tutorial? https://processwire.com/docs/tutorials/hello-worlds/

If you are looking for a good dev environment I'd recommend https://laragon.org/ (you need apache for PW) and https://code.visualstudio.com/.

Have fun!

  • Like 1

Share this post


Link to post
Share on other sites

@anderson

What the amazingly talented PW dev @bernhard said is true, especially the bit about it being different to point-n-click website builders.

Keep in mind that ProcessWire offers so much more on so many levels. Whether you want to get into module development or not is up to you. See the showcase for examples:

1. A landing page site of mine that used a number of custom & pro modules, including Repeater Matrix 

 

2. A landing page site from another PW dev that used nothing but core modules 

 

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites
1 hour ago, bernhard said:

Hi @anderson,

welcome to the forum! If you want to learn and improve this is a great place to be. ProcessWire is a little different to other CMSs, meaning it is a LOT more flexible, but it is also a little bit more "complicated". In other words: It is more tailored towards the needs of developers and not people who want a quick&dirty click-click-done website.

Did you already do (and I mean DO, not READ 😉 ) the hello world tutorial? https://processwire.com/docs/tutorials/hello-worlds/

If you are looking for a good dev environment I'd recommend https://laragon.org/ (you need apache for PW) and https://code.visualstudio.com/.

Have fun!

Thank you,sir.

hello world tuts?  not yet, I'll do it.

dev environment?  Great! That's the next question I plan to ask.

I appreciate your help.

  • Like 1

Share this post


Link to post
Share on other sites
59 minutes ago, psy said:

@anderson

What the amazingly talented PW dev @bernhard said is true, especially the bit about it being different to point-n-click website builders.

Keep in mind that ProcessWire offers so much more on so many levels. Whether you want to get into module development or not is up to you. See the showcase for examples:

1. A landing page site of mine that used a number of custom & pro modules, including Repeater Matrix 

 

2. A landing page site from another PW dev that used nothing but core modules 

 

Beautiful! I'll try to learn.

  • Like 1

Share this post


Link to post
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

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By bernhard
      --- Please use RockFinder3 ---
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
    • By MoritzLost
      Sorry for the convoluted title. I have a problem with Process modules that define a custom page using the page key through getModuleInfo (as demonstrated in this excellent tutorial by @bernhard). Those pages are created automatically when the module is installed. The problem is that the title of the page only gets set in the current language. That's not a problem if the current language (language of the superuser who is installing the module) is the default language; if it isn't, the Process page is missing a title in the default language. This has the very awkward effect that a user using the backend in the default language (or any other language) will see an empty entry in the setup menu:

      This screenshot comes from my Cache Control module which includes a Process page. Now I realize the description sounds obscure, but for us it's a common setup: We a multiple bilingual sites where the default language is German and the second language is English. While the clients use the CMS in German, as a developer I prefer the English interface, so whenever I install a Process module I get this problem.
      As a module author, is there a way to handle this situation? I guess it would be possible to use post-installation hooks or create the pages manually, but I very much prefer the declarative approach. The page title is already translatable (through the __ function), but of course at the time of installation there is no translation, and as far as I'm aware it's not possible to ship translations with a module so they are used automatically. Could this situation be handled better in the core? I would prefer if the module installation process would always set the title of the Process page in the default language, instead of the language of the current user.
×
×
  • Create New...