amplication/amplication#6605

If the 'User' entity was deleted by the user it can be restored by:
Option 1 - Creating a new entity named 'User'
Option 2 - Installing the core Auth plugin - amplication/amplication#6304

I think we can have a short page/section that explains we support SSO
and mentioning its part of the Enterprise plan

Single Sign-On (SSO) Support for Amplication Accounts
Amplication understands the significance of a streamlined login process for your organization's members. To enhance the security and convenience of accessing your Amplication account, we offer Single Sign-On (SSO) support.

What is Single Sign-On (SSO)?
Single Sign-On (SSO) is an authentication process that enables users to access multiple applications or services with a single set of credentials. This means that you won't need to remember multiple passwords or log in repeatedly to different services within your organization's ecosystem. Once authenticated via SSO, you will gain access to all the connected services without the need for additional logins.

Who Can Use SSO with Amplication?
SSO integration for Amplication accounts is exclusively available to our Enterprise plan users. By choosing our Enterprise plan, your organization can benefit from streamlined access to Amplication through your preferred SSO provider, ensuring both convenience and security.

How to Enable SSO for Your Amplication Account
To enable Single Sign-On (SSO) for your Amplication account:

1. Contact Us for an Upgrade: If you're interested in using the SSO feature, please reach out to us to upgrade your account to the Enterprise Plan.
2. Setup & Integration: Once your account is upgraded, our team will handle the SSO setup and integration for you.
   It's as simple as that! We're here to ensure a smooth and hassle-free experience for our Enterprise users.

For any questions or additional support, feel free to reach out to our dedicated team.

amplication/amplication#6195

amplication/amplication#5406

Step 5 of both React Todos and Angular Todos mention syncing with GitHub. These sections should be updated to link to the appropriate page instead of re-writing information and also mention Bitbucket too.

amplication/amplication#5802

amplication/amplication#6615

Document the new plugin and also create the content for announcing the plugin on social media and our product updates email.
The output can be delivered as a Notion page

1. Section for our Monthly Product Updates Email
2. LinkedIn post
3. Twitter Post
4. Post for our community on Discord

See - amplication/amplication#5854
Check and execute if it should be mentioned in the docs

There are several changes that can be made to the Plugins section to make it more clear and readable.

First, the introductory sections of both the How To Use Plugins page and the Plugin Development Overview page need to be rewritten for clarity.

Second, the Plugin Development Overview page should include links to other important plugin development documentation, such as events reference and architecture. This will make it easier for developers to find the information they need.

Next, the list of plugins, in the How To Use Plugins page, should be moved to its own page titled "Official Plugins" or "Available Plugins."

Some sentences need to be rewritten to more clearly explain where developers can find plugins list in the dashboard.

The Create Your First Service With Amplication page on the Amplication docs right now only mentions GitHub. It's possible we'll need to update it also refer to Bitbucket, or just mention git providers in general.

Describe how to select the authentication type (JWT or HTTP in The Auth Settings window.

Relevant more for plugin developers
amplication/amplication#5851

amplication/amplication#6610

This How To article explains how to update the folder structure for committing generated code to your Git provider. This article needs updating.

amplication/amplication#6618

In First app documentation https://docs.amplication.com/docs/first-app it states that the Searchable field is inactive by default

Correct to read active by default.

amplication/amplication#6726

Open AI Integration
This plugin adds the ability to easily use OpenAI API in your service

Right now, there's a tip mentioning that the User entity is automatically created. This is no longer true. Also, there' an opportunity to mention the ERD view on this page.

There are various updates that we can make to the FAQ page. The first 3 are Muly's feedback from PR #301.

1. Remove the link to the v1.0 blog post. Use a better link.
2. Mention AWS as a supported git provider
3. Fix the wording to push to git repository instead of move to git repository

I got on a call with Alex Bass and we discussed how to improve the documentation website's design to improve the user experience.

He suggested the following changes:

Alex feedback:

Make it darker color (grey color) on things that are not clicked or highlighted.

Replace the purple with white, so when you click or hover it becomes white (links)

All hyper links should be (#53DBEE) 

---

Text that is not highlighted - B7BAC7‏
Text that active - FFFFFF
Hyper link iside the contant - 53DBEE

373D57 - bg
text - B7BAC7
Text - #FFF

---

Let's make sure everything is the same size and same font

Top menu 14px

Poppins

---

We don't need to use the purple at all for the text.
 It's


Right Sidebar:

Text that is not highlighted - B7BAC7‏
Text that active - FFFFFF
Hyper link iside the contant - 53DBEE


Left Navbar is navigation
Right is fast navigation

Right should have the same values as the left (which is white and grey )


For breadcrumbs:

darker grey for everything until you get to the actual active page, which should be white...

Remove the darker grey background color for the breadcrumbs...

menu on the left should be 14px...

menu on the right should be 12px

----


אלכס בס‎3:21 PM
D3D4DC
אלכס בס‎3:23 PM
B7BAC7
53DBEE
אלכס בס‎3:25 PM
Text that is not highlighted - B7BAC7‏
Text that active - FFFFFF
Hyper link iside the contant - 53DBEE‏‎
You3:27 PM
##22273c
אלכס בס‎3:28 PM
373D57 - bg
text - B7BAC7
*timestamp*
אלכס בס‎3:31 PM
top menu - 14 px same font  - font poppins
You3:32 PM
header background-color: #15192c
אלכס בס‎3:35 PM
right menu should have the color style of the left
אני11:25
Text that is not highlighted - B7BAC7‏
Text that active - FFFFFF
Hyper link iside the contant - 53DBEE‏‏‎
אלכס בס‎3:39 PM
breadcrumbs 
Current link - FFFFFF
papa link  - B7BAC7‏
icon - B7BAC7‏‎
no need in current link bg wrap
אלכס בס‎3:44 PM
side menu left -14px
fast nav on right - 12px
middle contant :
H1 - 32px semi bold
inner contant:
Title - 18px semi bold
text - 14px  regular color D3D4DC
line hight - 1.25rem (for inner content)

Make sure the arrow is around 14px. Should be tinier.

אלכס בס‎3:48 PM
left menu arrow should be smaller
14px
אלכס בס‎3:51 PM
bg of scroll bar - 15192C
scroll stick - 373D57

The Set Up Entities, Roles, and Permissions introductory guide is a good place to note one of Amplication's key features: Import Prisma Schema

Plugins are one of the most valuable capabilities offered by Amplication as they allow you to quickly upgrade your services with additional capabilities such as authentication, database providers, Kafka message broker, helm chart, and many more.

I think we should create a short page to explain them and how they contribute to you as a developer working with Amplication.
this page should be presented as part of the "introduction" section. From there we can send the user to read more thoroughly about all available plugins

Feedback from Amit Barlexz in discussion with Yuval included the following comments:

Found some difficulties when reading the README and CONTRIBUTING:
Followed the instructions on CONTIRBUTING and didn't know she should go to README to continue the setup.

Missing information includes:

• Do I need to run npm i on the root?
• Do I need to fork first and then clone?
• Didnt know how to start running the server and client
• missing some info about the packages and where to start
• Didn't notice the "Login" button to try SAAS - navigated to GitHub and only used the Open-source version

Action Items:

1. Review the README and CONTRIBUTING articles and change flow and structure to make the workflow more understandable.
2. Reveiw the other issues and determine how the documentation can be enhanced.

Develop and Integrate a sidebar labels feature for Amplication's documentation to improve the navigability and user experience.

For example, "New" and "Updated" tags would help developers see what's changed and what's new at a glance.

A "5min" label could help readers estimate how long it will take to complete an article.

I see the Prisma docs doing the above too.

Finally, for paid plan users, "Enterprise" or "Pro" labels would highlight premium features.

Similar to Bitbucket this option is only available in the Enterprise plan.

amplication/amplication#5405
amplication/amplication#6028

The generated folder is called admin-ui but the docs still say to run in /admin.
https://docs.amplication.com/docs/getting-started/dev-env

amplication/amplication#1068
Document the new plugin and also create the content for announcing the plugin on social media and our product updates email.
The output can be delivered as a Notion page

1. Section for our Monthly Product Updates Email
2. LinkedIn post
3. Twitter Post
4. Post for our community on Discord

amplication/amplication#5796

The Understanding Projects, Resources, and Services page makes the introduction section feel cluttered. Also, the page contains outdated definitions. The terms "Project" and "Service" get defined in the quick start guides already. If we need these terms explained, my recommendation is to have a separate "Concepts" page where we define Amplication-specific words.

Find a proper place in the docs to add our promotion banner offering 2 months free on the pro plan with the use of a coupon code.

amplication/amplication#1962

This is a feature available in the Pro plan.
amplication/amplication#6196

amplication/amplication#5989
amplication/amplication#5990

This is a very long article and doesn't provide an introductory overview of the steps to be performed.

Consider doing the following:

1. Create an overview article with a list of the steps, each one linked to a separate topic for each part of the process.

• Create a New App
• Create an Entity
• Add Entity
• Set Access Permissions - add the new documentation in sub-topics - see amplication/amplication#2372 (comment)
• Create Roles
• Set Entity Permissions
• Commit Your Changes
• Taking your app a bit further

2. Change the title of the article ( isn't the same process relevant even if it is not your first App?)

When searching for JWT, it does not appear on search results. This would appear to be related to the formatting of the headings in the article.

1. Research the reason for the search not working in this specific case.
2. See where this issue applies elsewhere in the docs and correct

1. Review the structure of the Getting Started and How to sections. Need to clarify what is the difference between Getting Started and How To, as many how tow processes are also performed when getting started.
2. Consider adding an article after "welcome" to outline the major steps which are included in the Getting Started section.

If I'm understanding correctly, the Monorepo approach puts your code in the root of the repository. The polyrepo approach puts your code into multiple folders.

Is it possible to have code put into multiple git repositories? Does this FAQ need to be updated?

The Git Sync Plan Differences page could use some updates on giving more information to users who would be interested in upgrading to Pro or Enterprise.

In the documentation for the plugin developers, we need to add a note that the developer should be careful when using the After events
let's also mention what to be careful about for the Before events.