Replies: 4 comments 11 replies
-
To be clear: Discourse is not the central platform of this project. @weierophinney "homepage": "https://laminas.dev",But the redirect didn't work: laminas/laminas.dev#15 |
Beta Was this translation helpful? Give feedback.
-
|
It may be best for us to change the "homepage" metadata for each package, then. The rationale for having laminas.dev and getlaminas.org is water under the bridge at this point. We use laminas.dev for documentation purposes (docs.laminas.dev) and for some project integrations (it provides some webhooks used within the project), but getlaminas.org has been the primary project website since we launched the project fully in 2020. The fact that We can script this change across the repos, applying it to the most recent release branch; I know @michalbundyra has some scripts that can make this relatively quick. |
Beta Was this translation helpful? Give feedback.
-
|
Followup question: Is there a repo for the getlaminas.org website where I can commit changes? E.g it would be great to have a section "learning" where we link to books and tutorials and other learning material provided by the community. Or how do you want to get feedback about what to change on the website? |
Beta Was this translation helpful? Give feedback.
-
Sure. The repository has the same name as the website: https://github.com/laminas/getlaminas.org
Do you have concrete suggestions? |
Beta Was this translation helpful? Give feedback.
-
|
A "Learn" section is definitely needed and I would love to have it. But the focus should be on Mezzio, because a new application should definitely be created with Mezzio. The benefits are:
|
Beta Was this translation helpful? Give feedback.
-
|
Just because one is better doesn't mean we shouldn't honor the work of the others. From my point of view we should list all of them. We can still write at the top that Mezzio is now preferred. But there are still many companies with the normal MVC and they hire new employees as well which need training. So there is still valid reasons to keep this information available as well. |
Beta Was this translation helpful? Give feedback.
-
That's not the topic here.
Right, but here we can also use the documentation, for example: |
Beta Was this translation helpful? Give feedback.
-
|
I mean something like this: https://docs.astro.build/en/community-resources/content/ |
Beta Was this translation helpful? Give feedback.
-
|
And who can write blog posts? Are blog articles by the community of interest to the project? |
Beta Was this translation helpful? Give feedback.
-
Yes. I have: Then this video: Or this starter kit: |
Beta Was this translation helpful? Give feedback.
-
|
Or this tutorial: Or these articles: |
Beta Was this translation helpful? Give feedback.
-
|
"Mezzio: Getting Started" |
Beta Was this translation helpful? Give feedback.
-
|
I see there is more and more coming together. In my point of view we should list them on the website. As well to show that we honor the time people spent on writing about the framework. They are making marketing for the framework which is very valuable. |
Beta Was this translation helpful? Give feedback.
-
|
"Mezzio Essentials" is another book from @settermjd: https://matthewsetter.com/books-and-courses/ |
Beta Was this translation helpful? Give feedback.
-
I had a quick glance into this a few years back and that was pretty good! |
Beta Was this translation helpful? Give feedback.
-
We have at the moment at least two "official" websites about laminas. One is https://laminas.dev/ and the other one is https://getlaminas.org/. Who is responsible for them? What is the purpose of each? Why two different websites?
Furthermore do we really need the blog at https://getlaminas.org/blog/? Or could this be integrated into discourse?
Beta Was this translation helpful? Give feedback.
All reactions