Skip to content

Commit 5a1fd99

Browse files
Update README formatting and section headers
Signed-off-by: Fabiana ⚡️ Campanari <113218619+FabianaCampanari@users.noreply.github.com>
1 parent 414b5f3 commit 5a1fd99

1 file changed

Lines changed: 12 additions & 7 deletions

File tree

README.md

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -246,7 +246,7 @@ The group selects a market or social domain and develops the following steps:
246246

247247
<br>
248248

249-
[**Deliverables for Stage 1:**]()
249+
### ⚡️ [**Deliverables for Stage 1:**]()
250250

251251
<br>
252252

@@ -291,16 +291,21 @@ The [**second subproject**]() in the briefing explicitly requires building an AP
291291
[**Objective:**]() design and implement a **SQL database (≥ 3 tables)** and expose the processed/aggregated data through a **RESTful Web Service**.
292292

293293

294-
Main tasks:[file:2]
294+
<br>
295295

296-
- Choose a real‑world context (company, NGO, market sector, social domain, etc.).
297-
- Design the **SQL database** with at least 3 tables and produce its dump.
298-
- Implement a **RESTful API** that exposes the processed and aggregated data required by the use case.
299-
- Integrate this API into the end‑to‑end workflow: external APIs → processing and storage in SQL → publication via your own REST API.[file:2]
296+
### 🎯[Main tasks:]()
300297

298+
[-]() Choose a real‑world context (company, NGO, market sector, social domain, etc.).
299+
[-]() Design the **SQL database** with at least 3 tables and produce its dump.
300+
[-]() Implement a **RESTful API** that exposes the processed and aggregated data required by the use case.
301+
[-]() Integrate this API into the end‑to‑end workflow: external APIs → processing and storage in SQL → publication via your own REST API.[file:2]
301302

302303

303-
<br>
304+
305+
306+
307+
308+
<br><br>
304309

305310
> [!IMPORTANT]
306311
>

0 commit comments

Comments
 (0)