Skip to content

Comments

[DOCS] Add quick start chapter#886

Draft
gilbertsoft wants to merge 3 commits intobenjaminkott:masterfrom
gilbertsoft:quick-start
Draft

[DOCS] Add quick start chapter#886
gilbertsoft wants to merge 3 commits intobenjaminkott:masterfrom
gilbertsoft:quick-start

Conversation

@gilbertsoft
Copy link
Contributor

No description provided.

@gilbertsoft
Copy link
Contributor Author


.. code-block:: bash

ddev composer create "typo3/cms-base-distribution:^10" --no-install
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would avoid version numbers in documentation.

Copy link

@sypets sypets Mar 19, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like your approach very much, I am just not sure here is the right place for it.

This goes way beyond the bootstrap_package. Do you think it might be a good idea to add this to the official Installation Guide instead? I think that is where people would look for help on installing TYPO3 and I am not a huge fan of fragmented information in various places.

Disclaimer - I superficially looked at the content - I may have misjudged this.

I think this would need some structural decisions, but I have also been thinking for a while, if the building block approach in the installation guide is such a good idea or if it might be better to have one page full installation instructions for several typical usecases, e.g. with ddev / composer / bootstrap package, without composer etc. However I find it difficult to come up with a solution that does not have several pros and cons.

To illustrate this:

  1. building block approach: one page for each individual step, sometimes several options available, the reader must find his path through the steps (used currently)
  2. One page with one clear objective, e.g. install TYPO3 with DDEV, composer and introduction package. That would be more like your quickstart here.

Currently we have individual pages for various steps, e.g. install package, Admin tool. You are then walked through the various steps and often have something like, if you have Composer, do this next, otherwise do this etc.

What I am also missing in the official Installation guide are some steps which are strictly needed, such as site configuration.

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

Successfully merging this pull request may close these issues.

3 participants