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

Plan initial functionality #1

Open
KorvinSzanto opened this issue Mar 1, 2017 · 5 comments
Open

Plan initial functionality #1

KorvinSzanto opened this issue Mar 1, 2017 · 5 comments
Milestone

Comments

@KorvinSzanto
Copy link
Contributor

The broad stroke list is:

  1. Globally installed
  2. Manages concrete5 instances v7+
  3. Imports commands from the concrete5 instance
  4. Has most or all of the features of the current core CLI tool
@KorvinSzanto KorvinSzanto added this to the v1.0 milestone Mar 1, 2017
@KorvinSzanto
Copy link
Contributor Author

In order to draw in users and provide a value above the current CLI implementation, we should have the ability to generate specific working structures like Blocks, Themes and Packages within a concrete5 site.

c5 packages:stub:create
c5 blocks:stub:create
c5 themes:stub:create

Should we try to support this in v1? or is this a feature we should release in 1.1?

@matt9mg
Copy link

matt9mg commented Mar 2, 2017

I think for version 1 having a vanilla just install the c5 app and prompt for basic install creds should be enough for v1 :)

@matt9mg
Copy link

matt9mg commented Mar 2, 2017

Was just wondering when you do c5 install would be a good thing if we could run

c5 install v5.7 c5 install v5.8 or if just c5 install which gets the latest version of c5 by default.

I'm quite a big fan of the symfony installer

What do you think?

@KorvinSzanto
Copy link
Contributor Author

KorvinSzanto commented Mar 2, 2017 via email

@matt9mg
Copy link

matt9mg commented Mar 3, 2017

Sweet I didn't realise when you download C5 with composer it would also run the installation.

Well in that case I've asked around a handfull of developers and it seems that for v1 they are all saying the same thing.

  • Create a PageType
  • Create a Template
  • Create a User
  • Create a PageType Controller
  • Create a Theme
  • Create a Block
  • Create a Theme
  • Create a single page

Going along with your suggestions above create stubs for those is a great idea.

I think for v2 you could extend the above where more prompts would be asked such as generate ORM in package or DB.xml

What do you think about the above?

mlocati added a commit to mlocati/cli that referenced this issue Dec 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants