Build Your Own PHP Framework

Sign in Get started

This episode is for members only

Sign up to access "Build Your Own PHP Framework" right now.

Already a member? Sign in to continue

Playing

24. Page titles in Twig

Episodes

0%

Your progress

Total: 4h 45m
Played: 0m
Remaining: 4h 45m

Join or sign in to track your progress

01. Setting up

01. Introduction

02. Composer and PSR-4 Autoloading

03. Bootstrapping and structure

04. Error reporting with Ignition

02. Container

05. Using a container

06. Adding service providers

07. Autowiring with reflection

08. Refactoring to a singleton

03. Application config

09. Building the Config class

10. Reading and merging config files

11. Registering service providers through config

12. Using env files

04. Routing and controllers

13. Everything starts with requests

14. Adding routing

15. Responding in routes

16. Cleaning up responding

17. Defining routes in a separate file

18. Creating a controller

19. Using services inside controllers

05. Views

20. Installing Twig

21. Rendering a view

22. Debugging in Twig

23. Creating a base layout

24. Page titles in Twig

25. Creating a Twig config helper

06. Database

26. Setting up and querying the database

27. Working with models

28. Creating an example user profile page

07. Authentication

29. Setting up Sentinel

30. Creating the registration flow

31. Registering and authenticating a user

32. Showing authenticated state

34. Logging out

08. CSRF Protection

35. Protecting routes with CSRF

36. Adding tokens to forms

09. Flashing messages

37. Basic session flashing

38. Creating a Twig helper and flashing globally

10. Validation

39. Validating the login form

40. Manually adding validation errors

41. Validating the registration form

42. Custom validation rules

11. Middleware

43. How middleware works

44. Adding auth middleware and grouping routes

45. Persisting old form data

12. Exception handling

46. Creating an exception handler

47. Custom 404 (and other error) views

48. Rendering views for CSRF errors

13. Pagination

49. Paginating with Eloquent

50. Building a pagination view with Twig

14. Global helpers

51. Registering functions with PSR-4

52. Container resolution helper

53. View and config helpers

54. Route generator helper

Transcript

00:00

Let's recap by going through the entire flow of creating a new route, new controller and a new

00:05

view and then we'll look at changing over the page title depending on which page we're actually on. So to start with let's head over to our web routes and we'll create our new route in here for the user's dashboard. So let's create dashboard. Eventually we're going to be protecting this so the user can only access it when they're signed in but for now we'll just

00:25

register it as a plain route. Okay we need a controller here so why don't we head over to HTTP controllers. We could even grab the same structure as our home controller just to make life easier and let's create out a dashboard controller file in here, paste this in and of course just change over what we need. So let's call this dashboard controller. We don't need

00:49

our config for this but we do need the ability to render a view and in here we'll get rid of users and name and we'll just render out dashboard.twig which we'll create in just a second and we don't need any data to be passed down to here at least not yet so let's get rid of that as well. Okay over in our web routes we can now pull the namespace in for our dashboard controller so

01:10

let's pull that in and get rid of that and that's been pulled in just at the top here. Great. Okay so we have a route, we have a controller but we don't have a view. If we were to go over to our dashboard yeah sure enough we don't have dashboard.twig. Okay let's first of all add this to our navigation so I'm just going to create out another navigation item here which we'll be hiding when

01:34

the user isn't signed in so we can now click through to that directly from here. Okay all we need to do now is create out a new view so we could put this in a folder if we wanted to it doesn't really matter how we do this let's just create this out directly in here so dashboard.twig and paste this in let's go and just get rid of this and call this dashboard and we'll get rid of this as well. Okay

02:03

and we'll just say this is your dashboard. Okay brilliant so we're extending the base layout everything should look good like this. Perfect. Now we want to change over this page title here so how do we do that? Well we can use the same concept as a piece of content that we want to inject into a view so if we open up home.twig what we can do is as well as defining this block out

02:29

here we can also define a block in here for the title we're going to do this inline because we don't want any extra spacing so we'll end that block and we'll give the title in here and let's do the same thing for dashboard as well so let's pull this in and we'll call this dashboard. Okay so obviously this isn't enough on its own what we'll need to do is head over to our base layout

02:55

so layouts and app and we'll need to inject this into here under the condition that it actually exists. To do this we want to check if the block is actually defined first of all so let's use a if statement in twig and let's use the block helper here to grab the contents of the title block what we can then do is say is defined so if that block is defined we want to do something in here

03:19

we need to end that if here as well and this is where that content is going to go so what we can now do is just directly in here render out that title and let's go over and have a look there we go we've got home and we've got dashboard now what we could also do is onto the end of this add in the name of the app the overall name of the app and we'll change this up later when we create a

03:44

config helper specifically for twig to actually pull this out of our config but now though we know that we need to hard code it in so we'll look at changing this over later to do something like the following config get and then grab out any of the config that we need okay so we'll add no framework into here if the block is defined we'll add just a pipe at the end of this to separate

04:09

these two things out and now we have dashboard pipe no framework and home pipe no framework now if we don't have a block defined here that's fine because we're using an if statement so for example on the home page if you didn't want to specifically say home that's now just going to show the name of the app and on any of the other pages it will render out properly

Episode summary

In this episode, we walk through the whole flow of adding a new page in our app with a dynamic page title using Twig templates.

We start by setting up a new route for the user's dashboard, create a matching controller, and then build the dashboard view file. The goal is to have a basic but working page you can visit at something like /dashboard.

Next up, we add this new route to the navigation so it's easy to access, and then create the dashboard Twig file itself. At this point, everything works, but we notice the page title isn't updating—this is where things get interesting!

To fix the page title, we use Twig's block functionality to let each page set its own <title>. We define a title block inside each page template (like home.twig and dashboard.twig) and then modify our base layout (app.twig) to check if a title block is defined, and, if it is, render it in the <title> tag along with the app name (hardcoded for now). This means each page can control what appears in the browser tab.

At the end, we point out that soon, we'll make it even nicer by pulling the app name from our config using a Twig helper, but right now, we've got dynamic page titles set up and working. If a page doesn't define a title block, it just defaults to the app name. Nice and tidy!

Episode discussion

No comments, yet. Be the first!