-
Notifications
You must be signed in to change notification settings - Fork 320
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
Generic guide: improvements #3796
Comments
Is the suggestion here that we add explicit notes to the blog posts that say which version was used?
I leave this to the article authors if they want to match my wordplay title or not.
I believe we can add an icon next to the link to remove the jarring effect here.
Makes sense, yeah let's remove.
I don't understand the suggested change here.
We had a lot of discussion around this structure - I'd like to test for a while before adopting one of the alternatives we had thought about. In the interim, and perhaps to solve the issue here, let's generalize
This is a larger conversation. |
On #2, are we planning then on removing all stack-specific guides from the documentation and migrate them to the blog? Seems odd to have the docs duplicate the blog, or the blog duplicate the docs. On #5, this is now no longer documentation. This is a list of links, and does contain documentation on how to "Deploy Express on Upsun". IMO, if we are going to have dedicated stack sections in the documentation, then they need to include information that covers the specifics/uniqueness of a stack that isn't covered by the generic guide. Blog posts should then expand on the documentation to cover a topic that isn't included in the docs (e.g. adding a melisearch service to an express project). If the intent of these sections is to just be a list of resources, then they should be renamed "<stack/framework> on Upsun" to indicate the page covers topics concerning the stack/framework and its operation on Upsun. Specific to the Getting Started guideI find the Errors on First Push section to be confusing. Given the section before it (Required Files) covers the configuration files, we have them run Should we give a clarification for this Warning as to why an environment might not be active? Given we have them create the branch using the Upsun cli, it will by default activate the environment (and we mention this in that section) so this seems out of place. |
Where on docs.platform.sh should be changed?
https://docs.upsun.com/get-started/here.html
What exactly should be updated?
Up(sun) and running with Django
) and would like all of our blogpost to have the same "wordplay" -->Up(sun) and running with ...
Upsun demo app
link is a call to action, as it is a link to an "external" website (the console) to create a new demo app. Otherwise, being redirected to the console login page can be confusing.Getting started
section as theUpsun demo application
is already mention in the note block above.Documentation
toGo further
:Getting started
is for beginner and then, documentation section is for more advanced user.Configure your project
section that are not language related to the stack?example:
Javascript/Node.js
Express
Introduction
Setup
Create a project
Configure your project
JavaScript/Node.js
Resources
Revisions
Local development
Third party integrations
Get support
Additional context
No response
The text was updated successfully, but these errors were encountered: