Student checklists
Copy the list you need into your notes and tick it off.
Contents
- Before your first session
- A study site that is ready
- Every study session
- Before you hand in a project
- Before a pull request
- Before a presentation
- Before you buy the Student level
Before your first session
- To do: I chose a learning path (Choosing a learning path).
- To do: I started a study journal (Keeping a study journal).
- To do: I have PHP 8.0 or newer (PHP 7.4 usable without support) and Composer, or I start with the public demo (Your first site: three ways).
- To do: I have a password manager for the passwords the installer prints.
A study site that is ready
- To do:
php bin/php/console --versionworks and the release is in my journal. - To do: The site answers at its address, and I signed in to the administration.
- To do: I changed the administrator password and deleted
var/log/initial-admin-password(Installing a study site in one command). - To do: Test accounts use addresses at
example.invalid. - To do: I know how to back it up and rebuild it (Resetting and rebuilding your study site).
- To do: It is on my own computer or a training machine, never a live site.
Every study session
- To do: One goal, written down before I start.
- To do: Read a section, do it, compare with "Expected" (How to study with the help).
- To do: When something differs: log, cache, siteaccess (Reading logs and errors).
- To do: Journal entry written; work committed; nothing secret committed.
Before you hand in a project
- To do: Every task done, or the report says why not.
- To do: Every project check answered with evidence (Grading your own work).
- To do: No core file edited; overrides,
.ini.append.phpfiles and extensions only. - To do: Every printed value in templates escaped.
- To do: No passwords, keys,
settings/override/orkickstart.iniin the repository or screenshots. - To do: Only invented content; no personal data.
- To do: The release named; the pages used cited.
- To do: Self review done a day later (Grading your own work).
Before a pull request
- To do: The task is small and real (Your first contribution, step by step).
- To do: I searched the tracker for an existing issue.
- To do: Work is on a branch; the commit subject starts with
Added:,Updated:,Fixed:,Removed:orRenamed:. - To do: For the kernel:
make hooksinstalled,share/filelist.md5current, CLA signed (The CLA for students). - To do: The description says what, why and how I tested it.
- To do: I am ready for review rounds and will squash and rebase when asked.
Before a presentation
- To do: The study site runs; a backup is ready in case it does not.
- To do: No password or key on screen; the browser shows no saved logins or private tabs.
- To do: Demo data only.
- To do: If I show a public demo, I know its content may change or be reset (Trying the public demo).
- To do: I name the release and use the right names: Exponential, 7x, the Exponential Foundation (Names and history for learners).
Before you buy the Student level
- To do: I read The Student partner level and the live program pages.
- To do: I compared it with what is free (Student level or free community: what to choose).
- To do: I asked the partner team what "sandbox access" includes.
- To do: I understand the order: apply, review, pay, then sign (How to apply).
- To do: I know it is not a certification, and that official certifications are planned but not available yet (Certifications and certificates).
Related pages
- Student FAQ
- Student reading path
- Trainer toolkit
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.