Jerry Wu

I would suggest moving `write_latex()` to a separate PR. Could the team review whether this PR meets the expectations for `write_raw_html()`? Thanks!

I suspect the doc build failure might be related to the change in Polars (`pl.DataFrame.deserialize`).

Thanks for pointing this out! I originally thought it was a cool feature and didn’t notice that.

@dafriedman97, maybe try using `tab_options`: ```python from great_tables import GT, loc, style from great_tables.data import islands islands_mini = islands.head(5) ( GT(islands_mini) .tab_stub(rowname_col="name") .tab_style(style=style.fill("lightgray"), locations=loc.body(columns=["size"])) .tab_options(stub_background_color="lightgreen") ) ``` 

@hasibagen If I understand correctly, `feature_result.tab_options(table_width="300%")` should do what you want. However, in the last line, you're displaying the original `feature_result`, not the modified version—so the table appears unchanged. With...

Thanks for the feedback—this reminded me that we do have a warning message for `.cols_width()` [here](https://github.com/posit-dev/great-tables/blob/ae0204cd8f79cc6119a4678f20a243f43f422f52/great_tables/_render_checks.py#L37-L43). I haven’t used this function often myself, but you might try setting `quarto_disable_processing=True` to...

I'm not sure what's going wrong—the example runs fine on my machine: ```python from great_tables import GT from great_tables.data import sp500 # Define the start and end dates for the...

@rich-iannone and @machow, perhaps we should use a `try-import` here to handle the compatibility issue.

I'm wondering if this could also be achieved using [anywidget](https://anywidget.dev/) (#301).

@rich-iannone, I recall seeing a video where you shared your experience implementing a table that could be beautifully sent via email. Could you provide some insights on that? What else...