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

Create getting started guide #836

Merged

Conversation

alexandra-simeonova
Copy link
Contributor

Description

Changes proposed in this pull request:

  • Create getting started guide

Related issue(s)
See also #766

@alexandra-simeonova alexandra-simeonova added this to the Sprint 6 milestone Sep 17, 2019
@alexandra-simeonova alexandra-simeonova added the documentation documentation tasks label Sep 17, 2019
@alexandra-simeonova alexandra-simeonova added WIP Work in progress and removed WIP Work in progress labels Sep 18, 2019
@zarkosimic zarkosimic self-assigned this Sep 19, 2019
Copy link
Contributor

@zarkosimic zarkosimic left a comment

Choose a reason for hiding this comment

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

LGTM! 👍

Copy link
Contributor

@JohannesDoberer JohannesDoberer left a comment

Choose a reason for hiding this comment

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

👍

@JohannesDoberer JohannesDoberer self-assigned this Oct 1, 2019
Copy link
Contributor

@bszwarc bszwarc left a comment

Choose a reason for hiding this comment

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

Added comments :)

docs/getting-started.md Outdated Show resolved Hide resolved
docs/getting-started.md Outdated Show resolved Hide resolved
Micro frontends are small frontend web applications that are implemented on one global user interface. They allow you to:

* **break up big, monolithic UIs**: decompose your frontend into smaller chucks and make it more manageable, all while maintaining a consistent user experience.
* **give individual teams autonomy**: every team in your project can develop their own end-to-end application which exists on the same core app. This gives teams full autonomy over release dates and updates, while also reducing code dependencies.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
* **give individual teams autonomy**: every team in your project can develop their own end-to-end application which exists on the same core app. This gives teams full autonomy over release dates and updates, while also reducing code dependencies.
* **give autonomy to individual teams**: every team in your project can develop their own end-to-end implementation based on the same core application. This gives teams full autonomy over release dates and updates, at the same time reducing code dependencies.

I would go with end-to-end implementation more than application - but it might be a preference :D

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You're right, because otherwise we repeat "application" twice in the same sentence. 😃

I'm not sure about This gives teams full autonomy over release dates and updates, at the same time reducing code dependencies. There should be a word like "while" somewhere (a subordinating conjunction) because "at the same time reducing code dependencies" isn't a standalone sentence.
Maybe just This gives teams full autonomy over release dates and updates, and at the same time reduces code dependencies.
Or This gives teams full autonomy over release dates and updates, while at the same time reducing code dependencies.?

Copy link
Contributor

Choose a reason for hiding this comment

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

You are right - I like the second one :) 👍

docs/getting-started.md Outdated Show resolved Hide resolved
docs/getting-started.md Outdated Show resolved Hide resolved

## Prerequisites

All you need to get started with Luigi is basic knowledge of HTML and JavaScript.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
All you need to get started with Luigi is basic knowledge of HTML and JavaScript.
All you need to get started with Luigi is the basic knowledge of HTML and JavaScript.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Since "knowledge" is an uncountable noun, I don't think it needs an article 😕

Copy link
Contributor

Choose a reason for hiding this comment

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

👍


### Luigi Core

To create a global user interface and host a full web application in Luigi:
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
To create a global user interface and host a full web application in Luigi:
Follow these steps to create a global user interface and host a full web application in Luigi:

We usually add an introductory line about the steps to follow :) It doesn't need to be "follow these steps" can be something similar. However, in this case, we have 2 steps - Setting up a Luigi core app + Reading docu. since the introduction says: To create a global user interface and host a full web application in Luigi: I was wondering if we may be more direct in the second step. For example, we can have:
2. Configure the application. To do so, use the Luigi Core documentation. OR
2. Use the Luigi Core documentation to configure your application.

To create a global user interface and host a full web application in Luigi:

1. [Set up a Luigi Core application](https://github.com/SAP/luigi/blob/master/docs/application-setup.md).
2. [Read the Luigi Core documentation](https://github.com/SAP/luigi/blob/master/docs/README.md#luigi-core).
Copy link
Contributor

Choose a reason for hiding this comment

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

See comment above ⬆️


### Luigi Client

To develop micro frontends and connect them to an already existing Luigi Core app:
Copy link
Contributor

Choose a reason for hiding this comment

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

Same as above, maybe we can be more specific in the second point :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks! I made these changes in the latest commit.

alexandra-simeonova and others added 6 commits October 4, 2019 13:31
Co-Authored-By: Barbara Szwarc <barbara.m.szwarc@gmail.com>
Co-Authored-By: Barbara Szwarc <barbara.m.szwarc@gmail.com>
Co-Authored-By: Barbara Szwarc <barbara.m.szwarc@gmail.com>
Co-Authored-By: Barbara Szwarc <barbara.m.szwarc@gmail.com>
Co-Authored-By: Barbara Szwarc <barbara.m.szwarc@gmail.com>
Micro frontends are small frontend web applications that are implemented on one global user interface. They allow you to:

* **break up big, monolithic UIs**: decompose your frontend into smaller chucks and make it more manageable, all while maintaining a consistent user experience.
* **give individual teams autonomy**: every team in your project can develop their own end-to-end application which exists on the same core app. This gives teams full autonomy over release dates and updates, while also reducing code dependencies.
Copy link
Contributor

Choose a reason for hiding this comment

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

You are right - I like the second one :) 👍


## Prerequisites

All you need to get started with Luigi is basic knowledge of HTML and JavaScript.
Copy link
Contributor

Choose a reason for hiding this comment

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

👍

@JohannesDoberer JohannesDoberer modified the milestones: Sprint 6, Sprint 7 Oct 14, 2019
@alexandra-simeonova alexandra-simeonova merged commit 5131c65 into SAP:master Oct 15, 2019
@alexandra-simeonova alexandra-simeonova deleted the getting-started-guide branch October 15, 2019 13:00
stanleychh pushed a commit to stanleychh/luigi that referenced this pull request Dec 30, 2021
Create getting started guide for Luigi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation documentation tasks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants