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

ENDOC-433 First pass at reformatting #441

Merged
merged 5 commits into from
Mar 3, 2022
Merged

ENDOC-433 First pass at reformatting #441

merged 5 commits into from
Mar 3, 2022

Conversation

Lyd1aCla1r3
Copy link
Contributor

No description provided.

Copy link
Collaborator

@jyunmitch jyunmitch left a comment

Choose a reason for hiding this comment

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

sorry ahead of time, lots of comments on this one, probably from previous experience with with it

``` sh
ent check-env develop
```

### Manual Setup
The `ent jhipster` command is the recommended way to generate microservices and micro frontends but you can also setup JHipster and the Entando Blueprint yourself. You should then use the `jhipster` command instead of `ent jhipster` for the tutorial.
We recommend using the `ent jhipster` command to generate microservices and micro frontends, but you can also run the following commands to initialize JHipster and the Entando Blueprint. If you choose the manual setup, replace all instances of `ent jhipster` in this tutorial with the `jhipster` command.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I am very confused. If these are the manual steps, why didn't all the commands come with jhipster instead of ent jhipster so I don't have to replace them?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

so the manual steps header is ### and under prereqs; the prerequisite for not using the cli is to fire off the commands that follow, which are the jhipster and ent installs. if you go the manual route then any "ent jhipster" you encounter when you get to the actual tutorial should be replaced with "jhipster"

Copy link
Collaborator

Choose a reason for hiding this comment

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

I think the instructions were always confusing and I never knew which are the manual steps.

I think the issue is that the reference point keeps changing...the header says manual setup>> first sentence starts with recommended, so that must be the manual setup. But second part of that sentence says you can also do something else, is that the alternative or the manual steps? Because of the structure of these sentences, it is rather confusing, especially at this point when there could be several ways of doing things and one doesn't know that.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

hm. i think the best remediation is to be very explicit to clear up any confusion. i'll make the language more explicit.

