DeployLog publishes changelogs, the running list of what changed in a product, for the things you ship. This chapter of the manual, the documentation set you are reading now, takes you from no account to a published first entry in about five minutes. It is the path, not the specification; chapter 13 holds the reference.
1. Sign up on the login page
Open the login page. There are two ways in.
"Continue with GitHub" signs you in directly. No confirmation mail is involved.
For email, fill in Email and Password, then use the "Don't have an account? Sign up" button under the form. The sign-up form submits exactly two values, your email and your password: no name, no password confirmation, no card.
The password field requires at least 8 characters. Type fewer and the field itself refuses the value, so the form never submits.
2. Confirm your address (email sign-up only)
Email sign-up sends you a link. Opening it confirms the address and gives the account its organization, the single workspace that owns your projects.
The browser then lands in the dashboard, the signed-in side of DeployLog, signed in. A first confirmation also sends the owner a welcome email.
A link that fails returns you to the login page.
3. Your organization
You get one organization, and you own it. The dashboard reads your projects through it, so everything you create on this path belongs there.
Organization settings and API keys are chapter 11.
4. Create a project
The create form has two fields. Project name is required. Website URL is optional, and blank means the project has no website.
There is no slug field. "Create Project" submits the form and lands you on the new project's page. "Cancel" takes you back to the page you came from.
5. Slugs
The slug, the short name that identifies a project in URLs, is derived from the project name. Slugs are global across all of DeployLog, not just your organization.
If the slug your name produces is already taken, a number is appended: -2, then -3, and so on until one is free. If the numbering runs out of free candidates, the project is not created and you get back "Could not generate a unique URL for this project name. Try a different name." Pick a different name and submit again.
The name and the website URL can be changed later. The slug never can.
6. Write the first entry
From the project page, write your first entry, one dated item in the project's changelog, the public list of what you shipped.
Publishing puts the entry on the public changelog at deploylog.dev/p/<slug>/changelog.
Writing, editing and publishing entries are chapter 02.
The free plan on this path
The free plan allows 3 projects. No card is asked for anywhere on this path.
At three projects the dashboard stops showing the "New Project" button and shows an upgrade prompt in its place. A fourth project is refused with the message "Free plan is limited to 3 projects. Upgrade to create more."
Plans and billing are chapter 12.
The dashboard
The dashboard lists your projects newest first. Each card shows the project name and its /slug.
Before you create anything, the dashboard shows "No projects yet", the line "Create your first project to start publishing changelogs.", and a "Create Project" button.