Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New setup screen and process for blog installation #3072

Closed
ErisDS opened this issue Jun 24, 2014 · 1 comment · Fixed by #3102
Closed

New setup screen and process for blog installation #3072

ErisDS opened this issue Jun 24, 2014 · 1 comment · Fixed by #3102
Assignees
Labels
affects:admin Anything relating to Ghost Admin

Comments

@ErisDS
Copy link
Member

ErisDS commented Jun 24, 2014

Replacing the old issue: #1794


first-run

  • When installing Ghost / setting up the first user, Ghost should redirect to /ghost/setup/ instead of /ghost/signup/.
  • The setup screen should look like the above screenshot. Pre-styled markup for the screen exists here: https://github.com/TryGhost/Ghost/blob/master/core/client/html/setup.html
  • The setup process has 'blog title' which is additional to the old signup process. This will need validating and wiring up to get saved on the server side.
  • On the server side, the blog.description should be automatically set to: "Thoughts, stories and ideas by [user.name]"
  • Everything else should work exactly as per the old signup screen, the user should be created and automatically logged in, the welcome email should be sent, etc.

Question: should the setup be posted to an admin route, or do we need to move this onto the API? I'd say leave it as an admin route for now.

Note: the routes mentioned assume the ember admin is now the default, but that doesn't have to be done first.

@ErisDS ErisDS added this to the 0.5 Multi-user milestone Jun 24, 2014
halfdan added a commit to halfdan/Ghost that referenced this issue Jun 26, 2014
fixes TryGhost#3072
- Change router to handle /ember/setup/
- Adjust doSignup to also handle setup
- Adjust tests and add new where necessary
- Add setup controller, setup validation, setup route
- Adjust casper emberSetup to handle new setup
@sebgie
Copy link
Contributor

sebgie commented Jun 27, 2014

I'm sorry, and I hate when this happens but I have missed this question:

Question: should the setup be posted to an admin route, or do we need to move this onto the API? I'd say leave it as an admin route for now.

Yes it should be moved to the API. By the time we have finished the ember admin the admin controller should ideally consist of only a single controller for the index page to load the Ember client. All other actions are going to target the API.

When all this work is finished it will be theoretically possible to serve the Ember admin from a simple web server and all necessary data is fetched from the API.

I'll open an issues for that. The change is mostly for consistency and not urgent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects:admin Anything relating to Ghost Admin
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants