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

MODX 3 - Include auto-configuration options in the installer: multilingual site, blog etc. #14364

Open
digitalpenguin opened this Issue Feb 11, 2019 · 14 comments

Comments

Projects
None yet
9 participants
@digitalpenguin
Copy link

digitalpenguin commented Feb 11, 2019

Feature request

Creating a new issue for this feature request that began while discussing issue #13876

Summary

It would be great if MODX 3 could include configuration options in the installer. These options would provide a richer starting point for developing a project with MODX. For example, if selected, a multi-lingual site could be configured automatically while MODX is installed. A similar concept to what the MultiLangSetup extra does. Or if a blog is needed, it could be configured automatically using the appropriate extras which would be downloaded during setup.

Why is it needed?

There is no one size fits all and that's especially true with how customizable MODX is. This is certainly one of it's main strengths. However, it can be daunting for newcomers to be presented with a blank slate. In addition, for MODX veterans it would be incredibly useful to have time-saving functions such as these.
I believe this would help to grow the community by making the first few steps more user friendly.

Suggested solution(s)

I propose this is added via configuration scripts in the MODX installer. Required extras for the various setups would be downloaded on demand. For example, a multilingual site might need Babel and LangRouter installed and then contexts/settings configured.
This change to the installer only adds extra options and if not selected, a blank MODX site would be installed exactly the way it is currently.

  • What do you, the community, think about the proposition?
  • If for it, what configuration setups should be included?
  • Which extras should be used for each option?

Related issue(s)/PR(s)

Related to issue #13876

@arsentver

This comment has been minimized.

Copy link

arsentver commented Feb 11, 2019

A very unambiguous topic, for newbies it may be relevant, but MODX as a whole is not for beginners.
For example, I do installation scripts on the MODX API for different tasks, one click and everything on a clean system is everything that is needed and configured as needed. If you make such a functional, then each preset must be carried out in the form of an interactive sequence of steps, as during the installation of the system, so that any user understands what will be changed and what will be installed, with the possibility to make adjustments at each step. Somewhere to disable the system settings that he does not need, somewhere to disable the package he does not need. And of course there must be a point - I'll set everything up myself.

@digitalpenguin

This comment has been minimized.

Copy link
Author

digitalpenguin commented Feb 11, 2019

@arsentver I think that's a bit more ambitious than what I was initially envisioning. Not to say I'm not open to the idea of an interactive questionnaire though..

My original thought was just to have basic presets that can be used or not. If you wanted to alter the configuration, you could do that post installation or just not not use the options at all.

@arsentver

This comment has been minimized.

Copy link

arsentver commented Feb 11, 2019

The idea of presets is good.
Just a vision of how, for example, a typical blog should be, all different. Therefore, step-by-step installation would be useful here. This will help to navigate the system settings and understand what components are recommended for the blog.

@iWatchYouFromAfar

This comment has been minimized.

Copy link

iWatchYouFromAfar commented Feb 11, 2019

I make websites on MODX with the help of some developments that I managed to adapt in a short time to my needs for this CMS. At the same time, I like the fact that initially the MODX are install completely naked, without settings and sub-settings. Pure CMS. And I don’t really want the MODX to be transformed from a small and pleasant for the development CMS into big and huge transformer.

On the otherside, such a setting can be added to the usual installation version of MODX, and the advanced one can be left as it is now. This will allow simple users to install (in example) blog in a few clicks. But then you need to write official packages for that.

@JonikUl

This comment has been minimized.

Copy link

JonikUl commented Feb 11, 2019

We have too many options, for example, a multilingual site can be made with:

  • Babel
  • LangRouter
  • Localizator
  • Multilangsetup
  • etc

Which option we must choose?

@digitalpenguin

This comment has been minimized.

Copy link
Author

digitalpenguin commented Feb 11, 2019

@iWatchYouFromAfar The presets would be completely opt-in during the install. If you don't select the option, MODX will install the same as now.

@JonikUI That's right, so we would make a decision on what the presets use.
For a multilingual site I would vote for Babel and LangRouter. Just the same as I did in MultiLangSetup: https://github.com/digitalpenguin/MultiLangSetup

@Ibochkarev

This comment has been minimized.

Copy link
Contributor

Ibochkarev commented Feb 11, 2019

I suggest we hear @Mark-H @opengeek @rthrash opinion on this request.
Next, determine the types of sites. and then determine what will go to all types of sites and individual types of sites from add-ons.
Well, to hear more opinions from our colleagues.

@JonikUl

This comment has been minimized.

Copy link

JonikUl commented Feb 11, 2019

Сonsole is always required for installation))

@iWatchYouFromAfar

This comment has been minimized.

Copy link

iWatchYouFromAfar commented Feb 11, 2019

@iWatchYouFromAfar The presets would be completely opt-in during the install. If you don't select the option, MODX will install the same as now.

Well, let's say. We make the installation itself harder on the one hand and simpler on the other. Components that will implement the functionality should be supported and developed "officially." Like for example Fred. Otherwise, this is not a serious approach.

More over, these components should be more friendly for not developers but for simple users. With good documentation and etc.

There are a lot of questions. But one of the main things, considering the delay in MODX 3 release, is it worth it? Maybe first we just need to do the third version?

@digitalpenguin

This comment has been minimized.

Copy link
Author

digitalpenguin commented Feb 11, 2019

I don't think they need to be special official extras. There can be a note during installation saying that if this preset is selected that 3rd party extras will be used. Agree or go back kind of thing.

In terms of making the extras themselves more user friendly for end users, sure I agree. But that could be done on a case by case basis and doesn't really need to be related to this feature itself. I see this as mainly targeting developers/designers new to MODX.

This doesn't need to delay the release of MODX 3 at all. If it looks to be too time consuming it could certainly be targeted at 3.1 for example.

@ruvizuri

This comment has been minimized.

Copy link

ruvizuri commented Feb 11, 2019

Maybe, it`s better to show a list of extras from official repositories, and combine extras into task groups.
For example:

  1. Blog (and below is a list of possible extras: pdotools, image+, migx...)
  2. Landing page (.....)
  3. Online Store (.....)

And give the user a choice: set the whole group or only part of the selected extras.

.+ pure CMS
.+ self-support extras
.+ flexible settings

@Mark-H

This comment has been minimized.

Copy link
Collaborator

Mark-H commented Feb 11, 2019

I've worked on this before, adding a step to the setup that allows you to install packages/starter sites: #13472

The reason that never made it into core is the critical question of what to propose people install. There simply is no blueprint that everyone can agree on how to build a site in MODX, and we need that before the setup can install them out of the box.

@Ruslan-Aleev

This comment has been minimized.

Copy link
Contributor

Ruslan-Aleev commented Feb 11, 2019

Maybe worth display a list of standard categories (menus, forms, galleries, etc.) with several components that you can mark and install (as now at https://modx.com/extras/)? Also add a search.
And collect the list of components from the rating https://modx.com/extras/
But yes, the question is not obvious.

@digitalpenguin

This comment has been minimized.

Copy link
Author

digitalpenguin commented Feb 12, 2019

@Mark-H That's fantastic!
I for one don't mind which Extras are used, as long as it works efficiently.
If it really was a problem e.g. pdoTools vs getResources/Wayfinder, then a selection can be provided with a simple explanation for new users.
For example:
This preset is built using extras from the community.
Please choose one:
getResources / getPage / Wayfinder - original official extras built by the core team.
pdoTools - a newer suite of tools built by Vasily, designed to be faster with some experimental features.

This kind of thing is clear and easy enough for a new user I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment