solene
/
openbsd-webzine
6
0
Fork 8
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity

HTML Semantic #15

Closed
hucste wants to merge 0 commits from (deleted):main into main
pull from: (deleted):main
merge into: solene:main
Conversation 7 Commits - Files Changed -
hucste commented 2021-10-02 10:33:08 +00:00
Contributor
Copy Link

This is a proposal for a semantic HTML code!

  • the current CSS code must certainly be corrected. (not edited here)
This is a proposal for a semantic HTML code! - the current CSS code must certainly be corrected. (not edited here)
hucste added 16 commits 2021-10-02 10:33:08 +00:00
7ab479f66b div to p 
change div not need to p element
87ce97575b HTML semantic 
change div to semantic html
hucste commented 2021-10-02 10:58:30 +00:00
Author
Contributor
Copy Link

See the issue #14

See the issue #14
solene commented 2021-10-02 14:46:32 +00:00
Owner
Copy Link

Nice, but how removing the comment Section is useful for the semantic? It was used for commenting/uncommenting the whole file until we put something in it. That's not a big issue though.

Nice, but how removing the comment Section is useful for the semantic? It was used for commenting/uncommenting the whole file until we put something in it. That's not a big issue though.
hucste commented 2021-10-02 14:51:59 +00:00
Author
Contributor
Copy Link

Just comment bloc of elements, as usual!
and, please, correctly:

<!-- 
<article>
xyz
</article>
-->

You can even use article id for each article element, as:

<article id="quotes"> or <article id="tips">, etc…

Just comment bloc of elements, as usual! and, please, correctly: ``` <!-- <article> xyz </article> --> ``` You can even use article id for each article element, as: `<article id="quotes">` or `<article id="tips">`, etc…
solene commented 2021-10-02 17:47:14 +00:00
Owner
Copy Link

Is this still WIP ? I see there is a conflict for merging, I have no idea to handle that but at least if it's not WIP anymore I can work on figuring how to resolve a conflict from gitea properly :)

Is this still WIP ? I see there is a conflict for merging, I have no idea to handle that but at least if it's not WIP anymore I can work on figuring how to resolve a conflict from gitea properly :)
hucste added 1 commit 2021-10-02 18:20:09 +00:00
hucste changed title from [WIP] HTML Semantic to HTML Semantic 2021-10-02 20:01:40 +00:00
hucste commented 2021-10-02 20:02:28 +00:00
Author
Contributor
Copy Link

Is this still WIP ? I see there is a conflict for merging, I have no idea to handle that but at least if it's not WIP anymore I can work on figuring how to resolve a conflict from gitea properly :)

I delete WIP tag!
it's good for you?

however, I do not understand why it detects a conflict with 'issues/_template/91_QUOTES.html', I maded my fork well after any modification of this file.

Quid?!

Egual, I dont known why gitea wrote error message about my GPG ID!
On my account, it claims OK and displays it into green color. Weird!?

https://imgur.com/3y1dKSq.png

> Is this still WIP ? I see there is a conflict for merging, I have no idea to handle that but at least if it's not WIP anymore I can work on figuring how to resolve a conflict from gitea properly :) I delete WIP tag! it's good for you? --- however, I do not understand why it detects a conflict with 'issues/\_template/91\_QUOTES.html', I maded my fork well after any modification of this file. Quid?! --- Egual, I dont known why gitea wrote error message about my GPG ID! On my account, it claims OK and displays it into green color. Weird!? [![https://imgur.com/3y1dKSq.png](https://imgur.com/3y1dKSql.png)](https://imgur.com/3y1dKSql.png)
solene commented 2021-10-03 09:47:28 +00:00
Owner
Copy Link

The conflict is because changes happened since you made your changes and now we can't just merge your changes into the current state. This is perfectly normal, nothing wrong from your side.

Basically you should use a git pull -r in your branch to fetch the new changes and manage conflicts and make a new commit for fixing the conflict but I'll do it.

The conflict is because changes happened since you made your changes and now we can't just merge your changes into the current state. This is perfectly normal, nothing wrong from your side. Basically you should use a `git pull -r` in your branch to fetch the new changes and manage conflicts and make a new commit for fixing the conflict but I'll do it.
solene commented 2021-10-03 09:58:11 +00:00
Owner
Copy Link

Merged, the changes looked fine in terminal browsers.

Merged, the changes looked fine in terminal browsers.
solene closed this pull request 2021-10-03 09:58:11 +00:00
solene referenced this issue from a commit 2023-10-16 20:20:44 +00:00
issue #15 is out!
solene referenced this issue from a commit 2023-10-17 17:50:54 +00:00
fix puffies in #15 es

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
Easy

This is easy to do

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
bug
duplicate
Easy
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: solene/openbsd-webzine#15
No description provided.
Delete Branch "(deleted):main"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?