pelican-dev / docs

Documentation site for Pelican Panel
https://docs-peli.vercel.app
25 stars 24 forks source link

Update Blueprint FAQ section to better reflect the current state of things. #60

Closed prplwtf closed 1 month ago

prplwtf commented 2 months ago

This pull request has been made as the current Blueprint FAQ section incorrectly reflects the state of things:

No, you will not be able to use them with Pelican now or in the future. The author of Blueprint unfortunately does not have the time to migrate them to Pelican.

I've corrected this to the following:

No, Blueprint extensions are unsupported by both parties (Blueprint and Pelican). Blueprint is not planning to move over to Pelican now or in the future as Pelican does not align with their goals and objectives (alongside some technical reasons).

The current answer incorrectly assumes that I am responsible for making all extensions work with Pelican, which is incorrect. In my previous PR, I talked about how we didn't have the manpower to port Blueprint over (if Pelican were to align with our goals), not that we didn't have the time to migrate extensions over.

If there are any changes needed that are preventing this PR from getting merged, please let me know.

vercel[bot] commented 2 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 19, 2024 4:52pm
netlify[bot] commented 2 months ago

Deploy Preview for pelica ready!

Name Link
Latest commit 35c9ff3d41e2a043b0656cdb575088a5207b85b9
Latest deploy log https://app.netlify.com/sites/pelica/deploys/66730cae0a841a0008a55b1a
Deploy Preview https://deploy-preview-60--pelica.netlify.app
Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

imlayered commented 1 month ago

when merge

prplwtf commented 1 month ago

This has practically been reverted in commit ce341b8483cf129e3409eb521b07317c9da4f67b right after being merged.

imlayered commented 1 month ago

Pelicans team doesn't seem very good ngl

notAreYouScared commented 1 month ago

I see no reason to go into the whole objectives and goals do not align when it's a FAQ.

It's a simple no, they will not work.

prplwtf commented 1 month ago

I'll drop this topic for now, but merging something and then completely editing something afterwards (which feels like a way to silence a pull request) isn't the nicest thing to do. Recommending changes in my wording and discussing/suggesting better alternatives would've been more appreciated.