@@ -38,76 +39,85 @@ npm install -g [email protected]
```

## Generate the Project
Whether you elect to use the `ent jhipster` command or perform a manual setup, the next step is to create a project with microservices.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I am still thinking this is part of the manual setup and am still confused if I am following the manual setup or not. I can't go further because I can't figure out if I am supposed to change ent jhipster to just jhipster or not.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

no... manual setup was a ### header below prereqs. generate the project is the start of the tutorial. you can go further! the disclaimer indicates that - whether or not you chose to use the cli this is the next step

Copy link
Collaborator

Choose a reason for hiding this comment

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

I think if the manual setup paragraph was clearer, this would be fine.

- `Would you like to install other generators from the JHipster Marketplace?` (No)

4. Next, add an Entity to your microservice and create the corresponding Micro Frontends. For the tutorial, `Conference` is the name of the entity that will be added to the application.
3. You'll be presented with a series of prompts to configure your project. These are listed below, with the base values for this tutorial in parentheses. Except where noted in **bold**, you can input what works best for you. Note that hitting "Enter" will select the default option.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think the last sentence deserves being in bold, because it is an important point and I remember thinking that was useful when I went through this several times.

'base values' >> is default values more clear?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

no, base values are the values selected for this tutorial. they are not always the default values.

i actually think it's kind of awkward to bold that... that's like you're recommending to use the default, which is not necessarily the case. and if you just hit enter without thinking then you don't input required information in some cases

Copy link
Collaborator

Choose a reason for hiding this comment

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

Got it! Not a big deal. I guess I was thinking it eases the process

- `As you are running in a microservice architecture, on which port would like your server to run? It should be unique to avoid port conflicts.` (8081)
- `What is your default Java package name?` (Up to you)
- `Which *type* of database would you like to use?` (SQL)
- If no database is selected you'll be building a stateless microservice, which is a valid choice, but the rest of this tutorial won't work.
Copy link
Collaborator

Choose a reason for hiding this comment

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

If no database is selected, you'll be building a stateless microservice which is a valid choice, but the rest of this tutorial won't work. >> moved comma, which reads better, I think.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i think there needs to be a comma between microservice and which; "which is a valid choice" is an aside

- `Would you like to use Maven or Gradle for building the backend?` (**Maven**) <-- this is required for Entando
- `Which other technologies would you like to use?` (**Don't select any other technologies**)
- `What name would you give to the bundle to share on an Entando digital-exchange?` (Up to you)
- `Which is the organization name to use when publishing the docker image?` (**Enter the name of the organization where you are going to push your Docker image. If you're using your personal Docker hub account enter your username.**) <-- this can be changed later as needed
Copy link
Collaborator

Choose a reason for hiding this comment

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

should this start with 'What organization'? I read this a couple of times because I kept thinking there was a list of choices that I was supposed to know about or had preentered

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yeah i totally left the text in all the questions untouched, because this is what you actually get when you run the code. it should be tweaked in many cases...

- `Do you want to generate micro frontends?` (Up to you)

- At this point the blueprint will generate controllers, repositories, services, and micro frontends for your entity.
- `Overwrite src/main/resources/config/liquibase/master.xml?` When prompted with a conflict at this stage, enter `a` for "All." This will override existing files with the configuration changes needed for your new entity.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I always wanted this point to be bolded because I did not notice this until going through this tutorial a couple of times or more. My bad but I can't be the only one who glosses over steps that are not totally required.:)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

lol we must punish them for the oversight! jk - i had already started approving overwrites before i read this, too :P i'll draw attention

* ```/bundle``` is used to assemble the project code into an Entando bundle.
* ```/src/main/docker``` contains Docker files to help with local development environments.
* ```/src/main/java``` and ```src/main/resources``` contain the microservice codebase and configuration.
* ```/ui``` holds the React-based micro frontends. By default, each entity is allocated an MFE for details, form, and table.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is there one MFE or multiple? It also sounds like there could be multiple entities in this tutorial, is that right? Doesn't it get generated? >>"by default, an MFE is generated for each entity to display details, form, and table."

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i have the same question. i left the language as is because it could go either way, but i was also wondering... @nshaw i feel like we're talking about 3 MFEs here

* ```/src/main/docker``` contains Docker files to help with local development environments.
* ```/src/main/java``` and ```src/main/resources``` contain the microservice codebase and configuration.
* ```/ui``` holds the React-based micro frontends. By default, each entity is allocated an MFE for details, form, and table.
* ```/bundle``` is used to assemble the project code into an Entando Bundle.

## Next Steps
You now have a choice:
Copy link
Collaborator

Choose a reason for hiding this comment

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

this reads kind of fatalistic? Maybe 'Congratulations on ... then now you can choose between these ...'

Copy link
Contributor Author

Choose a reason for hiding this comment

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

LOL it's the matrix all over again. i didn't care enough to change it? but yeah i'll rephrase to make it seem a little less dire

- [Learn about the key elements included in the Blueprint generated widgets](../../../docs/create/blueprint-features.md)
- [Iterate on your data model using the JHipster Domain Language (JDL)](./update-data-model.md)

- [Build your Entando Bundle](../pb/publish-project-bundle.md) and deploy your microservice and micro frontends to the Entando Component Repository
Copy link
Collaborator

Choose a reason for hiding this comment

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

How about "Build and Deploy your Entando bundle to the Entando ..." because this makes it sound like deploying it will be a separate step. Another confusing thing is that a bundle is not really a bundle since the MS and MFE are deployed separately.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@jyunmitch "a bundle is not really a bundle"?? please rephrase?

Copy link
Collaborator

Choose a reason for hiding this comment

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

After you brought this up and Nathan clarified it, it all makes sense. But if it is a bundle, they should stay together when deployed but sadly they don't. Nothing is wrong about the verbiage. I just noticed it always says it this way, 'deploy your mfe and ms...' and in thinking about it, it makes sense.

- [Iterate on your data model using the JHipster Domain Language (JDL)](./update-data-model.md)

- [Build your Entando Bundle](../pb/publish-project-bundle.md) and deploy your microservice and micro frontends to the Entando Component Repository
- Folow the [Running Locally tutorial](./run-local.md) to run your microservice and micro frontends in your local dev environment
Copy link
Collaborator

Choose a reason for hiding this comment

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

the title for the page is now 'Run Blueprint-generated Microservices and Micro Frontends in Dev Mode' >> this is too long but the link reference should somewhat match?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

agreed - i will be totally honest; i did not check this link! i'll go through the others, too

@nshaw
Copy link
Member

nshaw commented Mar 2, 2022

@Lyd1aCla1r3 you have two approvals but I saw a new comment from you. Will leave this one to you to merge when you're ready or to tag us for one more review.

@nshaw nshaw merged commit 465e5ae into main Mar 3, 2022
@nshaw nshaw deleted the ENDOC-433 branch March 3, 2022 18:55
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