# New Swift-DocC content styling

**URL:** <https://forums.swift.org/t/new-swift-docc-content-styling/55326>\
**Category:** Swift-DocC\
**Created:** [February 14, 2022, 11:34pm UTC](https://forums.swift.org/t/new-swift-docc-content-styling/55326 "2022-02-14T23:34:29Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Karl](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@Karl](https://forums.swift.org/u/Karl)\
**Post date:** [February 17, 2022, 8:29pm UTC](https://forums.swift.org/t/new-swift-docc-content-styling/55326/6 "2022-02-17T20:29:37Z")

</div>

> [@beatriz](#):
>
> I totally see your point. By default, we can have have a simple design like the one in these screenshots, though I appreciate your feedback— will continue to investigate whether the default options should be simpler. For example, just a solid color. Eventually, I'm excited for this to be a customizable component.

I had [a quick go](https://forums.swift.org/t/swift-docc-sidebar/55250/12) at prototyping it using the WebKit inspector. I appreciate you continuing to refine the default options, and customisation would definitely be welcome as well (I understand that's a bigger topic for DocC-Render).

> [@beatriz](#):
>
> The text below the page title continues to be the summary for that page. The "Inherited form View.cornerRadius(...)" is a bit of a confusing example, but that's actually content generated by Swift-DocC itself and something we'd like to improve there. For the common-case where you've written a documentation comment for that symbol, the symbol's summary would be rendered here. That's better represented in the other screenshots I shared above, for SlothCreator and Sloth.

Looking at some of the other pages from Ethan's argument parser demo, I wonder how well this scales. If the summary is small, things work relatively well. But [this page](https://ethan-kusters.github.io/swift-argument-parser/documentation/argumentparser/parsablecommand/main()), for example, has a 3-line summary.

 ![image](https://global.discourse-cdn.com/swift/original/3X/f/2/f214ff02e16ee8c7300f99e24c64b3971b9d7f3e.jpeg)

At that point, you're basically reading the documentation of the symbol as centred text in the header, which doesn't feel very comfortable. Meanwhile, the content space below shows "No overview available".

That's quite unfortunate, because AFAIK there is no way to have the longer overview text without a summary.

I'm not sure if DocC-Render can be smarter about detecting these situations (and perhaps treat a long summary as an overview), or if the documentation just needs to be restructured to account for the new page style. In this case, I think a shorter summary is possible, but perhaps that is not always the case.

* * *

Another thing I wonder about with these design changes is what the plan is for the table of contents ("On This Page"). Is the idea to remove it? Will it be replaced with anything?

---

_[View the full topic](https://forums.swift.org/t/new-swift-docc-content-styling/55326)._