Yes, this is called Formurla meaning formula in an url. eg
/beside(above(a,b),beside(c,d))
  +—+—+—+
  | a |   |   |
  +—+ c | d |
  | b |   |   |
  +—+—-+–+
Where each of the above boxes is a FractalComponent and a,b,c and d are
different kinds of content, for example
  a = Graph(foaf2014)
  b = AllegationsTable(authLog)
  c = SubjectsTable(authLog)
  d = d   # the most appropriate visualizer for this identifier will display it
So the real url might look like this:
  /beside(above(graph(g=foaf20140114.nq),allegations(authLog)),\
          beside(SubjectsTable(AuthLog),d))
but really just mentioning an identifier should visualize that
in the fashion the user prefers, so:
  /beside(authLog,systemLog,1d_2)
would portray authLog, systemLog and 1d_2 with the user’s preferred
visualizations for those entities, or the default visualizer, failing
back to print().
Note these points:
   /beside(beside,above)
      would actually show the code for beside and above beside one another.
   /beside(beside(),above())
      would show the panes but they would be empty, ready to receive drops
         +—+—+—+
         |   |   |   |
     +   +   +---+
     |   |   |   |
     +---+---+---+
Questions:
1) Does this mean the default front page has the formurla?
     /above(header,welcome)
2) Should it be shown?
3) Once logged in should it be?
     /above(header,beside(metaKB,intro))
4) Those these are the appropriate formurlae, should we bother showing them?
   Uh, that is NOT clear!
5) Could coming up with shortcuts for formurlae help?
   For example the formurla
     /above(header,beside(metaKB,intro))
   could have the shortcut
     /zBga
   which might be stored in the assertion:
       “above(header,beside(metaKB,intro))”
   which might be nestable, eg
     /beside(zBga,zBga)   # yada yada, but you wouldn’t bother presumably
             
            
              formurla_prefix: '/__/'
  default_formurla: 'print("getting default_formurla from FormurlaManager")'