Getting started with IcePanel
Quick start guide
Getting started in IcePanel is simple. Here is a quick example to follow so you can have robust system documentation that will help you educate, learn, make decisions and plan future developments (which also look pretty cool).
Step 1: Create your first context view
- Create a landscape (if you haven't already)
- Add the top-level objects for your design, such as: the system(s) your company develops (start with 1), third-party systems you depend on, and people who use your solution, such as customers
- Add connections between the different objects, highlighting their high-level relationships.
Adding and editing objects in diagrams automatically adds them to your model to be re-used later.
What this is for: This is the context level (Level 1) of the C4 model, and the focus here is the big-picture view of your system architecture. This will mainly show how your system(s) solve your customer's problems, remaining primarily at the business level, so keep it simple!
Target audience: Everyone! Anyone in or out of your company who needs a high-level overview of how your system(s) work. Perfect for your business, product, or other non-technical peers, as well as onboarding new technical teammates.
Make sure to: Name your objects in a way anyone can understand. Label all connections so the relationships are clear.
Step 2: Zoom into a system and add your apps/stores
- Zoom into a System (using the + icon on the top left of the system).
- Add the Apps and Stores that are inside the primary system.
- Connect them to show messages or relationships between them.
What this is for: This is the App level (Level 2, known as Container diagram in C4). It shows the individually deployed/runnable units in each System that execute or store code.
Target audience: Mainly technical people, such as architects and developers. Some product people (such as product owners, product managers, or business analysts) will gain value here, especially for planning purposes.
Make sure to: Name your objects in a way anyone can understand. Label all connections so the relationships are clear.
Step 3: Add existing objects from the level above
Because we're using a model, we can add objects from higher levels here, such as other systems you depend on or the people interacting with your solution.
- Add your Actors and Systems from the level above by either: double-clicking in the diagram and typing their name, or going to the "Model objects" tool on the left and drag them in.
- Add the connections to the apps/stores inside the system from previously created connections.
You can create multiple diagrams to show different views of your model. Examples include customer-specific views, focusing on one object, and current vs. future design. Connections that were created at a higher level will show as higher connections.
Step 4: Assign tech choices
Once you have your Apps and Stores laid out and connected, start adding any tech choices, such as what service in AWS, GCP or Azure service, languages, libraries or frameworks, etc.
- Select your model object. You can multi-select objects by holding the Shift key.
- Go to the technology section on the right-hand panel.
- Search for your tech choice and add it.
These choices come with docs preassigned and a simple description for those unfamiliar. These can be used later to highlight tech choices using the tags bar, allowing people to learn your architecture's technical choice landscape and filter your model.
Step 5: Describe each object and diagram
Each object and diagram has a description, which adds details to help your teammates understand how things work. Descriptions follow that object wherever it is.
The minimum you should add is a brief displayed description for each object. This might seem obvious, but it will help your teammates (especially new ones).
- Select an object.
- Go to the right-hand panel.
- Add a displayed description to each object (max 120 characters).
Try to explain: what the object is, and what its primary responsibilities are.
Use the detailed description field to show other useful information, such as a link to the appropriate repository. The detailed description field supports Markdown.
Step 6: Collaborate with your teammates and Share
IcePanel is a collaborative tool for your whole team. Getting others involved helps you gain knowledge from across your business. Invite them as viewers (unlimited and free on all IcePanel plans) or create interactive read-only share links of your designs. Share links are a great way to showcase your designs without them needing an account using just a browser.
Invite your teammates:
- Click the Share button in the top right of the screen.
- Type the emails of the people you want to invite to your team.
- Send invitations.
Create share links:
- Click the Share button in the top right of the screen.
- Navigate to the Share link tab.
- Toggle on share links.
- Copy and paste the link to anyone you want to show your designs.
Wherever you are when you create a share link will be where your audience lands when opening the URL. This includes position, selected object, Flow, Tags etc.
That's the basics!
Congratulations! You've started your journey into interactive architecture documentation that remains up-to-date and can be accessed by all your teammates!