Skip to content

initial content - #3

Open
Tsche wants to merge 2 commits into
masterfrom
users/Tsche/initial_content
Open

initial content#3
Tsche wants to merge 2 commits into
masterfrom
users/Tsche/initial_content

Conversation

@Tsche

@Tsche Tsche commented Aug 12, 2026

Copy link
Copy Markdown
Member

This patch adds some initial content to fill the page. This is probably not very complete yet.

@Tsche
Tsche requested a review from a team August 12, 2026 04:36
@Tsche

Tsche commented Aug 12, 2026

Copy link
Copy Markdown
Member Author

@cppsocial/curators please review the content in this patch for correctness and quality. I'm sure we're missing a lot of content (for example I didn't have an invite link for TCCPP that isn't a vanity link) - let's do additions in separate patches (feel free to start opening issues to track them).

The about and contributing pages are pretty much empty as well. That's on purpose (gonna do that later), I guess it'd be nice to use github wiki to document how to add content to cpp.social :)

Please ignore CI failures as well, I'll mess with that once review for the initial content has concluded. It's currently failing because the metadata update job hasn't run yet.

@Tsche

Tsche commented Aug 12, 2026

Copy link
Copy Markdown
Member Author

To make the content review a little less painful, here's a current render of the site. To view it, extract the archive and run a http server :)

tar -xzf site.tar.gz
python -m http.server --directory build/

site.tar.gz

Comment thread content/about/about.md
Comment on lines +1 to +2
[cpp.social](https://cpp.social) is a community-driven resource aggregator. All content on this website is managed in a [git repository](https://github.com/cpp-social/site) or automatically retrieved from configured sources.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we maybe want to use semantic line breaks (https://sembr.org/) like the C++ draft markup?

If we're going to maintain this git-based, it makes code review much easier in the long run if the line-based diffs are somewhat clean and logical.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a good idea.

I'll go through the content and see where we can do sembr without changing the way stuff renders. If it causes render failures, I'd prefer to address this separately (to split work on content from work on the site generator).

title: Instant messaging and chat
description: Real-time conversation, questions, and community coordination
randomize: true
cards:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feels like TCCPP is missing from this list.

@Tsche Tsche Aug 13, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, I didn't have an invite link for TCCPP other than the vanity link. The problem with the vanity links is that they can get yoinked rather easily - if you lose boosts, another server can grab your link (after a very short grace period iirc).

We require a regular invite link that never expires for this. Please send a followup PR to add TCCPP :)

- type: card
title: Emscripten
path: https://emscripten.org/
icon: https://cdn.simpleicons.org/webassembly

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Emscripten does have its own logo icon, so using the WASM icon feels a bit misplaced.

Comment thread content/ecosystem/libraries.yaml
Comment on lines +23 to +26
- type: card
title: IEEE 754-2019
path: https://standards.ieee.org/ieee/754/6210/
description: The active IEEE standard for binary and decimal floating-point formats, arithmetic, exceptions, and reproducible numerical results

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps it would make more sense to use ISO/IEC 60559 here, since that is what the C and C++ standards actually reference.

Comment on lines +31 to +34
- type: card
title: "ISO/IEC TS 18661-3"
path: https://www.iso.org/standard/65615.html
description: ISO/IEC TS 18661-3:2015 extends programming language C to include types with the arithmetic interchange and extended floating-point formats specified in ISO/IEC/IEEE 60559:2011, and to include functions that support the non-arithmetic interchange formats in that standard.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has been absorbed into C23; see https://cstd.eisie.net/c2y.html#M.3

There's really no point in looking at this standalone document anymore.

Comment thread content/standardization/resources.yaml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants