DeployLog publishes changelogs, the running list of what changed in a product, for the things you ship. Sign-up to a live entry takes about five minutes. Here is the whole path.
1. Sign up on the login page
There is no separate sign-up page. The login page has one email field and one password field, and both "Sign in" and "Don't have an account? Sign up" use the values you typed there. Sign-up asks for nothing else: no name, no password confirmation, no card.
The password field asks for at least 8 characters. That is the field's own requirement, and the field will not submit a shorter value. Leave the email or the password empty and the sign-up button does nothing at all.
Prefer GitHub? Press "Continue with GitHub". That route signs you in directly and never involves a confirmation mail.
2. Confirm your address (email sign-up only)
Email sign-up sends a confirmation mail. The link in it does two things: it confirms your address, and it gives your account its organization. Your browser then lands in the dashboard, the signed-in side of DeployLog, signed in. If the link fails, you are returned to the login page.
3. Your organization
An organization is the account-level owner of your projects. Chapter 11 covers the organization's settings and API keys. You never create it, name it or pick it. It appears automatically at your first confirmed sign-in, one per account, and every project you create belongs to it.
4. Create a project
A fresh dashboard shows one thing: "Create your first project to start publishing changelogs." Press the button and you get the create form.
The form states what it is for: "A project represents a product or service you want to publish changelogs for."
It has two fields and no more:
- Project name, required.
- Website URL, optional. Give a full URL or leave it blank. Blank means none.
There is no slug field. "Cancel" takes you back to the page you came from.
5. Slugs
A slug is the URL name of your project, built from the project name, unique across all of DeployLog, and fixed for life. You do not type it. It appears on the project card as /slug once the project exists.
Slugs being global means a name someone else already uses is not rejected. A taken slug gets a number added to it (-2, -3, and so on) until a free one turns up. The one exception: if every candidate is taken, the form comes back with "Could not generate a unique URL for this project name. Try a different name."
The name and the website URL can be changed later. The slug never can.
6. Write the first entry
Creating a project opens that project's page. That page, not the dashboard, is where you write your first entry, meaning one item in the changelog. Chapter 02 covers writing, editing and publishing entries. The editor asks for a title and a body, and Publish puts the entry on your public changelog at deploylog.dev/p/<slug>/changelog.
The free plan on this path
No card is involved anywhere above. The free plan allows 3 projects. Chapter 12 covers plans and billing. Once you have 3, the dashboard hides the "New Project" button and shows an upgrade prompt in its place. The limit also holds at creation time: a fourth project is refused, with a message telling you the free plan is limited to 3 projects.
The dashboard
Projects are listed newest first. Each card shows the project name and its /slug, and opens that project.