Skip to content

Conversation

@ilyaZar
Copy link

@ilyaZar ilyaZar commented Feb 5, 2026

Fix #335

Just for illustration purposes. Some people may prefer such navbar information on the side. Branch for illustration is https://ilyazar.github.io/thecrawl/

For the moment at the top as a short minimal fix , so people see whats going on

Light:

image

Dark

image

cheers

Add a thin, unobtrusive navigation bar at the top of the page with
links to About, Docs, Submit, Status, and GitHub. This helps new
users discover important onboarding information without scrolling
to the footer.

- New: _includes/site-nav.njk partial
- New: static/style/site-nav.css styling
- Modified: layout.njk to include site-nav
- Modified: styles.css to import site-nav.css
@kaste
Copy link
Collaborator

kaste commented Feb 6, 2026

Thanks for coming by. I think I just moved these to the footer tbh. Some of them at least (like "About"). Status, Octicon link and About are very typical secondary links from a footer. So we need to discuss that. If we do this it should be on the primary header line I guess, for most viewport widths there is plenty of room there too. Maybe in a Hamburger menu, as that is easier to manage if we also support the narrow mobile views.

At this point in time, it is unfortunately also not clear if sublimehq will grab, copy and/or close this site. I have a few things on my disk I will upload, but then we might be in maintenance mode after this next weekend.

@ilyaZar
Copy link
Author

ilyaZar commented Feb 6, 2026

yes there are many options for navbars; I was more pointing to the fact, that I was unable to graps the purpose of the new site within a minute so.. (illness of a modern busy world ...)

regarding site ownership: lol seriously ? ok thanks for being so honest about this, because it saves me some time thinking through about certain other style things which I will not do anymore given the situation

if sublimehq is going to grabb/own stuff just like that ... change the license :) they are not going to sue anybody with a 4/5 people team this is not microsoft

and messing around with external/open source contributors like that ... that would be a really unwise decision, they should be glad that they have a community doing open source stuff for a commercial (and not open source) product . I mean, there are like at most 5people or something since the last 15years or so; compared to other projects like neovim (not to speak about vscode ...), SBhq lacks certain resources ... if the remaining community goes, well than thats pretty much it; what do they expect, that outside unpaid contributors are going to spend their time on enhancing a commercial product (thereby saving money on the 6th, 7th UI developer they might have to hire to maintain their website stuff); like the deathaxe guy is going to save PackageControl just for his fun sake ? taking over the paid job of wbond, I mean ... maybe one should pass them a wikipedia article on the point of open source and why people are willing to contribute their time toward a project ..

@kaste
Copy link
Collaborator

kaste commented Feb 6, 2026

LOL, yeah man.

@braver
Copy link
Member

braver commented Feb 7, 2026

SublimeHQ has an excellent track record of working with the community on core aspects of the project, like packages, and the community docs are respected and listed on the main website. So I'm sure we'll come to a balance that works for everyone involved.

However, it's currently just not very clear where each individual component of this project will land. They're probably mostly going to be concerned with the underlying infrastructure and the package itself, not so much with the website. But we'll see.

With that, how we solve #335 will need a different approach depending on the outcomes of that.

Moving links to top of the page is not the answer IMO, they're fine in the footer. We used to have "about" in the top bar, we could bring that back. But right now the purpose of the site being unclear is more caused by the project being in a transition period than any particular design decision.

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.

3 participants