Skip to content

Conversation

@dempseyatgithub
Copy link
Contributor

As discussed in the last website workgroup meeting, Swift info architecture project proposals and documents will be included in the swift-org-website repository.

The proposals are not rendered as webpages on swift.org.

Jekyll automatically ignores directories and files beginning with #. Since files beginning with an underscore are typically part of the configuration / operation of Jekyll itself, the directory name is #info-architecture to emphasize this is not part of the Jekyll infrastructure or published on the website.

This PR includes the first two proposals that have been announced and reviewed by the community. Future proposals will be added when they are ready for community review and feedback.

Copy link
Member

@heckj heckj left a comment

Choose a reason for hiding this comment

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

Content is great, but would you mind terribly if we switched the prefix from # to _, as the # symbol is causing no end of pain for me when I'm trying to interact with it on the command line.

Plus, that keeps in line with the other "ignored" directories that need to be explicitly included per config (https://jekyllrb.com/docs/structure/)

@dempseyatgithub
Copy link
Contributor Author

@heckj I changed the prefix to _. Items prefixed by # are also automatically excluded by Jekyll, but if that makes it much more difficult to use on the command line, let's change it. Was trying to differentiate it from a directory that was part of Jekyll's infrastructure or a directory that has content intended for the site.

I'm fine with using _.

@dempseyatgithub dempseyatgithub force-pushed the info-architecture-proposals branch from 8c52def to 4b2099e Compare July 10, 2025 18:35
@dempseyatgithub dempseyatgithub merged commit 54903ca into swiftlang:main Jul 10, 2025
3 checks passed
@dempseyatgithub dempseyatgithub deleted the info-architecture-proposals branch July 10, 2025 19:11
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