# SMTK 3.1 Documentation Issues
**URL:** https://discourse.kitware.com/t/smtk-3-1-documentation-issues/283
**Category:** Software Process
**Created:** [June 29, 2019, 2:55am UTC](https://discourse.kitware.com/t/smtk-3-1-documentation-issues/283 "2019-06-29T02:55:44Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Bob\_Obara](https://discourse.kitware.com/u/Bob_Obara)
#### Post date: [June 29, 2019, 2:55am UTC](https://discourse.kitware.com/t/smtk-3-1-documentation-issues/283/1 "2019-06-29T02:55:44Z")
# User Guide Comments
## Front Page
- Should also address operations and use cases of building/modifying things like model and model resources. - Currently its very attribute centric
## An Overview of SMTK’s Subsystem
- What is a better name than subsystem? Alternatives include:
- Concept (Major, Minor, etc…)
- Library
- Aspect
- Need concept of Persistent Object
Note that this is a work in progress discussion…
---
### Author:  [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [August 5, 2019, 5:33pm UTC](https://discourse.kitware.com/t/smtk-3-1-documentation-issues/283/2 "2019-08-05T17:33:25Z")
@Bob_Obara Besides the documentation itself needing some polish, it appears that Kitware owns [smtk.org](https://smtk.org/) but that it is misconfigured (neither the SSL cert is correct nor does it point to a good website). I would like to have gitlab pages enabled (or failing that use our github mirror) so that we can maintain a front page for SMTK that points to our documentation but also has other things there (e.g., [vtk.js](https://kitware.github.io/vtk-js/index.html), [sensei in situ](https://sensei-insitu.org/), [paraview glance](https://kitware.github.io/paraview-glance/index.html)).