[nodebb-plugin-glossary] Glossary Plugin for NodeBB

[phenomlab]

@baris not seeing this in npm yet ?

[yLothar]

@baris now that I know the trick...

[baris]

Added i18n, feel free to send pull requests to add new languages. https://github.com/NodeBB/nodebb-plugin-glossary/commit/616ab500cd6ad906ace7eb7510f7f08789d3515d

0 barisusakli committed to NodeBB/nodebb-plugin-glossary

feat: add i18n

[crazycells]

@baris Hi @baris , I think I missed it. What is "single match" option?

[baris]

If the same word is used multiple times in a post only the first one will be turned into a link if single match is turned on.

[volanar]

It is necessary to disable the use of keywords in URLs. Plugin must not affect URL

[crazycells]

Hi @baris , would you consider adding a "notes" or "extra info" section at .com/glossary page?

It can look like this:

There can be various use cases of this section. I believe it is also usual for regular dictionaries to have a notes section for:

• origin or history of the word
• other forms of the word
• example sentences

etc.

[crazycells]

additionally, is it possible to customize /glossary page just like the /feed page?

(header and footer sections would suffice)

[phenomlab]

@crazycells said in [nodebb-plugin-glossary] Glossary Plugin for NodeBB:

additionally, is it possible to customize /glossary page just like the /feed page?

You can do this with nodebb plugin customize - there isn't a widget etc from recollection.

[crazycells]

@phenomlab said in [nodebb-plugin-glossary] Glossary Plugin for NodeBB:

@crazycells said in [nodebb-plugin-glossary] Glossary Plugin for NodeBB:

additionally, is it possible to customize /glossary page just like the /feed page?

You can do this with nodebb plugin customize - there isn't a widget etc from recollection.

is adding this code to the top of the template enough?

<div data-widget-area="header">
	{{{each widgets.header}}}
	{{widgets.header.html}}
	{{{end}}}
</div>

or adding this to the bottom?

<div data-widget-area="footer">
	{{{each widgets.footer}}}
	{{widgets.footer.html}}
	{{{end}}}
</div>

I cannot see glossary.tpl in widget customize page...

[phenomlab]

@crazycells no, you won't do as there is no widget.

If you use the customize plugin, you can change it there

[crazycells]

@phenomlab said in [nodebb-plugin-glossary] Glossary Plugin for NodeBB:

If you use the customize plugin, you can change it there

Yes, this is what I did. I added those codes above to the tpl file... one to the top, one to the bottom and saved, restarted the forum...

what else should I add to the tpl file to be able to edit the page in the widget customize section?

[phenomlab]

@crazycells I just tried this myself, and get the same result

Added

<div data-widget-area="header">
	{{{each widgets.header}}}
	{{widgets.header.html}}
	{{{end}}}
</div>

Rebuilt, reloaded, but nothing shows in the widget section.

[crazycells]

maybe @baris can direct us... what codes should we add to the glossary.tpl file in order to be able to add widget to the page?

I am more interested in header and footer widgets, not side widgets...

[baris]

I will add the widget areas and info field to the plugin.

[baris]

Published 0.0.19

• Added widget areas to glossary.tpl
• Added info field which is displayed on the /glossary page

[crazycells]

@baris thanks a lot. looks great

what style/codes should I use to add links?

I can see all the HTML links and styles at .com/admin/plugins/glossary page in ACP, however everything is converted to plain text at .com/glossary page...

[baris]

@crazycells That is not possible right now since all the content entered is escaped to make it safe for the front end. I can parse the info field like regular posts so you can use markdown in them. Please open an issue on the plugin page.

[volanar]

@baris can you change the code so that the plugin doesn't look for keywords in the url?

[crazycells]

@volanar said in [nodebb-plugin-glossary] Glossary Plugin for NodeBB:

@baris can you change the code so that the plugin doesn't look for keywords in the url?

I think it is not checking URLs.