As we wrap up the Jobeet tutorial, let's have another look at the framework. Forget Jobeet for an hour, and recall all the features you learned during the last three weeks.
Today, we will see what need to be done before going to production, what kind of deploying strategies you can use, and also the tools you need for a successful deployment.
Today, we will talk about the HTML cache. To improve your website performance, you can cache whole HTML pages or just parts of them.
As announced at the beginning of the Jobeet tutorial, we are holding a design contest today. The goal is to choose the default design used by Jobeet.
Today, we will talk about plugins: what they are, what you can bundle in a plugin, and what they can be used for.
Today, we will talk about Jobeet internationalization (or i18n) and localization (or l10n).
Today, to enhance the responsiveness of the search engine, we will take advantage of AJAX to convert the search engine to a live one.
Two days ago, we added some feeds to keep Jobeet users up-to-date with new job posts. Today, we will continue to improve the user experience by implementing the latest main feature of the Jobeet website: the search engine.
When you post a job, you will want to have the greatest exposure possible. If your job is syndicated on a lot of small websites, you will have a better chance to find the right person. That's the power of the long tail. Affiliates will be able to publish the latest posted jobs on their websites thanks to the web services we will develop today.
If you are looking for a job, you will probably want to be informed as soon as a new job is posted. And it is not very convenient to check the website every other hour. To keep our Jobeet users up-to-date, we will add several job feeds today.
With the description of the symfony User class yesterday, we have now finished our tour of the fundamental features of symfony. You still need to learn a lot but you should already be able to create simple symfony projects all by yourself.
Today, we will discover how symfony manages persistent data between HTTP requests.
Today, thanks to the admin generator functionality of symfony, we will develop a complete backend interface for Jobeet in just one hour.
Yesterday we created our first form with symfony. People are now able to post a new job on Jobeet but we ran out of time before we could add some tests. That's what we will do today. Along the way, we will also learn more about the form framework.
The second week of Jobeet got off to a flying start with the introduction of the symfony test framework. We will continue today with the form framework.
Today, we will write functional tests for the features we have already implemented in the job and category modules.
Today, we will start talking about something completely different: automated tests.
Follow the Jobeet 24 day tutorial using Doctrine!
I hope you worked on the Jobeet category page as today's tutorial will then be much more valuable for you.
Today, we will enhance the Jobeet website by tweaking the code here and there. In the process, you will learn more about all the features we have introduced this week.
We started publishing the Jobeet tutorial five days ago, and the first feedbacks have been very encouraging.
Today we will dive into the wonderful world of the symfony routing framework.
Today, we are going to customize the basic job module we created yesterday.
Those of you itching to open your text editor and lay down some PHP will be happy to know today's tutorial will get us into some development.
Tutorial demonstrating how to setup a simple registration form for the sfDoctrineGuardPlugin.
Today, we will take the time to describe the requirements of the Jobeet project with some basic mockups.
Today I am happy to introduce the first official piece of documentation for symfony and Doctrine.
Read the first day of the symfony tutorial.
You will need to read the full blog post to know what Jobeet is...