-
Notifications
You must be signed in to change notification settings - Fork 23
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-373 customer-portal.md #374
Changes from 1 commit
7ee7985
969471a
e36cf4e
5e434d9
5431c75
3c95771
f9194ff
26ec79c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,125 @@ | ||
# Introduction | ||
Entando Customer Portal is a self-service application for customers to interact within your organization to administer your Entando platform and its users. You can manage users, projects and customers. You can track projects and service tickets for your application. It is a Kubernetes-native solution built on Entando’s Application Composition Platform. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this reads like an entando customer's customers have the ability to manage the customer's entando platform and everyone who uses it, like the customer's customers have control and authority... then that's kind of contradicted by the next 2 sentences. maybe reword for clarity? i'd also lead with the last sentence. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "The Entando Customer Portal provides your organization with a self-service application, making it easy to manage users, projects and customers. Using the Role Based Access Control (RBAC) model, users are granted varying levels of access to optimize your workflow process. It is a Kubernetes-native solution built on Entando’s Application Composition Platform." How's this? I don't like to start with the Tech verbiage because that seems less important than what they get from the product? Although I am not explaining it very well. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I agree, definitely start with the business value. What you have is much better already. Tweaking further "The Entando Customer Portal enables an organization to quickly provide a modern, customer-facing self-service application for management of subscriptions and service tickets, via a lightweight integration to JIRA Service Management. Organization admins can use the included Role Based Access Control (RBAC) design to grant users different levels of access to the portal. It is a K8s..." There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. definitely want to lead with value! i really like the edits There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Umm, how about this? Softened and slowed it up just a bit. It sounded really professional and informative but a bit unapproachable? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Round 5(?)
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🤣 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I said just a BIT! :) |
||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Role-based access control ?? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's most often 'role-based access control' but sometimes it is capitalized and not hyphenated. In this case, I like that it gets highlighted so I'm tempted to leave it as is. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We have it in caps above, but hyphenated here. Maybe just drop the hyphen at line 12. |
||
Key Features: | ||
|
||
* Customizable service ticketing and tracking system with Jira Service management | ||
* Role-Based Access Control (RBAC) Entando Identity Management System | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we should lock down if role-based is hyphenated for the style guide; i've been leaving it as two words with a space between (as it was written prior to editing) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not sure but a google search for Role-Based Access Control seemed to be hyphenated so I just went with it. Will do more research. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. not a big deal; i just know i've been not using a hyphen so wanted to sync with you on that There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think the general rule should probably be when referring to RBAC specifically, it is hyphenated. In all other cases, it can be used in both ways. But is is not capitalized so have to correct that. |
||
* Integrated User, customer, project and subscription management | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. lowercase "user"? unless Integrated User is a proper noun There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. it's lowercase. |
||
|
||
This tutorial covers | ||
1. [Installation](#installaton) | ||
2. [Configuration for Administrators](#configuration) | ||
3. [A brief User Reference](#user-refernce) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. it seems like "brief" should be capitalized ?? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It ended up being such a small section, wasn't sure what to call it. I'm kind of waiting to see what Nathan thinks of the section. Will take 'A brief' out. |
||
|
||
# Prerequisites | ||
* A working instance of Entando running on Kubernetes. See [Getting Started](../../docs/getting-started/)for more information. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. space after link |
||
* Use the Entando CLI to verify that all dependencies are installed: | ||
ent check-env develop | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. link to Entando CLI and skip citing the command? referencing the CLI will surface that and preserve the limited detail provided by the first and third bullets There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I like your idea too but it's such a short command, I hate to make people go elsewhere just for that. Maybe just tweak the statement. I'm not sure what you mean by preserving the limitation of the details of the specified bullets? How about: 'Use the Entando CLI command There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yes, if you redirect someone just for a one-liner that needs no context or explanation that's unnecessary and annoying. if they're not familiar with the CLI i could see a link; if we assume they are i love your reworked sentence! There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. actually idk what you mean by "are consistent"?? maybe just "..verify all dependencies"? by preserving limited detail i meant that the first and third bullets don't provide specifics, whereas the second bullet provided a specific command There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. compatible? Use the Entando CLI command ent check-env develop to verify that all dependencies are compatible There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. i'd leave it at "verify all dependencies"... that implies compatibility. short and sweet. |
||
* Docker installed and running | ||
|
||
# Installation | ||
## Quick Install from Entando Hub | ||
|
||
1. From the Entando Hub, click on the Customer Portal bundle from the Catalog | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. in the Catalog? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think it works both ways. |
||
2. Click Install to see a popup page with two commands. These need to be implemented in the order shown. Copy the first command and paste into your CLI. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. would say "executed" instead of "implemented" |
||
3. Copy the second command and do the same. The content bundle will now be deployed. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. would remove "Copy the first command..." from 2. and reword 3. to something like "Run the first, then second, command from the CLI." |
||
4. Go to the Entando App Builder and navigate to the Repository. Here you will see the two bundles for the Portal. Install both bundles in the version you desire. You will be able to update the version at any time. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. the wording implies both bundles must have the same version ?? |
||
5. To navigate to your Customer Portal: <br> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. noting that the customer portal is being referred to as either Customer Portal or Portal |
||
from the left menu → `Page` → `Mangement` <br> | ||
find `Customer Portal` under `Page Tree` list<br> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. would remove "list" There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. it's a long list so I wanted to prepare them. |
||
from the `Actions` pull-down menu → `View Published Page` | ||
|
||
## Manual Install | ||
Top install the Entando Customer Portal manually to your specific environment, go to the [Entando Github Repository](https://github.com/entando-samples/customer-portal/tree/main/application) and refer to the README.MD there for more details. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. To install? :) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Let's avoid pointing directly to the source code for documentation. 1) dev.entando.org is supposed to be the definitive place for docs, and 2) I don't trust developers to maintain READMEs, apply style guides, etc. even/especially if that developer is me... Let's discuss on our next call but I was thinking we'd have a manual install just like the Standard Demo with the 2 commands that need to be run. Any pre/post steps beyond that we should document here. |
||
|
||
# Configuration | ||
## Administrators | ||
In order to configure the Customer Portal and its users, the administrator will need Jira Service Manager and Entando Identity Management credentials. As the administrator, you can create and configure users and groups, assign roles, projects and track service tickets. You can also customize the ticketing system. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. would reword to "...assign roles and projects, and track..." |
||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not sure where it should live but we still need the config steps for 1) enabling the mail mapper in keycloak per https://github.com/entando-samples/customer-portal/tree/main/application "The built-in mapper for email must be enabled on the server client so that user accounts can be retrieved from Jira and tickets created used that account information.", and 2) using the cp_admin_config.page to configure the Customer Portal to connect to JIRA Service Management. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As a TODO we still also need a way to configure the Customer Portal to let it work with a specific Jira Service Management instance. There are a couple tickets open to finish that work. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. added some bullet points under Entando ID Management in the document for now. We can discuss more where it needs to be permanently. |
||
### JIRA Service Manager | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. above this is referenced by "JIRA Service management"; would change line 6 to "JIRA Service Manager" There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The product name is JIRA Service Management. I think we've called it the wrong name in multiple places. https://www.atlassian.com/software/jira/service-management |
||
|
||
The administrator begins here to create users and projects, define the organization, and configure the service ticket system. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. would say "uses JIRA Service Manager" instead of "begins here" There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. will reword |
||
|
||
Go to Customers to add organizations and projects. Once added, click on the name of the organization to get the ID from the URL which is needed later, e.g example.com/jira/servicedesk/projects/ECS/organization/3, where the organization ID is “3”. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. URL, which |
||
|
||
For more information or help with the Jira Service Management System, contact ?????? | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. lol maybe don't offer a lifeline! There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Agreed, or maybe have a Resources section with a link to JIRA Service Management - https://www.atlassian.com/software/jira/service-management. Also to the source code, at a minimum. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ok will add links under Resources |
||
|
||
### Entando Identity Management System | ||
Logging into the Entando Identity Management System, you will see the landing page below. The left navigation bar is your guide for managing users, groups, and most importantly, roles for your application. Using the RBAC model, you define what users have access to by the roles and groups they are assigned to. Some important guidelines are noted below. | ||
|
||
![Entando Identity Management System](./images/custportal-idmanagement-main.png) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. would introduce A, B, etc., with a note on what this list comprises (i.e. configuration options) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I know this bothered me too. Maybe the order doesn't matter so much. |
||
|
||
A. **Define the Realm Setting**. The Realm is a set of users, credentials, roles, and groups. A user belongs to and logs into a Realm. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. line break between bold and unbolded text |
||
|
||
B. **Create Roles**\ | ||
You must select the roles available to users and/or groups. Create new roles with varying degrees of access for the needs of your application. You can also use the default roles by clicking on Client Roles and choosing entandodemo-customerportal-server. The following define their parameters for access: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "The following define their parameters for access:" reads a little off... what about "The access parameters for roles are defined as follows:" ?? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Let's not suggest creating new roles. They can use keycloak for that but the guide is to help them use what's available in the Customer Portal. |
||
* cp-customer - assigned directly to specific projects for a single customer | ||
* cp-partner - assigned directly to specific projects for multiple customers | ||
* cp-support - read only view of all customer projects | ||
* cp-admin - admin access for Customer Portal. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. no . |
||
|
||
C. **Create New Users**: | ||
1. The user must be created in Jira first, then configured here for access to the Portal. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. would nix "here" |
||
2. From the navigation bar, go to Users. Click `Add User` at right. | ||
3. Enter the fields as needed but note the requirements for the following:\ | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. would reword to "Enter information in the fields as needed, but..." |
||
`Username`: A unique name\ | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. lowercase "a"? |
||
`Email`: must use the same address used in Jira\ | ||
`User Enabled` → On\ | ||
`Email Verified` → Off\ | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Let's remove this line. That's up to the admin. |
||
Save | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. would make "Save" a separate step to preserve 1 action/task per step - or omit (should be obv to save) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The layout of the page is a bit confusing and the save is not so obvious |
||
|
||
4. From the headings, go to `Credentials`. \ | ||
Under `Credential Reset`, in the `Reset Actions` → Update Password. \ | ||
For external users, you can extend the `Expires In` setting to a minimum of 2 days. \ | ||
Click `Send Email`. \ | ||
This will send an email to the user to activate their account and set a new password. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. would lead with the last sentence to introduce what you're doing, e.g. |
||
5. Role Mappings | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. something like "Assign the user to roles with Role Mappings:" then line break ?? |
||
For each user, select the appropriate `Realm Roles` from the `Available Roles` and click `Add Selected` to assign. If you want to use the Customer Portal default roles, choose `entandodemo-customerportal-server` from the `Client Roles` pull-down menu. This will give you additional roles that you can add. Check the Effective Roles column to make sure the correct roles have been assigned. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. restructure this paragraph to instructional line items like in the previous steps? "do this ___ to..." ?? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "If you want to use the Customer Portal default roles" - this isn't an option. If they don't use the pre-defined roles, they have to build their own version of the CP since the RBAC controls are based on those roles. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. can they create Realm roles? tried to make it step by step and it's messier |
||
|
||
![Entando ID Management Role Mapping](./images/custportal-identity-userrole.png) | ||
|
||
7. Under Groups, assign to appropriate groups. Roles are additive as in RBAC models. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "...assign the user to..." There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. reworded |
||
|
||
### Customer Portal Administrator | ||
|
||
As administrator for the Customer Portal, you can create and manage customers, projects and subscriptions. You will also be able to assign projects to users who have activated their account on Jira and have been assigned roles in the Entando Identity Management System. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "You can also assign" instead of "You will also be able to" - match tense |
||
|
||
The administrator also needs a Jira account and the correct role assignment in the Entando ID management system. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. would lead paragraph with this - has to happen before anything else There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this depends on how people read these sections, and in my mind, they are looking for operations/functions first? |
||
|
||
![Customer Portal Landing Page](./images/custportal-landing-page.png) | ||
|
||
**A. Create a Customer or Partner**\ | ||
Creating a Customer or Partner is a similar process. Here we have laid out the details for adding a Customer. Please follow the same procedure for adding a Partner. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. would say "Below are the details..." - no other references to we, and less casual |
||
1. Click Add a Customer | ||
2. Enter the details: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Customer details There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. is it needed? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. it's redundant :( but "the details" sounds a little odd to me. add details? idk. it's minor. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. reworded section |
||
* The Customer Number must be unique. | ||
* The notes field is visible only to Support and Admin users. | ||
* Click Save | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Save is not real a detail; would make its own step or omit (should be obv) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. these instructions came from an admin person, and are for admin people, so I kept the obvious stuff There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. got rid of some but still unsure. it is obvious. |
||
|
||
![Customer Portal Add Customer](./images/custportal-addcustomer.png) | ||
|
||
**B. Create & Assign Projects** | ||
1. From the landing page, click on any customer to see their associated Project list. | ||
2. To create a new project, click on the header → Add a Project. | ||
* Enter the Project details | ||
* Provide the Organization ID from Jira. Only one project in the portal can be used with that ID. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Portal |
||
* Click Save | ||
3. To assign projects | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. : like used in similar contexts above? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. sorry - To assign projects: There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Took out the colons. They are both instructions. |
||
* Use the drop-down menu under Action on the right side and choose → | ||
Manage Users | ||
* Find the user and click Submit | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. would say "Select" instead of "Find" - more precise |
||
Use the drop-down menu under Action to manage Partners, and request and manage subscriptions. | ||
|
||
### User Reference | ||
|
||
All Customer Portal users need Jira Service Management credentials and Access provided by your organization administrator. You can request and track subscriptions and create and track service tickets. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Access capitalized? or lowercase? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. mistake, lowercase. |
||
|
||
Once you login to your Customer Portal, you will see your list of customers. Click on any customer to see the details and to track their projects. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "the details" -> what details? would say "their details" or "customer details" There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. kind of a mess! reworking |
||
|
||
1. To create a Service Ticket for a project, use the Action pull-down menu → Open Ticket | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. service ticket now capitalized?? |
||
|
||
![Customer Portal Open Ticket](./images/custportal-open-ticket.png) | ||
|
||
2. To Request a Subscription or track all Tickets, use the same Action pull-down menu and choose the corresponding option. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. the capitalization here is odd... |
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need the 2nd level nav in the left bar so add this to the top:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was wondering why the nav was incomplete, thought I was confused about the header level that was included but now it makes sense. :)