PrestaShop / PrestaShop/prestashop.github.io

Idea for articles: new features for developers

Open
#1,118 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
SCSS
Stars
41
Forks
56
Avg merge
21h 46m
Merged PRs (30d)
2

Description

Idea:

Series of shorter articles presenting new developer features in PrestaShop 8. This might feel like a duplication of some of the documentation items. Still, it would help share these pieces on a broader scale on social media + a better way to provide developers with real-life examples.

Series name:

e.g., PrestaShop 8 zoom-in: ...

Ideas:

  • PrestaShop 8 zoom-in: changes in the Hook component, how to deal with them?
  • PrestaShop 8 zoom-in: new CLI features
  • PrestaShop 8 zoom-in: versioning for assets, how to use it? (it probably could be as an explanation of entire registerStylesheet, registerJavascript) + best practices
  • PrestaShop 8 zoom-in: improved front office profiler
  • PrestaShop 8 zoom-in: creating a module for the new back office product page (on hold)
  • PrestaShop 8 zoom-in: using PATCH method in Webservice
  • PrestaShop 8 zoom-in: creating your own distribution
  • PrestaShop 8 zoom-in: meet new hooks + examples
  • PrestaShop 8 zoom-in: details behind performance optimizations
  • PrestaShop 8 zoom-in: what's new for front-end developers?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue proposes a broad series of articles covering hooks, CLI features, asset versioning, the profiler, Webservice PATCH requests, distributions, performance, and front-end development. No files, tests, or entry points are named; first narrow the series to one topic and identify the relevant existing documentation. Done means an agreed article scope with a publishable article and real-life examples.

Written by the indexing model from the issue text.

Assessment

Domain
content, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.