theos / theos.dev Goto Github PK

During first launch of Xcode, the following window shows up:

It should probably be clarified in the docs whether "iOS" option should be ticked here.

It's partially so huge because it downloads emulators and all sorts of junk. But does it download SDKs too or are they included by default? Are the SDKs even needed for Theos if you use the patched SDKs, or rather, do the default SDKs even still work in Theos in latest Xcode?

It says this:

But Swift for some time is already bundled with iOS and the ${LIBSWIFT} dependency isn't even installable on newer iOS (especially on rootless where it's just missing).

This PR was submitted for templates (theos/templates#32):
theos/templates@6d400f1

So I think that docs should also change

Depends: ${LIBSWIFT}

to

Depends: firmware (>= 12.2) | ${LIBSWIFT}

in that place.

See: http://theos.howett.net/nic/

A number of users have expressed that navigating to the docs from the current homepage is unclear and/or that the current homepage's existence doesn't make sense. To remedy this, I think it would make sense to remove the current homepage, update the docs landing page, and use that for the homepage. The current site only provides the docs and has a footer that provides the links on the current homepage, so I don't think we'd be losing anything in going through with this change.

Opening this as I am unsure how to best approach this and know others may have thoughts/implementation ideas.

The current sidebar implementation works wonderfully on a typical browser, with the various pages and subpages hyperlinked on the side. On mobile, however, this sidebar is placed at the bottom of each respective page. This is functional, but non-ideal for navigating the site. I think it's worth updating our code to hide the page-based sidebar and provide a fixed, JS-based button to present the sidebar on mobile.

I have taken a brief look at implementing this, but the current jekyll setup [1, 2] complicates things a bit. That being said, I am by no means a proficient web dev, so if others want to take a crack at it or have other ideas, feel free!

The previous wiki page still has some bits of info not on this repo. Namely "Command line interface" and "Splitting Logos Hooking Code Across Multiple Files"