Hi Andrew, El vie., 7 jun. 2019 a las 0:39, Andrew Wetmore (<[email protected]>) escribió:
> @[email protected] <[email protected]> I think the > "flex-equivalents" page should go just below the "components" page in the > ToC. > Don't see "Components" page, do you mean "Component Sets" ? > If you told me how to add things to the ToC, I don't remember it! > yeah! TOC is in "_data/toc.json" notice that there's a relation between urls and folder names, so if you want flex-equivalents in the main TOC you need to move it to root folder, or if you nest in a folder TOC expect a main node called in the same way. You can see how is done in other nodes and copy how it's done. > And, really, I think both Component Sets and Flex Equivalents should be > under a User Interface heading, as the source files are. > The problem with that is that we don't support 3 nesting in TOC, but I think that is good. Useful docs use to be 2 levels and simplify as much as possible the path a user must to follow to reach useful documentation. For that reason Component Sets needs to be on root and nest all sets that will be populating as we create it. That will be a huge aumount of info that seems to be easy to navigate for a coming user, since he wants go to a set and he goes directly to the branch. In the other hand I think is good to have docs about how Royale and Flex share concepts and things, but I always said that Royale is new software and we should try to avoid populate compilations in many places to give Royale its own entity. So I prefer to put all Flex comparisons in a concrete zone, for people that comes from Flex world and want to learn all about similarities. IOW, we changed the name from FlexJS to Royale since we want us to create a brand that was seen as something new with its own personality and future and avoid as much as possible be weighed down by the weight of another technology that is going through bad days. If we can to concentrate as much as posible Royale Flex related docs in one place I think that would be great for Royale in global. -- Carlos Rovira http://about.me/carlosrovira
