-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EPIC] Build Section #413
[EPIC] Build Section #413
Conversation
f9f5884
to
61ad68f
Compare
I like the idea of calling the new section 'build'. Fits for me. I have to confess I'm emotionally attached to the term 'core concepts', but I'm willing to change it if it's getting in the way. What's the reason for changing it to 'learn'? Consistency? I'm also seeing a need for howtos like 'distribute your app', 'Holochain upgrade 0.1→0.2', and 'Setup for a local event', which really shouldn't be in 'get started'. 'Resources' makes sense for most of them, except that 'distribute your app' feels like a build (or rather, post-build) topic. Seems there's two types of content that might show up in 'build':
I've got a proposal for an IA reorg but I want to hear your ideas too:
|
I guess consistency and just copying language from other documenation sites, but it's not important to me -- I'd defer to you.
I don't think these are resources. To me resources are either external links (i.e. to libraries), or api reference docs. Knowing how to upgrade and distribute an app is critical info in the app development process. If we don't want to keep it in build, then maybe it deserves its own section "App Lifecycle" or something. |
Thanks on both counts -- your second point resolves a quandary I was just chewing on, in fact (where to put howtos like deployment, upgrade, etc) |
Closing because #436 deals with the CC renaming, and the Build section will automatically get created once we create our first page in that section. |
actually I created a skeleton in #437 without any actual individual pages. |
This is the main PR to contain many smaller PRs, before they can be merged into main.
Overview